Attributes in MxCATIAV5-GlobalConfig Object

This section lists the attributes in MxCATIAV5-GlobalConfig and its usage.

IEF-AssignCADModelNameFromPart

This attribute is CATIA V5 specific. This boolean flag determines whether to create the name of a new CATIA document from the name of the part assigned to the new CATIA document at Checkin.

The flag is mandatory only during the first Checkin. In subsequent Checkins, the Assign Part column is displayed, but the values cannot be modified for existing CATIA objects. By default this flag is false.

If this flag is TRUE, the target name (filename and part number) of the new CATIA document is assigned the same name as the assigned Engineering part. This prevents mismatches between the object in ENOVIA and the Engineering Central part. This can require renaming the CATIA files. The part associated with the new CATIA model can be an existing part, already in the ENOVIA database, or a newly created part.The CAD models on the CATIA side will be renamed only for CATParts and CATProducts, based on the name of the assigned part. Other CATIA types are not renamed, because they do not participate in the BOM structure.This option does not support V4 models.

If you attempt to assign the same part to more than one item listed in the Checkin page, only one of the items is renamed. The renaming is not sequence dependent. If Checkin fails, the name of the CATIA model does not revert to its original name.

MCADInteg-RelationShipClassMapping: (Multiline String)

This attribute classifies the relationships. This attribute is generally not altered. This is a system level attribute that tells Designer Central how it should treat each relationship. The left side of each entry denotes the integration-defined relationship and the right side denotes the class of the relationship.

The default value for the relationship classes are as follows

assemblyComponent|AssemblyLike

drawing|AssemblyLike

designTable|AssemblyLike

analysis|AssemblyLike

process|AssemblyLike

catalog|AssemblyLike

mml|AssemblyLike,ExternalRefereneLike

DerivedOutputOf|DerivedOutputLike

MCADInteg-TypePolicyMapping: (Multiline String)

This attribute defines the policies to use for each type.

Each entry is a map of two strings separated by a separator "|". The left side of the "|" is the type and the right side is the policy that controls it. Multiple policies can be defined for each type in which case they must be separated by commas. This mapping is shown to the user in the checkin dialog. In the case where multiple policies have been mapped for a given type the user will have to select the policy to use on the checkin dialog. Note that the types and policies must exist in ENOVIA.

Default Value:

CATPart|CATIA V5 Design Policy,Design Policy

CATShape|CATIA V5 Design Policy, Design Policy

CATProduct|CATIA V5 Design Policy,Design Policy

CATDrawing|CATIA V5 Design Policy,Design Policy

CATIA V4 Model|CATIA V5 Design Policy,Design Policy

CATIA Design Table|CATIA V5 Design Policy,Design Policy

CATIA CGR|CATIA V5 Design Policy,Design Policy

IGES|CATIA V5 Design Policy,Design Policy

VRML|CATIA V5 Design Policy,Design Policy

CATAnalysis|CATIA V5 Design Policy,Design Policy

CATIA Catalog|CATIA V5 Design Policy,Design Policy

CATProcess|CATIA V5 Design Policy,Design Policy

Versioned CATPart|Versioned CATIA V5 Design Policy,Versioned Design 
Policy

Versioned CATShape|CATIA V5 Versioned Design Policy, Versioned Design 
Policy

Versioned CATProduct|Versioned CATIA V5 Design Policy,Versioned Design 
Policy

Versioned CATDrawing|Versioned CATIA V5 Design Policy,Versioned Design 
Policy

Versioned CATIA V4 Model|Versioned CATIA V5 Design Policy,Versioned 
Design Policy

Versioned CATIA Design Table|Versioned CATIA V5 Design 
Policy,Versioned Design Policy

Versioned CATIA CGR|Versioned CATIA V5 Design Policy,Versioned Design 
Policy

Versioned IGES|Versioned CATIA V5 Design Policy,Versioned Design 
Policy

Versioned VRML|Versioned CATIA V5 Design Policy,Versioned Design 
Policy

Versioned CATAnalysis|Versioned CATIA V5 Design Policy,Versioned 
Design Policy

Versioned CATIA Catalog|Versioned CATIA V5 Design Policy,Versioned 
Design Policy

Versioned CATProcess|Versioned CATIA V5 Design Policy,Versioned Design 
Policy

Derived Output|Derived Output Policy

