The Bavarian Research Alliance, in cooperation with the Institute of Materials Handling, Material Flow, Logistics at Technical University Munich, Germany, has tested PDM systems for their suitability for building and civil engineering. The PDM systems were tested for the usage in central data administration of AutoCAD drawings and 3D models of buildings in the context of the ForBau project. The results of the comparison were published in February in a detailed study.

PRO.FILE PLM of PROCAD ranked first place in this comparison. Eleven technical criteria were used for the evaluation. PRO.FILE scored best in the categories user ergonomics, administration and customizing, as well as process management. Also in the categories general data management, interfaces and rights/roles/user management, PRO.FILE was not topped by any other system.

Based on this ranking, Technical University Munich selected PRO.FILE for the data management in their large research project ForBAU. The efficiency of the PDM usage in building and civil engineering was demonstrated at the ForBAU final presentation on February 17, with more than 170 visitors. The two project engineers Prof. André Borrmann and Markus Schorr showed in a live presentation how a building project can be handled, from parametric 3D planning to the simulation of execution processes to the recording of the construction progress, with all data being managed centrally in a product data management system.

Details on the study “Data management in construction” Link

Dettagli relativi al progetto ForBAU  Link

Link alla notizia sul sito ufficiale di Procad Click

1. Analisi precisa ed attenta delle esigenze in fase di prevendita.

2. Operatività fin da subito grazie ai Test di Progetto.

3. Implementazione corretta, sicura e produttiva.

Ti garantiamo

1. Un valido supporto nel pre-vendita grazie all’analisi di fattibilità dell’introduzione di un sistema PDM-PLM.

2. Implementazione step by step con formula “Chiavi in mano”.

3. Un aiuto costante nel post-vendita, grazie alla formazione del personale e alla gestione dell’assistenza anche da remoto.

Fin da subito con un modesto investimento iniziale in termini di tempo e risorse verrà fornito lo strumento più potente per intraprendere un percorso di ottimizzazione dei processi aziendali produttivo fin da subito.

Cosa ci distingue?

Ciò che ci distingue da un semplice fornitore è la capacità di interpretare correttamente le richieste e di accompagnarvi come un Partner.Se poi si riesce anche ad anticipare e a superare le aspettative riposte, allora siamo sicuramente molto più di un Partner.

Dall’ascolto attento delle singole esigenze alla proposta della soluzione PDM/PLM mirata, Cadtec lavora con passione e professionalità a fianco del tuo team per studiare il risultato migliore garantendo un servizio completo, efficiente, tempestivo e vantaggioso sul piano economico.

Di seguito le modalità a disposizione:

Per richiedere supporto le ricordiamo di accedere al Techcenter e solo al primo accesso cliccare su New User compilando le informazioni necessarie all’inserimento del Ticket.

Siamo orgogliosi di annunciare che PRO.FILE (www.profile-plm.it), con il nuovo Service Pack 8.3 SP7, ha aggiornato tutte le integrazioni con le nuove versioni dei sistemi CAD 2012, e nello specifico:

• SolidWorks 2012
• Solid Edge ST4
• Creo Parametric 1.0
• Pro/E Wildfire 5.0
• Creo Elements Pro 5.0
• Creo Elements Direct Modeling 18 (ex CoCreate Modeling v18)
• Inventor 2012
• Catia V5 R21
• Creo Elements Direct Drafting 18 (ex ME10 v18)
• AutoCAD e AutoCAD LT 2012

Il template partirà in automatico quando vi connetterete al sito mediante un terminale portatile.

Ne approfittiamo per ricordare a tutti i clienti che anche il portale di assistenza ha un suo template mobile cui si può accedere specificando “/pocket50″ anzichè “/tech50″ nell’indirizzo del portale stesso.

Il giorno dal quale il nuovo SP sarà disponibile è il 22 settembre 2011.
Come sempre, appena avremo a disposizione i changelog definitivi, provvederemo a fare un elenco delle migliore apportate nella nuova versione, così da poter permettere a tutti i nostri customer di valutare se applicare o meno il nuovo service pack.

La causa del disservizio è da riferirsi ad una manutenzione straordinaria dei server.

Ci scusiamo per il disagio, segnalando che i tecnici saranno comunque reperibili telefonicamente o via mail durante tutto il periodo di down del portale.

Il down partirà alle ore 12.30 e terminerà entro e non oltre le ore 13.45

Epta Group

Leader mondiale nel settore refrigerazione, utilizza il sistema PDM/PLM Pro.file integrato ai sistemi CAD ed ERP in uso nelle varie sedi remote di Italia (Costan) Francia (Bonnet Nèvè), Regno Unito (George Barker).Implementazione realizzata in 6 MESI.

Alcuni passi del changelog (eng) sono disponibili dopo il salto.



Changelog

