Integration with Other Applications > Windchill Workgroup Manager Documentation > CATIA V5 > User > Advanced Techniques for CATIA V5 > CGR File Management for Large Assemblies (CATIA V5) > CGR and XML File Generation (CATIA V5)
CGR and XML File Generation (CATIA V5)
CGRs and XMLs can be generated with the following types of actions.
Action
Description
Open of a CAD document
During the open of an assembly, a check is performed on each CATPart with the XML file to determine if there are any pending metadata changes for the documents in session. These metadata changes fall into two categories: system attributes (examples: revision changes, iteration changes, lifecycle changes, name/number changes) and file-based Attributes (metadata changes which are tracked on the CAD document through an attribute which is mapped to a global attribute in Windchill) Depending on which update is necessary the XML file determines if new CGR files are generated on disk.
Switch a CATPart into Design Mode
If the only updates necessary for an in-session CAD document are for system attributes, then the update is delayed until the part is switched into design mode. This delay prevents loading the documents into session when only the system attributes have been changed.
Save to Workspace
If a CATPart has been modified, then it is saved and a new CGR and XML file is generated to reflect the changes made to the document.
The following are the most common reasons for an update to the CAD document, which would then cause CGRs to be regenerated:
• The CATPart was last saved with the 8.0 Windchill Workgroup Manager for CATIA V5.
• System attribute changes, such as Revise, Lifecycle, Check In and Check Out using only the Windchill Workgroup Manager client interface.
• Changing a global attribute value using the Windchill Workgroup Manager client interface.
• Checking in a CAD document in without checking it out first. The iteration value is not changed before the document is saved. When you next open this document you must change the iteration value again. Because this is a system attribute, it does not generate a new CGR until the CATPart is put into visualization mode.
Was this helpful?