MCADInteg-RelMapping: (Multiline String)

This attribute maps integration-defined relationships to ENOVIA relationships.

Each entry is a map of two strings separated by a separator "|". The string on the left is the integration-defined relationship. The string on the right is the ENOVIA relationship; a comma separated list of two entries. The second entry (e.g. CAD SubComponent) is the name of corresponding relationship in ENOVIA. The first entry indicates the direction of arrowhead for the relationship, either to or from.

Default Value:

assemblyComponent|to, CAD SubComponent

drawing|from, Associated Drawing

designTable|to, CatDesignTable

analysis|to, CatAnalysis

process|to, CatProcess

catalog|to, CatCatalog

DerivedOutputOf|to, Derived Output

MCADInteg-BusTypeMapping: (Multiline String)

This maps the business types from CATIA V5 to ENOVIA.

The types on the left side of the separator cannot be modified but the ENOVIA types they are mapped to can be modified. If a CATIA V5 type maps to more than one ENOVIA type, the user will be have to choose the type at the time of initial checkin from the checkin dialog. If more than one ENOVIA type is mapped it must be a comma- separated list. Additionally, many-to-one mapping is supported where more than one CATIA V5 type maps to the same ENOVIA type.

Default Value:

assembly|CATProduct

component|CATPart

drawing|CATDrawing

shape|CATShape

v4model|CATIA V4 Model

designTable|CATIA Design Table

cgr|CATIA CGR

iges|IGES

vrml|VRML

analysis|CATAnalysis

catalog|CATIA Catalog

process|CATProcess

image_jpg|Derived Output

image_postscript|Derived Output

All derived output cad types with name starting with "userfile_" mapped in the MCADInteg-BusTypeMapping attribute of the GCO will have the automatic and background selection disabled. These options are disabled because these derived outputs need to be generated explicitily by the user.

MCADInteg-TypeFormatMapping: (Multiline String)

This attribute maps the integration type to the ENOVIA type and format.

Each entry is a map of two strings separated by a separator "|". The string on the left is the integration. The string on the right is the ENOVIA type and its format. For example, if the entry is component|CATIA Model,prt, then components are checked into the prt format.

Default Value:

component|CATPart,prt

assembly|CATProduct,asm

drawing|CATDrawing,drw

v4model|CATIA V4 Model,prt

designTable|CATIA Design Table,prt

cgr|CATIA CGR,prt

iges|IGES,prt

vrml|VRML,prt

analysis|CATAnalysis,prt

catalog|CATIA Catalog,prt

process|CATProcess,prt

component|CATPart Template,prt

assembly|CATProduct Template,asm

drawing|CATDrawing Template,drw

image_jpg|CATPart,Image

image_jpg|CATProduct,Image

image_jpg|CATDrawing,Image

image_jpg|Derived Output,Image

postscript|CATPart,PS

postscript|CATProduct,PS

postscript|CATDrawing,PS

postscript|Derived Output,PS

shape|CATShape,prt

stlOutput|CATShape,STL

igesOutput|CATShape,IGES

modelOutput|CATShape,MODEL

stepOutput|CATShape,STEP

3dmapOutput|CATShape,3DMAP

cgrOutput|CATShape,CGR

wrlOutput|CATShape,WRL

pngOutput|CATShape,PNG

image_jpg|CATShape,Image

postscript|CATShape,PS

tifOutput|CATShape,TIF

MCADInteg-CADToMxRelAttribMapping: (Multiline String)

This is the CATIA V5 to ENOVIA attribute mappings for relationships.

This is also used for the attribute synchronization operation during checkin but only if the users' local preference is set up to copy relationships attributes on checkin. By default, this option is Enforced.

Default Value:

assemblyComponent,relativeXform|CAD SubComponent,Spatial Location

assemblyComponent,componentID|CAD SubComponent,Reference Designator

assemblyComponent,UUID|CAD SubComponent,IEF-UUID

Default Values in both MxToCAD and CADToMx are mandatory mappings which should not be removed. It enable to have a mapping of instance name, 3DPosition and UUID.

MCADInteg-MxToCADRelAttribMapping: (Multiline String)

This is the ENOVIA to CATIA V5 attribute mappings for relationships.

This is also used for the attribute synchronization operation during checkout but only if the user's local preference is set up to copy relationships attributes on checkout. By default, this option is Enforced.