• Pro.File 8.3 Sp5 Server Component e Pro.File 8.3 Sp4 Windows Client
• Pro.File 8.3 Sp5 Proadmin Console
• Pro.File 8.3 Sp5 Web Client
• Pro.File 8.3 Sp5 Process Designer
• Pro.File 8.3 Sp5 Autocad Integration
• Pro.File 8.3 Sp5 CATIA V5 Integration
• Pro.File 8.3 Sp5 Inventor Integration
• Pro.File 8.3 Sp5 PRO Engineer Wildfire Integration
• Pro.File 8.3 Sp5 Solid Edge Integration
• Pro.File 8.3 Sp5 SolidWorks Integration
• Pro.File 8.3 Sp5 Unigraphics Nx Integration
• Pro.File 8.3 Sp5 Microsoft Office Integration
• Pro.File 8.3 Sp5 Microsoft Outlook Integration
• Pro.File 8.3 Sp5 Lotus Notes Integration
• Pro.File 8.3 Sp5 Job Server NDF
• Pro.File 8.3 Sp5 Job Server Monitor

Pro.File 8.3 Sp5 Server Component e Profile. 8.3 Sp4 Client:

241.) Request 40839
The quantity bill of materials can now be configured in such way, that fields with dimensional
variations are regarded for grouping. That means if e.g. one part with 2 different dimensions is
assembled 3 times in a CAD model and the bill of materials is derived from this model, 2 positions
with count 3 and one of these dimensions appears in the quantity bill of materials.

242.) Request 41147
When the environment variable “DoUpdateAutoparBeforeTitleBlock” is set to the value “YES” or with the
aid of the PRO.FILE Management Console parameter “DO_UPDATE_AUTOPAR_BEFORE_TITLEBLOCK” it is possible
to define, that when a drawing has been changed and is saved back to PRO.FILE, the parameters are
transferred to PRO.FILE via the AUTOPAR functionality first and the title block is updated afterwards.

243.) Request 41308
When an assembly is saved to PRO.FILE, it is now checked whether or not other versions of the
components are referenced than in the PRO.FILE document structure. If this is the case, the affected
subassemblies are marked as “locally changed” and offered for saving to PRO.FILE.

244.) Request 41389
Lookup reference list fields can now also be used in connection with the tool Showlist. If several
values are to be used, they must be separated with comma. However, only the reference list field can
then be used for the search.

245.) Request 41431
For the document list, the evaluation of the configuration of the names of the month has been
corrected in order to display the name of the month in the configured language.
Note: In date fields of the document list it is possible that English names of the month are displayed
instead of German names. The configuration of these list fields must be corrected in the PRO.FILE
Management Console. If this is the case for many fields, this can be done with a direct change in
the database.

246.) Request 41519
When a document favorite searches documents via a status name, e.g. “In work for fair 2010″, and this
status does no longer exist, no documents are found and a corresponding message is displayed instead.

247.) Request 41743
When the connection type of a connection is changed from static to dynamic, no more unnecessary SQL
statements are created.

248.) Request 42063
In the Gantt diagram the correct duration is now displayed for tasks that have not been started, even
if the company calendar has been changed afterwards.

249.) Request 42344
It is now possible to move a leading tab, even if this tab was active before.
Note: A leading tab cannot be moved in front of the start and the task page.

250.) Request 42421
When the function lock or unlock is used in the WorkCenter, a function right check is now made.
With this, the user can lock only the documents for which he has the right to do so.

251.) Request 42467
PRO.FILE no longer crashes, even if very large assemblies with thousands of parts are opened from
PRO.FILE.

252.) Request 42499, 40714
Result lists, which have been created via a favorite, are now displayed completely and fill the
entire area of the leading window.

253.) Request 42537
If the creation of a modification entry is configured for the status of a document when a new version
is created, a modification entry is now also requested in the context of the integration function
“Append version”.

254.) Request 42545
It is now possible to fill the project status field via the API or via a cross table.

255.) Request 42582
The search for documents via parts using a multi-line field of the part master record now returns
the correct results.

256.) Request 42586
When a file is opened from PRO.FILE and the local file is newer, an inquiry, asking whether or not
the local file should be overwritten, is now displayed in any case.

257.) Request 42607
The PRO.FILE Management Console parameter “Show a list of documents to lock/unlock” is now evaluated
correctly, and if it is configured like this, a lock list is displayed when an assembly is initially
saved to PRO.FILE.

258.) Request 42648
If an SQL check function is defined on a reference list field and if it is configured, that this
check function is only to be executed when the form is closed, it is now only executed when the form
is closed.

259.) Request 42657
In the Mail class, methods for special programming have been added.

260.) Request 42711
When additional fields are displayed on a PRO.FILE form, because of an item characteristics class or
a change of the document type, and the form does not offer enough place for those fields, the
scrollbar is now displayed correctly.

