About Global Configuration Objects
The Administrator can configure X-CAD Design Management
functionality according to the company's business requirements.
You can
configure the defaults for checkin, check out and more.
The MCADInteg-GlobalConfig object (the object type of
the GCO as stored in the ENOVIA database) stores configurations and settings
for each installed integration. For example, you need separate GCOs for
SolidWorks, CATIA, and Solid Edge. Settings are stored as attribute/value
pairs.
The GCO:
- Captures the rules that map the compound document structure in the authoring
tool to object structure in ENOVIA including the CAD type, relationship
type, and attribute mapping.
- Sets global preferences.
- Stores the program name that implements the key functionality.
The GCOs specific to your integrations are installed with X-CAD Design Management. For example, the SWNewArch GCO supports the
ENOVIA/SolidWorks collaborative application. See the Installation and Administrator's
Guide for your collaborative application for the name of the GCO that controls
its defaults and preferences.
Some collaborative applications add additional attributes to the GCO that
may not be included in this guide. In general, this guide defines the
attributes that apply to all collaborative applications and the specific
collaborative application guides provide the details about attributes specific
to that CAD tool.
To configure the GCO, directly edit the GCO by following the instructions in Entering GCO Attribute Values.
About Local Configuration Objects
When an Administrator assigns a collaborative application to
a user, X-CAD Design Management creates an MCADInteg-LocalConfig object (the object type as
stored in ENOVIA) and copies the defaults and preference from the GCO
for that collaborative application.
The LCO also contains the user's preferences
and working set, the file that tracks the objects and files that
the user checks out to a local computer. See the X-CAD Design Management
User's Guide for more information on working sets.
You may never need to edit an LCO--the GCO provides the starting defaults
and the user can update many settings. If you do need to edit the LCO
for a user, follow the instructions in Entering LCO Attribute Values.
About Checkout Views Registry
The Checkout page or the ENOVIA Save dialog box available from
dialog box in native UI, includes Document Iteration (analogous to a lateral view) and Related Documents (analogous to a vertical view) drop-down
lists that let the users change the tree structure.
The items in these
lists call programs that encapsulate business logic to load appropriate
business objects into the Checkout page.
The MCADInteg-CheckoutViewProgramRegistry object named
DefaultViewRegistry Revision 1 can be used as is or
as a sample for creating your own views registry. The DefaultViewRegistry maps names of programs that
the integration applies for displaying Document Version/Related Documents
views on the Checkout page or the Options dialog box available from ENOVIA
Save dialog box in native UI.
See Creating or Editing Checkout Views Registry for details on configuring the Checkout Views
Registry.
About EBOM Config Object
If your implementation includes Engineering BOM Management, you can synchronize CAD drawing
structures with an Engineering Bill of Material.
When a user selects the EBOM Sync function (see the X-CAD Design Management
User's Guide for instructions), this series of JPOs are
invoked:
MCADEBOMSynchronize is the main JPO invoked when
the user clicks the EBOM link. This JPO implements the logic of traversing
the CAD structure. IEFEBOMSyncNewPartCreation contains the logic for
new part object creation and related attribute synchronization.IEFEBOMSyncFindMatchingPart locates matching Parts
that need to be connected to the CAD Model.IEFEBOMSyncConnectParts connects the found Parts
and CAD objects, and executes relationship attribute synchronization.
The default settings for these Program objects suit the standard process
for creating EBOMs from CAD models, and you can configure several attributes
to conform to your specific needs as described in Configuring the EBOM Configuration Object.
|