Default Value:

CAD SubComponent,Reference Designator|assemblyComponent,componentID 

CAD SubComponent,Spatial Location|assemblyComponent,relativeXform

CAD SubComponent,IEF-UUID|assemblyComponent,UUID

Default Values in both MxToCAD and CADToMx are mandatory mappings which should not be removed. It enables the mapping of instance name, 3DPosition and UUID.

The following special relationship attribute mapping can be used to store the ENOVIA relationship id of an assembly component in CATIA V5 so relationships can be preserved on checkin. This is useful when versions are not created and relationship attributes have been added in ENOVIA that must be retained.

CAD SubComponent,$$id$$|assemblyComponent,mxid

MCADInteg-CSETypeToCADAttributeMapping

This flag sets the default value for the Type field in the Checkin page.

The syntax of this attribute is:

<CSEType>|<CADAttribute>, Default Value: NULL

If this attribute is not set, or if it contains an invalid value, the options in the Type field are determined by the first Type listed in the MCADInteg-BusTypeMapping attribute. For example, if the first item in MCADInteg-BusTypeMapping is:

assembly|CATProduct,MOD1,SRB4

Then CATProduct, MOD1, and SRB will be displayed in the Type field in the Checkin page. The first value given, CATProduct, is the default value in the Type field.

MCADInteg-CSETypeToCADAttributeMapping is type:

<CSEType>|<CADAttribute>

where CSEType can be any CSE Type listed on the left-hand side of the MCADInteg-BusTypeMapping attribute,



and CADAttribute can be any of the supported System Properties, like sys:Description. Therefore, you could set MCADInteg-CSETypeToCADAttrbuteMapping to something like this:

v4Model|sys:Definition

assembly|sys:Definition

For example:

Set MCADInteg-CSETypeToCADAttributeMapping to:

component|sys:Description

In CATIA, update the Description property of the part you plan to checkin with:

CATPart

Valid values in the Type field will include those values present on the right side of the pipe (|) in MCADInteg-BusTypeMapping. If MCADInteg-BusTypeMapping includes:

component|ZSB-Part, CATPart

then both ZSB-Part and CATPart are valid values for the Type field of the Checkin page.

Check in the part for the first time. In the Type field of the Checkin page, CATPart is displayed as the default value.

If the same CSEType is mapped to different values, for example:

assembly|sys:Description

assembly|sys:Definition

one of the mappings in MCADInteg-CSETypeToCADAttributeMapping is used and the other mappings ignored.

If validation of the mappings in MCADInteg-CSETypeToCADAttributeMapping fails, the default value will be determined as if CSETypeToCADAttributeMapping was not set. That is, it will be determined based only on MCADInteg-BusTypeMapping.

MCADInteg-NonSupportedCharacters: (Multiline String)

This attribute holds the characters that are not supported in file names.

If any CATIA V5 file getting checked in has any of the characters listed in this attribute a message is shown to the user and checkin is not allowed.

MCADInteg-ExpandedSubComponent: (Boolean, Value: TRUE)

This flag controls the rolling up behavior for "CAD SubComponent" relationship.

The value of this flag is always set to TRUE. If there are shared components in an assembly, then multiple "CAD SubComponent" relationships are created between the shared component and the assembly.

MCADInteg-CreateDerivedOutputObj: (Boolean, Default Value: FALSE)

This flag determines how Derived Outputs are represented in the integration.

If this flag is set to true, the integration creates an object for each of the Derived Outputs and connects it to its respective parent CAD Model using the "Derived Output" relationship. If this flag is set to false, the Derived Output file is checked into its parent CAD Model in a different format.

This attribute controls how cgr files are stored. If it is true, the cgr is stored so that you can view CgrViewable type objects in the Checkout panel and select them for check out (which is necessary for working in visualization mode). If this attribute is set to false, you cannot view (and therefore not select) cgr files in the checkout panel.

MCADInteg-TypeDerivedOutputMapping: (Multiline String)

This mapping determines the type of the Derived Output object that is to be created (if MCADInteg-CreateDerivedOutputObj is true) for mapped business types.

This attribute contains the mapping between business types and Derived Output types. Each mapping contains two entries separated by a "|". The entry on the left is a business type in the integration context and the entry on the right contains Derived Output type(s). If there are multiple Derived Output types they must be separated by commas.