261.) Request 42721
When the PRO.FILE Escalation Manager or the PRO.FILE Notification Server try to send an e-Mail and
this does not work, a message is written into the Event Log. This message is now more precise and
points out the error cause to the user.

262.) Request 42723
Changing several documents with different document types in one action now works, because the
document type has no longer to be entered in this case and the changes are thus applied to all
documents.

263.) Request 42724
When a document or the first version of this document is created, different entries are now written
into the database table BIZE_EVENT, so that these two cases can be distinguished.

264.) Request 42738
Bitmap files, that are located in the folders under the path %DBANWPFAD% can now be exchanged, even
if the PRO.FILE Windows Client is running. These bitmap files are used e.g. to display the icons for
the status in PRO.FILE lists.
Note: When the bitmap files, that are located in the folders under the path %DBANWPFAD% are
exchanged, they do not become visible in the PRO.FILE lists before the PRO.FILE Windows Client
has been restarted.

265.) Request 42764
PRO.FILE no longer freezes when, during the creation of a document, the document type is selected via
the tree on the left-hand side and the recently selected document type has the same characteristics
as the currently selected document type.

266.) Request 42768
When documents are searched via part fields, the search now also returns the documents, for which
the newest document version is to be found.

267.) Request 42804
A change of the redlining information is now recognized by PRO.FILE as a change and is therefore
correctly saved back to PRO.FILE.

268.) Request 42805
When the user works with projects, the PRO.FILE windows are now displayed correctly and with the
correct content.

269.) Request 42809
When PRO.FILE meta data are changed, only the contents of the fields, which are configured on the
change form are written into the database.

270.) Request 42822
The bill of materials can now be renumbered without problems in the bill of materials editor, even
if some of the columns have the same title.

271.) Request 42834
The search in multi-line fields now returns the correct results, even if there are numerous multi-line
fields with more than 1000 characters, which do not contain the search string.

272.) Request 42841
If the environment variable SUPRESS_REFRESH_ON_DISCONNECT is set to “yes”, PRO.FILE no longer performs
a refresh for the active windows if an integration closes its connection to PRO.FILE.
With this, PRO.FILE is immediately ready to accept a new connection.
Note: When an integration closes the connection to PRO.FILE, no refresh is performed for the active
windows in PRO.FILE. The refresh has to be executed manually, if necessary.

273.) Request 42853
When a version of a document is not linked with a part and a newer version of this document is
linked with a part, this part is now displayed in the usage view of the older document version.

274.) Request 42868
In the context of the conversion of CAD data, the correct date format is now entered into the
document master record when the CAD documents are saved back to PRO.FILE.

275.) Request 42881
The evaluation of the project access rights now works correctly for cumulated superior projects,
and with this, the correct objects are found. In addition, the superior project is now checked,
even if access rights exist.

276.) Request 42883, 42562
Thanks to a program change the Archive Server and the Cache Server should no longer crash.

277.) Request 42913, 42864
If it is configured like this, reference lists on multi-line fields are now displayed in selection
forms and are working correctly.

278.) Request 42914
Even if a PRO.FILE field is filled by a script and the title length of this field is 0, the field
is no longer moved.

279.) Request 42917, 41669, 42815
When changed data are saved back to PRO.FILE via an integration, the PRO.FILE window for entering
and saving the modification log is displayed in the foreground and is ready for the input.

280.) Request 42941
Even if a connection to the PRO.FILE Windows Client is established by the port scanner, telnet etc.,
the PRO.FILE Windows Client works properly and without error message.

281.) Request 42971
When changes are to be saved back, all CAD integrations now only display the locally changed documents
in the PRO.FILE document list and offer them for saving.

282.) Request 42980
The search for documents by expressions like “today” (#) now returns the correct results in different
time zones as well.

283.) Request 43025
The user now gets a feedback, if he starts the client-side creation of the neutral format without an
output format being configured for that.

284.) Request 43028
When PRO.FILE is started by an integration and during this action a dialog is displayed, the
integration no longer freezes and the dialog is displayed correctly.

285.) Request 43042
When a reference list is expanded, the number of characters is now used to calculate the display
width. This is not as exact as GDI functions, but uses less time.

286.) Request 43073
When a new window is opened via the object specific editor (open with “Edit” -> “Editor”) and a
status change is made for one of the objects in this window via the button “Status change” in the
main toolbar, no empty message is displayed any longer.

287.) Request 43080
When the function “New with data” is applied to a document, to which another document is linked, and
only data of the linked document is changed, then the leading document is not duplicated any longer.

288.) Request 43102
When a PRO.FILE field is filled via a cross table and the form has been scrolled vertically before,
the scrollbar is set to its previous position after the form has been refreshed and the field is
displayed again at the same screen position.

289.) Request 43104, 43394
The dialog for entering the modification comment is now also displayed in the task bar in order to
make it reachable for the user. Furthermore, the mechanism for displaying PRO.FILE data via an
integration has been changed. With this, PRO.FILE should no longer freeze when e.g. the part master
record of a CAD part is to be displayed.

290.) Request 43109, 42309
Sending e-Mails to internal recipients in the context of a status change in the PRO.FILE Web Client
now works properly.

291.) Request 43133, 43233
If the name of the document type is configured language-specifically and is used as a criterion
for a favorite, this favorite now works in all used languages.

292.) Request 43136
When the function Managed Copy is used and drawings are included, these drawings are reloaded from
PRO.FILE, if necessary. During this action PRO.FILE checks whether or not the drawing models of the
first level have the right version. If this is the case the substructure of these drawing models is
not checked and the program assumes, that the locally present versions of the subassemblies and
parts are to be used.

293.) Request 43142
Changing several documents with different document types in one action now works, if only fields of
the fix document master record are changed.

294.) Request 43147
If all of the documents within a version list are of the same document type, the specific fields
for this document type are now displayed correctly.

295.) Request 43158
When a change operation for several positions is aborted in the multi-selection mode of the bill of
materials editor, the parent part of these bill of materials positions is not locked anymore
afterwards.

296.) Request 43189
Thanks to a change in the PRO.FILE database gateway, reference list entries, which contain a double
quote or double prime symbol, can now also be deleted in the PRO.FILE Management Console.

297.) Request 43211
When a file is saved to PRO.FILE via Drag & Drop and attached to a document with a folder, the file
is now added to the folder.
Note: This also applies for Redline files.

298.) Request 43243
When several documents are selected in PRO.FILE for opening, an inquiry is displayed, asking which
of them are to be opened directly in the CAD system after they have been copied to the local working
folder.

299.) Request 43270, 43598
When an object list with several objects is displayed in the leading tab and an object is selected in
the dependent tab “Browser” and a status change is made via the icon “Status change” , then all of
the objects are now displayed in the leading tab.

300.) Request 43280
The PRO.FILE preview window now works with the AutoVue version 20.1, but no longer with AutoVue
version 20.0!
Note: If the PRO.FILE preview window is used with AutoVue, all of the client computers have to be
updated to the AutoVue version 20.1. If this is not possible, the configuration has to be adapted to
the AutoVue version 20.0. For doing so, the configuration parameter “ProcadView.AutoVue.Assembly”
under “PRO.FILE” -> “Document” -> “Viewer” in the PRO.FILE Management Console has to be changed to
the value “Procad.Profile.Viewer.AutoVue200.dll”.
If the AutoVue version 20.1 is installed later, the configuration parameter has to be reset to its
original value “Procad.Profile.Viewer.AutoVue.dll”.

301.) Request 43295
When a file is saved to PRO.FILE via Drag & Drop and during this action a new version of an existing
PRO.FILE document is to be created, the user exit is now called before the file is actually saved.
With this, the status can be reset early enough, so that the user has the right to change the file.

302.) Request 43304
Even if a status is named language-dependent and a favorite uses the name of such a status as search
criterion, this favorite now works in all languages.

303.) Request 43336
When the transfer of values during the derivation of a bill of materials is defined in a CAD system,
these values are now also transferred if the values are changed afterwards in the CAD system and the
bill of materials is derived again.

304.) Request 43338
If the user has defined grouped list views as default and he wants to select users via the user
selection dialog, this dialog is opened and positioned on the first line as expected.

305.) Request 43352
When an assembly is saved to PRO.FILE, the program checks whether or not a document exists for the
CFG file. If this is the case, the CFG file is saved to this document.

306.) Request 43418
When the version selection is used for the open function, the opened version is displayed with the
folder icon in the dependent list with the existing versions, and the version “as saved” is displayed
with the floppy disk icon. With this, it is directly visible for the user, which version is used in
the assembly. In case of version conflicts an exchange of the versions is made generally, because
otherwise it is not possible to open the assembly. For this exchange the highest assembled version
is used.

307.) Request 43426
A new API function has been implemented giving the possibility to check whether or not a user exit
is called within an open transaction.

308.) Request 43436
PRO.FILE now checks directly before the call of a print command of a Format Generator whether or not
a file with the defined fixed file name exists. If this is the case, the file is deleted and the
Format Generator waits until its own file has been created. This makes sure that the correct neutral
document is saved to PRO.FILE.

309.) Request 43455
When the version of a part in an assembly is replaced by another version of this part and the bill of
materials is derived afterwards, a new bill of materials position with the same position number is
created for this part. In addition, all float and string fields of the original bill of materials
position are now taken over, provided that the CAD integration does not hand over values for these
fields. Fields with administrative information e.g. GUID, PPS state etc. are still created anew,
because it is a new bill of materials position.