shape|cgrOutput,igesOutput,stepOutput,stlOutput,modelOutput,3dmapOutpu
t,wrlOutput, pngOutput,image_jpg,postscript,tifOutput

MCADInteg-FeatureJPOMapping: (Multiline String)

This attribute contains the mapping of the feature and the name of the JPO that is to be invoked for that feature.

Default Value:

EBOMSynchronize|MCAD-EBOMSynchronize

Finalize|MCAD-Finalize

UndoFinalize|MCAD-UndoFinalize

Purge|MCAD-Purge

Rename|MCAD-Rename

SaveAs|MCAD-SaveAs

The string on the left represents the operation, like finalize, EBOM synchronize etc. The value on the right is the name of program, a JPO that gets invoked that has all the logic for the operation implemented. All the programs indicated in the above setting are installed by the out-of-the box installation.

MCADInteg-TypeClassMapping: (Multiline String)

This attribute defines the class for business types. This is a system level attribute and this attribute should not be modified.

This attribute has two entries separated by a "|". The entry on the left defines the class for the business types, while the entry on the right contains a comma-separated list of integration types.

Default Value:

TYPE_CADMODEL_LIKE|assembly,component,drawing,v4model,designTable,cgr,
iges,vrml,analysis,catalog,process

TYPE_COMPONENT_LIKE|component

TYPE_ASSEMBLY_LIKE|assembly

TYPE_FAMILY_LIKE|

TYPE_INSTANCE_LIKE|

TYPE_DERIVEDOUTPUT_LIKE|image_jpg,postscript

TYPE_COMPONENT_FAMILY_LIKE|

TYPE_ASSEMBLY_FAMILY_LIKE|

IEF-TypeTemplateMapping (Multiline String)

This attribute holds the mapping of cad types to template types required for start design.

The format for this mapping is:

CAD_TYPE|TEMPLATE_TYPE

Default Value:

component|CATPart Template

assembly|CATProduct Template

drawing|CATDrawing Template

IEF-SourceDetails (String)

This attribute holds the name of the integration and is currently being used for the start design feature.

The CSE version may optionally be provided by appending a "|" to the integration name. The format for this mapping is:

CSE_NAME[|CSE_VERSION]

Default Value:

MxCATIAV5

IEF-Pref-MCADInteg-DefaultTypePolicySettings

Defines the mapping between ENOVIA Type, DesignPolicy and Version Policy.

Function: This mapping shows default values for new objects in the policy columns for the selected ENOVIA Type in the Checkin page. By default, CATIA V5 Design Policy and Versioned CATIA V5 Design Policy is set as values for all CATIA Types.

Example:

(DEFAULTVALUE)CATPart|CATIA V5 Design Policy,Versioned CATIA V5 Design 
Policy

CATShape|CATIA V5 Design Policy, CATIA V5 Versioned Design Policy

IEF-ReleasedState

Set the state of Release for an object.

Syntax: PolicyName Policy|StateName

Default Values:

Design Policy|Release

CATIA V5 Design Policy|Release

IEF-FinalizationState

Define the lifecycle state at which a design is considered finalized; the policy governing the design must have at least 2 states, and the first state must not be the finalization state

Syntax: Policy|State

Example:

Design Policy|Approved

CATIA V5 Design Policy|Approved

IEF-CADToMxMandatoryAttrMapping: (Multiline String)

This attribute allows Administrator to specify mandatory type and mandatory value for the attributes specified inside MCADInteg-CADToMxAttribMapping.

Note that mappings for all the attributes in this section must also be defined in the MCADInteg-CADToMxAttribMapping section.

Mandatory Attributes are supported for the following reasons:


  • Administrator can provide a mandatory value for an attributes, to be set inside ENOVIA; this mandatory value has preference over the value set inside CATIA V5
  • Administrator can provide a default value for an attributes, to be set inside ENOVIA; this default value can be over-written by the CSE if the CSE chooses.
  • Administrator can force CATIA V5 user to provide a value for the attribute inside CATIA V5 document.

To enable this, the format of the mandatory attribute defines the type of the required attribute as discussed below.

The syntax for this mapping is,

attributeName,attributeValue,attributeType