310.) Request 43460
When transmittals are sent to internal recipients, the P2M file is now created correctly so that the
recipients are able to open this file to display the PRO.FILE objects.

311.) Request 43494
In the CAD/Office browser the first line with the data of the root element is now displayed correctly.

312.) Request 43508
When the user selects the value “cumulative superior project” in the field “guest role” of a
subordinate project, all of the defined role assignments are now evaluated.

313.) Request 43518
The document list is now also displayed completely for large bills of materials without the need to
scroll to the end before.

314.) Request 43541
When several parts are changed in one action, the selection function is no longer evaluated for the
multi-line fields, but additional properties, which are not depending on the configuration.
With this, regardless of the configured selection function, multi-line fields are only changed if
the user really has changed them.

315.) Request 43560
The Cache Server now only copies the files to the cache area, if they are not up to date there.
This also applies when the environment variable PROCOMPRESS is set.

316.) Request 43581
When the user tries to delete a link between a part and a document and he answers the query whether
or not the link should really be deleted with “NO”, then the link is not deleted and the field
contents inherited from the part are no longer cleared.

317.) Request 43599
The printer settings “printer”, “portrait/landscape” (only for forms), “paper size” and
“border settings” (only for forms) are now saved in the file %APPDATA%/Procad/Profile/PrintSettings.xml
and can thus be used again for the next printout.

318.) Request 43605
The integration function “Display Drawing” now works error-free, even if there are a lot of drawings
in the local working folder.

319.) Request 43659
When the extended bill of materials is refreshed via the key F5, the first line with the parent part
now stays.

320.) Request 43706
When an object is created, all fields are now filled according to the configuration via a cross table,
even if a check function is defined on the form and this check function returns an error.

321.) Request 43717
In the WorkCenter the working folder can no longer be changed, if it is only in viewing mode.

322.) Request 43736
When bill of materials positions are renumbered, a modification date is now entered.

323.) Request 43778
The project list is now displayed sorted, e.g. when the user searched via the project name.
In the results the newest project is always at the  top of the list.

324.) Request 43781
The order of the variable part master data in the database no longer has consequences for the change
of part master data. With this, the changes are taken over and written correctly into the database.

Pro.File 8.3 Sp4 Proadmin Console

048.) Request 41431
In the PRO.FILE Management Console the configuration with English and German names of the month has
been switched in order to match the display and the behavior in the context of the form view.
With this, there is no change necessary for the date fields in the form view and future configurations
can be done according to the display. For the document list, the evaluation of the configuration of
the names of the month has been corrected in order to display the name of the month in the configured
language.
Note: In date fields of the document list it is possible that English names of the month are displayed
instead of German names. The configuration of these list fields must be corrected in the PRO.FILE
Management Console. If this is the case for many fields, this can be done with a direct change in
the database.

049.) Request 42616
When an output format is not supported for the creation of neutral formats, a message is displayed.
This message is now suitable, even if the method “SaveAs” is used for the format generation.

050.) Request 42824
For the users listed under the node “Configuration” -> “User parameter” no properties can be displayed
or changed. For this reason, the menu item “Configuration” -> “Properties” has been deactivated.

051.) Request 42865
In the form designer it is now possible to delete the form set 0, if at least one other form
set exists.

052.) Request 43267
When the user changes the name of a control on a form in an older PRO.FILE release and exports this
form, the form definitions and fields are now written correctly into the database for another form
during an import of this form. With this, the objects of such a form remain visible after the form
has been changed and saved.

053.) Request 43372, 42882
The maximum waiting time in the printer configuration for the Format Generators was increased to
14400 seconds (4 hours) and the default is set to 120 seconds.

Pro.File 8.3 Sp4 Web Client

028.) Request 42210
If a project is duplicated and the field “Guest role” is not defined on the creation form, the default
value “user” is now entered for the guest role. This is required, because otherwise the project is no
longer visible in PRO.FILE.
Note: Since the implementation of the status management for projects, the field “Guest role” cannot be
changed during creation, because projects would not be visible in PRO.FILE afterwards. When a project
is changed, another value for the field “Guest role” can be entered, because in this context
additional checks are made (e.g. role assignments, superior project, etc.).

029.) Request 42335
In the status administration the access permissions of the functional user “AUTOR” are now evaluated
correctly for projects.

030.) Request 42346
Updating files or documents via an integration now also works correctly when role assignments are
used for projects.

031.) Request 42063
In the Gantt diagram the correct duration is now displayed for tasks that have not been started, even
if the company calendar has been changed afterwards.

032.) Request 42547
On the start page, the icon next to the field for the full-text search is now displayed correctly,
even if the user switches to part, document or project in the selection box.

033.) Request 42935
A list view, which is set as default in the PRO.FILE Windows Client is now also used in the
PRO.FILE Web Client.

034.) Request 43109, 42309
Sending e-Mails to internal recipients in the context of a status change in the PRO.FILE Web Client
now works properly.

035.) Request 43508
When the user selects the value “cumulative superior project” in the field “guest role” of a
subordinate project, all of the defined role assignments are now evaluated.

036.) Request 43778
The project list is now displayed sorted, e.g. when the user searched via the project name.
In the results the newest project is always at the top of the list.

Pro.File 8.3 Sp4 Process Designer

001.) Request 39638
In the English version of the setup the correct product name is now displayed throughout the dialogs.

002.) Request 40680
When the PRO.FILE Process Designer is to be used with Visio 2010, its setup now checks whether or
not the .NET programmability support is installed on the computer. If not, an error message is
displayed and the setup aborts.

Pro.File 8.3 Sp4 Autocad Integration

17.) Request 43256
Updating the drawing title block of a drawing with external references (drawing and pixel image)
now works error-free.

Pro.File 8.3 Sp4 CATIA V5 Integration

10.) Request 43678
Drawings, which reference parts or assemblies via HybridBodies, can now also be saved to PRO.FILE.

Pro.File 8.3 Sp4 Inventor Integration

17.) Request 42353
In the Managed Copy dialog, components that are locked by another user are now displayed and can
thus be copied.

18.) Request 42542
Before a component is opened from PRO.FILE, all components in the session are now updated.
This makes sure that always the newest components are loaded before the opening action.

19.) Request 42618
When a bill of materials is inserted on a drawing, Inventor no longer crashes, even if a lot of
positions (>20) are set to “Bill of materials irrelevant” in the PRO.FILE bill of materials

20.) Request 42656
When an assembly contains instances, that are referencing from different folders to the same part
family, and this assembly is saved to PRO.FILE, a message is displayed during the reading of the
structure, pointing out this fact to the user, and the save action is aborted.

21.) Request 42674
The integration no longer reads PRO.FILE Management Console parameters, which are not needed.
With this, the integration commands should be executed faster.

22.) Request 42880
The setup for the  Inventor Integration now installs the integration correctly, and as a result,
the PRO.FILE menu is available in Inventor after the installation.

23.) Request 42907
An assembly with derivations, whose references to the parent part are broken, can now also be saved
to PRO.FILE without problems.

24.) Request 43062
When iPart or iAssembly instances are inserted via the command “Insert part”, the corresponding
CAD files are now copied to a subfolder of the local working folder. This subfolder is named after
the part family. When the instances are saved back to PRO.FILE, they are now recognized as PRO.FILE
documents.

25.) Request 43219
When the function “Insert bill of materials” is used, Inventor no longer crashes, even if the
PRO.FILE Management Console parameter “Update/Sort parts list on drawing” is set to the value
“NO_UPDATE”.

26.) Request 43383
When an assembly is opened from PRO.FILE, Inventor no longer crashes, even if the recently active
detail precision cannot be read.

Pro.File 8.3 Sp4 PRO Engineer Wildfire Integration

24.) Request 42453
If the environment variable “CHECK_MODELS_IN_SESSION_AFTER_RETRIEVE_ONLY_ON_NDF” is set to the value
“YES”, the Pro/ENGINEER models are checked for errors during the opening action, and no neutral format
is created if the models are faulty.
Note: This hotfix only makes sense in the context of the Format Generator.

25.) Request 42607
The PRO.FILE Management Console parameter “Show a list of documents to lock/unlock” is now evaluated
correctly, and if it is configured like this, a lock list is displayed when an assembly is initially
saved to PRO.FILE.

26.) Request 42664
For the Format Generator, the neutral format STEP is now also created correctly for assemblies
and parts.

27.) Request 43153
If it is configured via the PRO.FILE Management Console parameter “Update BOM during save”, the
function “Save BOM” no longer adds suppressed components, that are not loaded in the system memory,
to the bill of materials.

28.) Request 43466
When Pro/ENGINEER data is saved to PRO.FILE, an automatic connection between the CAD document and an
existing part master record can be configured. This is now possible by using the number as well as the
name of a part master record field, i.e. in both cases the matching part master records are found,
if they exist.

29.) Request 43711
The menu item “Open all drawings” has been added to the menu. With this it is possible to open all
drawings, which are included in the structure of the active model.
Note: Only the drawing for the active model is opened. All other drawings are copied to the local
working folder.

30.) Request 43717
In the WorkCenter the working folder can no longer be changed, if it is only in viewing mode.

Pro.File 8.3 Sp4 Solidedge Integration

35.) Request 42341, 42516
After the integration function “Replace component” has been used, the Solid Edge function “Open”
remains active and works without problems.