where,


  • attributeName: the name of the attribute, for example sys:description
  • attributeValue: the value of the attribute, for example Bicycle Handle
  • attributeType: the type of value. Possible values for this section are:
  • Mandatory: The value specified in "attributeValue" is used by the CSE as the value of the attribute. CSE overwrites the value of this attributes in the CATIA V5 document with the value specified in "attributeValue". The system administrator MUST provide a value in "attributeValue" since mandatory attributes should always have a value.
  • Default: CSE checks whether the attribute value is specified inside CATIA V5 document. If yes, then the value from the document is read and synchronized to DesignerCentral. If the attribute value is not specified, then CSE picks up the "attributeValue" from the mapping and synchronizes this value to Designer Central. The same value is set on the attribute inside CATIA V5 document.

    Note: The administrator MUST provide a value in "attributeValue" since mandatory attributes should always have a value.

  • NULL: The CSE should search this attribute in the CATIA V5 document and pick its value to synchronize it with the ENOVIA attribute. If an attribute is specified as "NULL" then, user MUST provide a value for such attribute because mandatory attributes should always have a value. The system administrator should not provide any value in the "attributeValue", since it will not be used by the CSE.

The above mandatory attribute rules are applied in the following cases:


  • During checkin operation
  • During ENOVIA V6 > Attribute sync To ENOVIA

IEF-Pref-MCADInteg-BackgroundCheckin

Enable or disable background checkin

Possible Values:

True--Background checkin option will be active by default during checkin

False--The CAD tool is not released until the checkin operation is completed

Default Value: (DEFAULTVALUE)false

IEF-Pref-MCADInteg-SelectedDerivedOutput

Map the list of derived outputs supported by the CAD tool to the listed derived outputs selected by default in the Preferences page and in the Derived Output selection page

Default Value: (DEFAULTVALUE)cgrOutput,pngOutput,image_jpg

IEF-Pref-MCADInteg-CopyRelAttribOnCheckout

Set the default state of the check box on the checkout page to enable or disable relationship attributes to be copied at checkout.

Possible Values:

True--Copies relationship attributes

False--This value for the attribute is still supported but will be deprecated in future releases.

Default Value: (ENFORCED) true

If enabled, you must map relationship attributes using the MCADInteg-RelMapping attribute.

IEF-Pref-MCADInteg-CopyRelAttribOnCheckin

Enable or disable copying of relationship attributes at checkin.

Possible Values:

True--Copying of attributes is done

False--This value for the attribute is still supported but will be deprecated in future releases.

Default Value: (ENFORCED) true

IEF-Pref-MCADInteg-CreateVersionOnCheckin

Set the default state of the Create Version check box

Possible Values:

True--every checkin creates the next version

False--the first object creates a version, and subsequently all the files are checked into the same version overwriting the earlier design

Default Value: (DEFAULTVALUE)true

IEF-Pref-MCADInteg-DeleteLocalFileOnCheckin

Set the default state of the Delete Local Files check box on the user's Checkin page.

Possible Values:

  • True--local files will be deleted after checkin
  • False--local files will not be deleted after checkin

Default Value: (DEFAULTVALUE)false

IEF-CSEDisabledCommandsList

List menus (comma-separated list) to disable in CATIA V5 when connected to ENOVIA.

Syntax: menuname1,menuname2

These menus can be disabled for CATIA V5:


  • StartDesign
  • CheckoutLoad
  • CheckoutInsert
  • CheckinActive
  • CheckinAll
  • QuickCheckinActive
  • QuickCheckinAll
  • LockUnlock
  • AttribSynchFromEnoviaActiveFile
  • AttribSynchFromEnoviaActiveStructure
  • AttribSynchToEnoviaActiveFile
  • AttribSynchToEnoviaActiveStructure
  • RecentlyAccessedDesigns
  • ListVersionsAndRevisions

List Versions option changes to List Revisions if the attribute IEF-CreateVersionObjects is set to FALSE.


  • CheckForUpdateAll
  • CheckForUpdateCurrent
  • ManageWorkspace
  • Preferences
  • Help
  • About

Examples: CheckoutLoad,LockUnlock

This example disables the Checkout > Load and Lock/Unlock in the CAD tool.

The following table lists the changes in syntax for IEF-CSEDisabledCommandsList attribute to disable ENOVIA menu commands for the listed menu items:

Menu Item

Former Keyword

New Keyword

Attribute Synchronization from ENOVIA > Active File

AttribSynchFromMatrixActiveFile