36.) Request 42395
The creation of a position number in a drawing now works, even if parts are missing in the structure
or if parts are grouped in the EdgeBar.

37.) Request 42783
When a drawing is in background mode and a neutral format has to be created from this drawing, no more
message is now displayed.

38.) Request 42861
When a neutral document is created, it is now saved to the correct folder and therefore saved correctly
in PRO.FILE.

39.) Request 42875, 43325, 42704
When a subassembly is selected in the Edge Bar and the user tries to display the corresponding part
master record in PRO.FILE, this part master record is displayed properly and without prior error
message.

40.) Request 42889
Parts of a Solid Edge assembly can now only be replaced by Solid Edge documents.

41.) Request 42974
After a drawing is opened, the Solid Edge file properties are now updated by the Solid Edge
integration. With this, the Solid Edge file properties can be used for updating the drawing title
block.

42.) Request 43091
In the context of an assembly the function “Display drawing” now displays the drawing of this assembly.

43.) Request 43224
Some commands of the Solid Edge integration check whether or not the referenced files match the file
names of the assembly components. If an inconsistency is found, the integration assumes that the name
of the assembly component is not updated correctly. In this case the document is loaded and its file
name is checked. This behavior results in a little performance loss. But since the documents are only
loaded for the components, for which the file names are returned incorrectly, this should only lead
to a noticeable delay in exceptional cases.

44.) Request 43225, 43602, 43590, 43591
When the user aborts the function “Replace Part” or “Insert Part”, no more error message is displayed
in the CAD system and the function can be used again.

45.) Request 43243
When several documents are selected in PRO.FILE for opening, an inquiry is displayed, asking which
of them are to be opened directly in the CAD system after they have been copied to the local working
folder.

46.) Request 43354
In the context of the function “Managed Copy” the selected documents have to be renamed, and for
doing this, they must be closed and opened again. During this action the connection to PRO.FILE no
longer gets lost and the function “Managed Copy” works properly.

47.) Request 43435
When decimal numbers are in Solid Edge text fields and they are transferred to PRO.FILE via the AUTOPAR
functionality and variable fields, the decimal places are now transferred correctly.

Pro.File 8.3 Sp4 SolidWorks Integration

35.) Request 42551
SolidWorks documents, that are saved in PRO.FILE, are now correctly recognized as PRO.FILE documents
by the integration, because the upper and lower case spelling of the property procad@dokid is ignored.

36.) Request 42727
The file property containing the PRO.FILE ID is no longer evaluated for drawings.
Note: For parts and assemblies the configuration-specific file property containing the PRO.FILE ID
is still required. If this property is deleted, the user is still requested to create a document
for an instance.

37.) Request 42789
When a drawing and a part have the same name and the drawing is saved to PRO.FILE immediately after
the part, the Check-In wizard now displays the thumbnail of the drawing.

38.) Request 42904
The check of the file properties when saving assemblies or parts was deactivated. With this,
assemblies which contain VarBox parts can be saved in PRO.FILE.

39.) Request 43085
When the references are read from SolidWorks, the spelling of the corresponding file names concerning
lower/upper case is transferred like it is returned from the SolidWorks API.
Note: SolidWorks assemblies take over the spelling for components at the moment these components are
inserted. If the spelling of a component is changed afterwards, SolidWorks does not take over this
change, because it is not relevant for the loading of the component. Because the SolidWorks integration
takes over the spelling of assembly components like it is returned from SolidWorks, it may still happen
that a later changed spelling is not taken over in PRO.FILE.

40.) Request 43243
When several documents are selected in PRO.FILE for opening, an inquiry is displayed, asking which
of them are to be opened directly in the CAD system after they have been copied to the local working
folder.

41.) Request 43512
Even if an assembly that is opened from PRO.FILE has several configurations, it remains open.

Pro.File 8.3 Sp4 Unigraphics Nx Integration

20.) Request 43086
After the client-side creation of the neutral format, the connection to PRO.FILE is now released
properly, so that the user can continue working with PRO.FILE.

21.) Request 43345
When a part family is saved to PRO.FILE, this action now works error-free, because the Generic can
now be renamed properly.

Pro.File 8.3 Sp4 Microsoft Office Integration

016.) Request 42737
If it is configured like this, the file name is now entered reliably as original name into the
document master record in PRO.FILE.

Pro.File 8.3 Sp4 Microsoft Outlook Integration

012.) Request 43515
When a document is changed via the Outlook integration, the document master record is also changed,
and the version key of the integration, e.g. MS Outlook-2000, is now entered correctly.

013.) Request 43615
The PRO.FILE Management Console parameter “Replace original mail” can now also be set to the value
“ASK”.  With this, the user has the possibility to decide himself whether or not an e-Mail is to be
replaced.