AttribSynchFromEnoviaActiveFile

Attribute Synchronization from ENOVIA > Active Structure

AttribSynchFromMatrixActiveStructure

AttribSynchFromEnoviaActiveStructure

Attribute Synchronization to ENOVIA > Active File

AttribSynchToMatrixActiveFile

AttribSynchToEnoviaActiveFile

Attribute Synchronization to ENOVIA > Active Structure

AttribSynchToMatrixActiveStructure

AttribSynchToEnoviaActiveStructure

List Versions

or

List Revisions

ListVersions

ListVersionsAndRevisions

IEF-CheckObsoleteAcrossRevisions (Default Value: TRUE)

When IEF-CheckObsoleteAcrossRevisions is set to TRUE, ENOVIA checks whether or not the current Major revision is the latest Major revision in ENOVIA V6. It is recommended to set IEF-CheckObsoleteAcrossRevisions to TRUE to evaluate if a newer Major revision is present in ENOVIA V6.

When IEF-CheckObsoleteAcrossRevisions is set to FALSE, this check only indicates if the current Minor version is the latest minor of the current Major revision even if newer Major revisions might be present.

This means that even though there might be a latest Major Revision available in the server, you will only be able to compare their designs with the latest available Minor Version in the current Major Revision tree.

CatPreventCheckinIfStructureContainsNewNotSavedNodes: (Boolean, Default Value: FALSE)

This is an attribute specific to the ENOVIA Collaborative Design for CATIA V5. When this flag is set to True, if the user tries to check in one or more models, the Checkin page is not displayed if any nodes in the design structure have not been saved to disc.

Instead, the user will see a message indicating which files need to be saved. The user can save the necessary files and then checkin the active model or all models. This attribute is only supported for sparseloading = false. See Using sparseloading Attribute section for details on setting sparseloading as false.

CatUpdateInstanceNamesOnRename: (Boolean, Default Value: TRUE)

This is an attribute specific to the ENOVIA Collaborative Design for CATIA V5. Valid values for this attribute are "TRUE" or "FALSE". Existing autonamed instance names will be renamed to make sure that instance names match autoname of corresponding reference part-number.

When this flag is set to TRUE, the integration will update the instance names of renamed objects during the fix up process that occurs on checkout. The higher-level assembly is retrieved to fix up renamed objects. Renamed items that have instances names of the format '<name>.#' will be updated to '<newname>.#' The instance name will not be updated if the format of the instance name does not match this format of '<name>.#' . A '.' must be in the instance name to be updated and the rightmost portion of the instance name must guarantee its uniqueness.

It is recommended that this attribute should be set to TRUE only if the attribute CATUpdatePartNumberOnRename is set to TRUE.

CatUpdatePartNumberOnRename: (Boolean, Default Value: TRUE)

This is an attribute specific to the ENOVIA Collaborative Design for CATIA V5. Valid values for this attribute are "TRUE" or "FALSE". When this flag is set to TRUE, the integration will update the part number properties of renamed objects in CATIA during the fix up process that occurs on checkout.

The part number value will be set to the model name. Attribute mapping settings will be applied AFTER the fix up process. This will happen regardless of the attribute mapping in the GCO object.

In case of Embedded Component, CatUpdatePartNumberOnRename = FALSE is not applicable.

CatSetReadWriteAccessBasedOnLockUnLockOptions: (Boolean, Default Value: FALSE)

This attribute decides whether or not the integration should change the filesystem read/write status of files based on the ENOVIA lock setting.

If TRUE, the integration alters the file system read/write status based on the ENOVIA lock status. For files that are locked, the files are read/write. For files that are unlocked, they are opened as Read-Only in CATIA. When some modifications are made and checked in, then the files are successfully checked in with the modifications because from version 2010, acquirelockoncheckin flag is deprecated which means that all files are temporary locked during check in."

If FALSE, the integration leaves all files as writeable. Note that this will work only during check in, checkout, and lock/unlock operations.

If Designer Central allows to acquire the lock during the check in of unlocked documents, then using this flag will not change the lock status.

CatSetReadWriteAccessBasedOnLockUnLockOptions=TRUE, unlocked documents will be read-only in CATIA, but still modifications to these documents will be saved in ENOVIA during checkin.

This will be also applicable if the user has expilictly opened the file in read-only mode. Since a temporary lock is held on the files during checkin, changes made to these documents will be also saved onto the local checkin directory.

CatDerivedOutputOptions: (Multiline String)

This is an attribute specific to the ENOVIA Collaborative Design for CATIA V5. This attribute defines the user-configurable options of image file generation.

The syntax is:

derived output|option=value,<option=value,?>

Default Value:

image_jpg|delete_on_checkin=yes

postscript|delete_on_checkin=yes

Note:

delete_on_checkin specifies whether or not to delete the derived output file upon successful completion of the checkin operation. If this is set to 'yes' the derived output file will be deleted upon checkin. If this is set to 'no' the derived output file will not be deleted.

CatExcludeTypes: (String)

This is an attribute specific to the ENOVIA Collaborative Design for CATIA V5. This allows specified V5 object types to be ignored by the integration.

For example, to ignore CATDesignTable objects you would set this attribute to designTable. Comma-separate the names for multiple types. The valid type names can be found in the MCADInteg-BusTypeMapping attribute.

CatPreventTypeCheckin: (String)

This is an attribute specific to the ENOVIA Collaborative Design for CATIA V5. This allows the integration to prevent specified V5 object types to be checked into ENOVIA.

For example, to prevent V4 models to get checked in you would set this attribute to v4model. Comma-separate the names for multiple types. The valid type names can be found in the MCADInteg-BusTypeMapping attribute.

CatCheckinAssociatedDrawings: (Boolean, Default Value: FALSE)

This is an attribute specific to the ENOVIA Collaborative Design for CATIA V5. If set to TRUE the integration will checkin drawings of objects in the active structure but only for those drawings that are in session.

If a drawing is not in session the integration cannot check it in.

CatPreventCheckinForUnloadedModels: (Boolean, Default Value: FALSE)

This is an attribute specific to the ENOVIA Collaborative Design for CATIA V5. If this attribute is TRUE checkin operations will be prevented if any models in the structure are not loaded in the session.

If this attribute is FALSE the checkin will be permitted but unloaded models will not be selectable for checkin.

CatDeleteModifiedFilesOnCheckin: (String, Default Value: no)

This attribute is specific to the ENOVIA Collaborative Design for CATIA V5. It defines the behavior of deleting modified files not selected for checkin when the IEF-DeleteFilesBehaviourOnCheckin is set to 'Delete All Local Files'.

This GCO attribute is ignored if IEF-DeleteFilesBehaviourOnCheckin is set to 'Delete Selected Local Files'.

This attribute can be 'no', 'yes', or 'ask'. If this is set to 'no' then modified files not selected for checkin will not be deleted when the structure is checked into ENOVIA. If this is set to 'yes' then modified files not selected for checkin will be deleted when the structure is checked into ENOVIA. If this is set to 'ask' then the user will prompted whether or not to delete the modified files not selected for checkin.

CatObjectLoadingInSession: (String, Default Value: LoadObjectsInSession)

This is an attribute specific to the ENOVIA Collaborative Design for CATIA V5. This controls the behavior of how to handle the loading of objects into the V5 session during Checkin, Lock/Unlock, and RecognizeVersion.

If an object and its children are not loaded in session it is not possible for the integration to gather the required information for the object to be selectable during the command.

This can be set to 'DoNotLoadObjectsInSession' or 'LoadObjectsInSession'. If this is set to 'DoNotLoadObjectsInSession' the unloaded object will not be loaded, nor can its structure be expanded. Unloaded objects are not selectable for checkin into ENOVIA. If this is set to 'LoadObjectsInSession' the integration will load the unloaded objects and they will remain in session after the operation.

Note: Note that cached models are considered unloaded and will not be selectable for checkin if this is set to 'DoNotLoadObjectsInSession'.

CatEnableLoadingInVisuModeInCheckout: (Boolean, Default Value: TRUE)

This attribute controls the generation of cgr files during check in and the extraction of cgr files during checkout (regardless of whetehr the cgr derived output has been selected for either check in or check out.)

This attribute does not control whether the CATIA V5 cache is being used (cache is activated using Tools > Options > Infrastructure > Product Structure > Cache Management.) If you do not wish to use cache mode and you would prefer that cgr files not be automatically generated and extracted (instead they will be controlled by the derived output mechanism), then CatEnableLoadingInVisuModeInCheckout should be set to FALSE.