014.) Request 43617
The format of the local e-Mail is not changed anymore, when the e-Mail has been saved to PRO.FILE and
has been extended by the text, that gives the user the information about the database, in which the
e-Mail has been saved and the document ID, under which the e-Mail has been saved.

Pro.File 8.3 Sp4 Lotus Notes Integration

03.) Request 43515
When a document is changed via the Lotus Notes 8 integration, the document master record is also
changed, and the version key of the integration, e.g. Lotus Notes 8, is now entered correctly.

Pro.File 8.3 Sp4 Job Server NDF

005.) Request 43113
When the Format Generator processes a task, it now checks whether temporary working folders still
exist from previous tasks. If this is the case, these temporary working folders are deleted.

006.) Request 43571
The PRO.FILE Job Server now also works correctly in the context of Solid Edge x64 and the Format
Generator for Solid Edge.

Pro.File 8.3 Sp4 Job Server Monitor

007.) Request 42975, 43045, 43068, 42806
In the monitor for the Job Server the correct dates for the creation and finish date are now also
displayed on a German operating system.

008.) Request 43681
In the monitor for the Job Server the time zone is now regarded in date fields with displayed time.

Le certificazioni comprendono:

SERVER OS\DB:

• Windows Server 2008 x64 SP2
• Windows Server 2008 R2 x64
• SQL Server 2008 x64
• SQL Server 2008 R2 x64
• Oracle 11g Release 1 x64 (11.1.0.x.0)
• Oracle 11g Release 2 x64 (11.2.0.x.0)

Sistemi Operativi Client:

• Windows XP SP3
• Windows XP x64 SP3
• Windows 7
• Windows 7 x64

-Integrazioni CAD-

Autocad – : regular version, Mechanical version e Mechanical Power Pack

• AutoCAD 2009
• AutoCAD 2010
• AutoCAD 2010 x64
• AutoCAD 2011
• AutoCAD 2011 x64
• AutoCAD 2012
• AutoCAD 2012 x64

Catia:

• Catia V5 R18
• Catia V5 R18 x64
• Catia V5 R19
• Catia V5 R19 x64!

CoCreate Drafting:

• CoCreate Drafting Version 2007 (15.5)
• CoCreate Drafting Version 2008 (16.0)
• Creo Elements/Direct Drafting 17

Inventor:

• Inventor 2009
• Inventor 2009 x64
• Inventor 2010
• Inventor  2010 x64
• Inventor 2011
• Inventor 2011 x64
• Inventor 2012

Microstation:

• Microstation 8.5
• Microstation XM (8.9)
• Microstation 8i

Pro/Engineer:

• Pro/Engineer Wildfire 3.0
• Pro/Engineer Wildfire 3.0 x64
• Pro/Engineer Wildfire 4.0
• Pro/Engineer Wildfire 4.0 x64
• Pro/Engineer Wildfire 5.0
• Pro/Engineer Wildfire 5.0 x64

Solid Edge (tutti gli MP):

• Solid Edge V20
• Solid Edge ST
• Solid EdgeST x64
• Solid Edge ST2
• Solid Edge ST2 x64

SolidWorks (tutti gli MP\SP se non specificato):

• SolidWorks 2010 (da SP4)
• SolidWorks 2010 x64 (da SP4)
• SolidWorks 2011
• SolidWorks 2011 x64

Unigraphics:

• Unigraphics NX 5.0
• Unigraphics NX 5.0 x64
• Unigraphics NX 6.0
• Unigraphics NX 6.0 x64
• Unigraphics NX 7.5
• Unigraphics NX 7.5 x64

Office ed E-Mail:

Lotus Notes:

• Lotus Notes 8.0.1
• Lotus Notes 8.5

Microsoft Office (SP MINIMO specificato):

• MS Office XP SP3
• MS Office 2003 SP3
• MS Office 2007 SP1
• MS Office 2010

Microsoft Outlook (SP MINIMO specificato):

• MS Outlook XP SP3
• MS Outlook 2003 SP3
• MS Outlook 2007 SP1
• MS Outlook 2010

Sono disponibili ulteriori integrazioni con CAD meccacini, CAD Elettrici e programmi E-mail.
Se interessati a ricevere ulteriori informazioni, vi preghiamo di contattarci.

Sono come sempre disponibili, per tutte le integrazioni certificate, pacchetti per la generazione e l’archiviazione automatica di formati neutri (PDF, DXF, TIF, etc) sia per i programmi CAD che per quelli di produttività personale o e-mail.

Con questo Service Pack, sono stati rilasciati aggiornamenti anche per le integrazioni con i sistemi ERP (esempio SAP, etc.), così come nuovi updates per il servizio di condivisione dati via web, quello di compressione dati, il sistema di gestione con cache server e per le sedi remote, e tutti gli altri pacchetti che formano il mondo di Pro.File.