Entering GCO Attribute Values

As installed, the GCO object for an integration contains the values required for a typical business process.

You can update the values using the user interface as described in Setting Global Preferences, or you can update the values using ENOVIA Matrix Navigator. See the Matrix Navigator Guide for details on editing objects.

If you only installed the Integration Exchange Framework, and not Designer Central, you need to follow this procedure. In addition, some GCO attributes can only be updated in Matrix Navigator, and cannot be edited from the Designer Central user interface.

When entering a system (for ENOVIA) or summary (for CSE) attribute as a value, enclose it in $$, such as $$Description$$. When mapping attributes, you can also use MQL select expressions (see About Syntax for Mapping Types and Relationships).

When entering attribute values, start with the Rule to Apply (either DEFAULTVALUE or ENFORCED) as follows:

(DEFAULTVALUE)SW Component|Design Policy,Versioned Design Policy

(ENFORCED)SW Component|Design Policy,Versioned Design Policy

Attributes that start with IEF-Pref- are copied to the LCO when the collaborative product is assigned to a user, and can be changed for individual users by editing the LCO.

  1. In Matrix Navigator, open the attributes of the MCADInteg-GlobalConfig object, for the needed collaborative product, for editing.

  2. Edit the value for any attribute as required. The available attributes are:


    • Attribute: MCADInteg-CADToMxAttribMapping

      Function: Defines the CAD-to-Matrix attribute mapping.

      Syntax: CAD-Type,CAD-Attribute|Matrix-Type,Matrix-Attribute

      CAD Type values: component, componentInstance, componentFamily, assembly, assemblyInstance, assemblyFamily, drawing and ALL.

      Examples:

      component,Test01|SW Component,Test01

      component,$$Author$$|SW Component,Author

      component,$$Comments$$|SW Component, $$Description$$

      Do not map the Title attribute. This attribute is required for Common Document Model functionality. The "Title" attribute is not supported in the Matrix side of the MCADInteg-CADToMxAttribMapping. If present in the mapping, it is ignored during attribute synchronization.

    • Attribute: IEF-CADToMxMandatoryAttrMapping

      Function: Define attributes to be copied for attribute synchronization on checkin

      Syntax: CADAttribute,value,mandatoryValue

      where mandatoryValue is one of these values:

      • mandatory--values are always synchronized / copied from the GCO. If no value is specified in GCO, then the checkin / save to ENOVIA operation will fail with an appropriate error message.
      • default-- If attribute value is not set on file, then the value from GCO is synchronized / copied. If value is set on file, then the value on file is synchronized / copied. If no value is specified (neither on the CAD file nor in the GCO), then checkin / save to ENOVIA operation will fail with an appropriate error message.
      • null - When an attribute is defined as "null", it is compulsory that the user specifies some value for this attribute on the CAD file. This value specified by the user on the CAD file is synchronized / copied to the object. If no value is specified on the CAD file, then checkin / save to ENOVIA operation will fail with an appropriate error message.

      Example:

      $$Subject$$,companyABC,mandatory

      Test01,alwaysCopy,mandatory

      $$Comments$$,drawing by ABC,default

      Test01,defaultValue,default

      $$Author$$,,null

      Test01,,null

    • Attribute: MCADInteg-FileReadOnlyBehavior

      Function: This attribute controls the read-only behavior of designs

      Possible Values


      • True--Depending on the lock status of the design object in Designer Central, the file is made read-only or writable.
      • False--No change in behavior.
      • Attribute: IEF-EnforceInstanceNameUniqueness

      Function: Whenever an user checks in a family with instances, the name of the instance object that is created in ENOVIA depends upon the value of this attribute.

      Possible Values:

      • True--The instance object name does not contain family name. For example, if an instance I1 with family F1 is checked in, then the name of the instance object that is created will be I1.
      • False--The instance object name contains family name. For example, if an instance I1 with family F1 is checked in, than the instance object name will be I1(F1).

      Default Value: False

    • Attribute: IEF-TypeRestrictedFeatureMapping

      Function: Used to restrict certain Designer Central features for the user.

      Example:

      SW Component|Rename,Purge

      SW Assembly|Purge

      Default Value: Blank

    • Attribute: IEF-Pref-IEF-BackgroundCheckinDirectory

      Function: Define the temporary directory where design files are kept during background checkin, and where success and failure logs are created. If left blank, Designer Central uses the User Profile Directory.

      Example: For Windows XP, the background checkin directory location is, C:\Documents and Settings\<user>\IEFBackgroundCheckin\BackgroundCheckin<date_time>

      For Windows Vista and Windows 7, the background checkin directory location is,

      C:\Users\<user>\IEFBackgroundCheckin\BackgroundCheckin<date_time>

      Default Value: Blank

    • Attribute: IEF-CreateVersionObjects

      Function: Define whether or not new version objects can be created for a Revision

      Possible Values:


      • True--more than one minor object can be created in any revision stream
      • False--only one minor object can be created in one revision stream and Version column is not displayed in all UI pages

      Default Value: True

    • Attribute: IEF-AdminTables

      Function: Used to define the list of admin tables that will be available in all the custom table views to all the users assigned to the GCO.

      Syntax: AdminTable1|AdminTable2

      Examples: AdminTable|AdminTable2

    • Attribute: IEF-Pref-MCADInteg-DefaultTypePolicySettings

      Function: Define the mapping between ENOVIA Type, DesignPolicy and Version Policy. This mapping shows default values for new objects in the policy columns for the selected ENOVIA Type in the Checkin page. The mapping between ENOVIA Type, Major Policy and Minor Policy as the policies is specific to each Collaborative product.

      Syntax: ENOVIA Type|major object policy,Versioned object Policy

      Example:

      (DEFAULTVALUE)SW Component|SolidWorks Design,SolidWorks Versioned Design

      (ENFORCED)SW Assembly|SolidWorks Design,SolidWorks Versioned Design

    • Attribute: IEF-SourceDetails

      Function: Define the integration to use for the Start Design feature, including an optional CSE version; the version is the integration version, not the CAD tool version

      Syntax: integration|version

      Examples:

      SolidWorks

      SolidWorks|V6R2011

    • Attribute:IEF-Webforms

      Function: List of Webforms forms available to the user.

      Examples:DECObjectProperties

    • Attribute: MCADInteg-TypeChangeMapping

      Function: Define the list of possible type changes entered as a newline-separated list.

      Examples: component|componentFamily

    • Attribute: IEF-Pref-IEF-EnableProgressiveLoading

      Function: Define how structures are loaded into the Checkout page

      Possible Values:


      • True--during checkout or promote, only root level assembly is brought for display in the Checkout or Promote page, User has to expand this node to get the first level children from the database
      • False--entire structure will be brought to Checkout or Promote page

      Default Value: True

    • Attribute:IEF-Pref-IEF-DefaultLateralView

      Function: Define the default lateral view to be applied

      Syntax: [DEFAULTVALUE]LatestVersion

    • Attribute:IEF-Pref-IEF-DefaultVerticalView

      Function: Define the default vertical view to be applied

      Syntax: [DEFAULTVALUE]None

    • Attribute: IEF-Pref-MCADInteg-SelectFirstLevelChildren

      Function: Define whether or not to select first level children when selecting a root node

      Possible Values:


      • True--select the first level children if you select the root node of a structure
      • False--selecting the root node of a structure selects only that node

      Default Value: False

      For this flag to work as expected, MCADInteg-SelectChildItems must be false.

    • Attribute: IEF-Pref-MCADInteg-CheckOutDirectory

      Function: Define the default location for downloading files during checkout

      Default Value: C:\temp

    • Attribute: IEF-EnableRapidFileAccess

      Function: Enable or disable rapid file access (hardlink):

      Possible Values:


      • True--Rapid file access is enabled
      • False--Rapid file access is disabled

      Default Value: False

      See About Rapid File Access for details on implementing this feature.

    • Attribute:IEF-CSELaunchBinaryDetails

      Function: Define the path where the binary file for the CAD tool exists. This path is used to launch the CAD tool when the user clicks Start CAD Tool option from Designer Central.

      Example:

      WINDOWS|mxlaunchCATIAV5.bat

      UNIX|mxlaunchCATIAV5.sh

    • Attribute: IEF-PurgeAllMinorsDuringFinalization

      Function: Purge or retain all the minor objects upon finalization.

      Possible Values:


      • True--Upon finalization, purges all minor objects except the one which is finalized.
      • False--Minor objects are not purged upon finalization.

      Default Value: False

    • Attribute: IEF-FinalizationState

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

      Syntax: Policy|State

      Examples:

      SolidWorks Design|Approved

      Design Policy|Approved

    • Attribute: IEF-Pref-MCADInteg-BackgroundCheckin

      Function: 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: True

    • Attribute: IEF-UserExitEventRegistration

      Function: User Exits help you abort a particular action when the condition fails. The user exits for each event are entered on a single line.

      Syntax: Value1,Value2

      Examples: CheckinPartPre,CheckoutPartPre

      For UG, ProE, and CATIA, values are entered as a space-separated list.

      For SolidWorks, SolidEdge, Microstation and AutoCAD: values are entered as a comma-separated list.

      For more details on IEF-UserExitEventRegistration, see About User Exits.

    • Attribute: IEF-Pref-IEF-DefaultConfigTables

      Function: Maps the custom workspace tables to the Designer Central pages.

      Examples:

      Version$Admin:DECVersionDetails@Baseline$Admin:DECBaselineDetails@ Open$Admin:DECOpenPageDetails@Save$Admin:DECSavePageDetails@PLMTree$Admin:DECPLMTreeDetails

      @Checkin$Default@Checkout$Default@LockUnlock$Default@Promote$Default@SaveAs$Default@DesignChangeReport$Default@StartDesign$Default

      @EBOMSynchronize$Default@RecentlyAccessedParts$Default

      "Default" can be any defined workspace table.

    • Attribute: MCADInteg-NonSupportedCharacters

      Function: Define characters that cannot be used in filenames. If any CAD object with any of these characters in file name is checked in, an error message is displayed and checkin is not allowed.

      Note: This attribute is blank by default in Collaborative Design for Solidworks GCO. Instead, Collaborative Design for Solidworks uses the attribute, IEF-UnsupportedCharacterMapping.

      Example: @ , * ? [ ] # $ { } \" < >

    • Attribute: IEF-UnsupportedCharacterMapping

      Function: This attribute is used to map an entity specific list of unsupported characters. Mappings for the following entities can be made:

      • familybusname:Business object name of a family type object.
      • instancebusname: Business object name of an instance type object.
      • busname: Business object name of all other object types except family, instance, workspace/folder object.
      • foldername: Business object name of Workspace and Workspace folder.
      • filename: Name of the actual file.

      Note: This attribute is used by Collaborative Design for Solidworks only.

      Syntax: The mapping between entity type and unsupported characters is defined in the following format:

      familybusname| <LIST OF UNSUPPORTED CHARACTERS> 
instancebusname|<LIST OF UNSUPPORTED CHARACTERS>
busname|<LIST OF UNSUPPORTED CHARACTERS>
foldername|<LIST OF UNSUPPORTED CHARACTERS>
filename|<LIST OF UNSUPPORTED CHARACTERS>

      Default Mapping:

      familybusname|()
instancebusname|/
busname||"#@$&%,*?<>[]
filename|/\:*?"<>|@'#$&%[]
foldername|/\:

      Note: familybusname, instancebusname, and foldername entities are the super-sets of the busname entity and these entites define additional unsupported characters other than busname in their mapping. For example, restricted characters for folder will be the combination of unsupported characters of busname and foldername entity, so by default, unsupported character for foldername will be | " # @ $ & % \ / : * ? < >.. This is also applicable for familybusname and instancebusname.

    • Attribute: IEF-Pref-MCADInteg-ApplyToChildren

      Function: Enable or disable application of choices from parent to child nodes

      Possible Values:


      • True-- choices made for the parent node are applied to its child nodes
      • False--choices made for the parent node are not applied to its child nodes.

      Default Value: (DEFAULTVALUE)false

    • Attribute: IEF-AllowLeapFroggingInCheckin

      Function: Enable or disable the ability to check in older version of designs if a higher version exists, such as occurs when one user checks out a design, then another user checks out the same design, makes changes, and checks it in. When the first user tries to check in changes, this attribute determines what happens

      Possible Values:


      • True--Users can check in older version of the file, creating a version higher than any others in the revision stream
      • False--Users cannot check in older versions of the file; even to other revision streams of the design

      See About Lock Behavior for a discussion about how the various attributes related to locks affect the user's process.

    • Attribute: IEF-EBOMSync-RegistryTNR

      Function: Define the EBOM Synch configuration object using the type, name, and revision

      Syntax: ENOVIAType|Name|revision

      Default Value: MCAD-EBOMSyncConfig|MCAD-EBOMSyncConfig|-

      If you created subtypes of this object to configure it for your business processes (see Configuring the EBOM Configuration Object), use that name for the ENOVIA subtype.

    • Attribute: IEF-EBOMProxyJPOName

      Function: Proxy JPO Name which is used to call EBOM Syncronization on multiple cad objects

      Default Value: IEFEBOMProxy

    • Attribute: MCADInteg-TypeFormatMapping

      Function: Maps CAD type to ENOVIA type and format

      Syntax: CADType|ENOVIAType,format

      Examples:

      component|SW Component,prt

      component|SW Component,prt

      assembly|SW Assembly,asm

      drawing|SW Drawing,drw

    • Attribute: IEF-Pref-MCADInteg-LockObjectOnCheckin

      Function: Enable or disable the ability to retain lock after checkin

      Possible Values:


      • True--Users can choose to retain the lock on objects when checking in
      • False--Users can not retain the lock.

      Default Value: False

    • Attribute: IEF-Pref-MCADInteg-ViewRegistryName

      Function: Set the registry name to indicate which View Registry object sets the lateral and vertical views

      Examples: SWViewRegistry

      Default Value: DefaultViewRegistry

      See Creating or Editing Checkout Views Registry.

    • Attribute: IEF-Pref-IEF-DefaultWebforms

      Function: Maps default webforms for Designer Central pages.

      Examples: Open$DECObjectProperties@Properties$DECObjectProperties

    • Attribute: IEF-Pref-MCADInteg-CopyRelAttribOnCheckin

      Function: Enable or disable copying of relationship attributes at checkin

      Possible Values:


      • True--relationship attributes are copied on check in.
      • False--relationship attributes are not copied on check in.

      Default Value: (DEFAULTVALUE)false

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

    • Attribute: MCADInteg-MxToCADAttribMapping

      Function: Map ENOVIA-to-CAD attributes for attribute synchronization during checkout (attributes must exist). The user can choose whether or not to perform the attribute sync.

      Syntax: ENOVIA-Type,ENOVIA-Attribute|CAD-Type,CAD-Attribute

      When mapping the revision attribute for an unfinalized minor object, you can use either of these formats:


      • ENOVIA-Type,$$revision$$|CAD-Type,CAD-Attribute or
      • ENOVIA-Type,$$Major_Revision$$|CAD-Type,CAD-Attribute

      When the object is not finalized, the first, $$revision$$, maps the ENOVIA minor object to the CAD file; the second, $$Major_Revision$$, maps the ENOVIA major object to the CAD file. Mapping for these attributes is supported from ENOVIA to the CAD file, not from the CAD file to ENOVIA.

      Only use $$revision$$ OR $$Major_Revision$$ for an object type; do NOT use both.

      All the attributes listed in the MCADInteg-MxToCADAttribMapping are displayed as search fields in ENOVIA Open dialog box in the CAD Collaborative products. Only text based search is allowed using the fields added using this attribute. The system attributes are not displayed. For example, if the string

      SW Component,Test01|component,MX_ATTRIB_TEST

      is added to MCADInteg-MxToCADAttribMapping, then Test01 is added as a search criteria in ENOVIA Open dialog box.

      Examples:

      For system to system mapping:

      SW Component,$$description$$ |component,$$Comments$$

      Note that the attribute mapping of "description" string must be in lowercase. The mappings for System attributes must always be in lower case on the Mx side.

      For system to custom mapping:

      SW Component,$$Major_Revision$$ |component,rev

      For custom to custom mapping:

      SW Component,Test01|component,Test01

    • Attribute: IEF-Pref-MCADInteg-WarnForFileOverwrite

      Function: Enable or disable warning if files will be overwritten during checkout

      Possible Values:


      • True-- warning for overwriting the file appears during checkout
      • False--no warning displays

      Default Value: True

    • Attribute: MCADInteg-RenameFilesInServer

      Note: This is a system level attribute and should not be altered.

      Function: Enable or disable renaming of files on the server when user performs a Rename or Save As action

      Possible Values:


      • True--the files are renamed on the Server side during Rename and SaveAs
      • False--no file renaming operation is done on the Server side during Rename and SaveAs.

      Default Value: True

    • Attribute: IEF-Pref-MCADInteg-CreateVersionOnCheckin

      Function: 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: True

    • Attribute: IEF-PreferencesPageLayoutJPO

      Function: Name of the JPO that creates the page layout for the preference page (do not change unless you create a custom JPO)

      Default Value: IEFPreferencesPageLayout

    • Attribute: IEF-Pref-MCADInteg-CheckOutDirectory

      Function: Set the default Checkout directory. Users can change their default Checkout directory from the Checkout or Preferences page

      Default Value: c:\temp

    • Attribute: MCADInteg-RelMapping

      Function: Map the CAD relationship to ENOVIA relationship

      Syntax: CADRelationship|direction,MatrixRelationship

      direction is to or from; use symbolic names for the ENOVIA relationship

      Examples:

      CADSubcomponent|to, CAD SubComponent

      CADDrawing|from, Associated Drawing

    • Attribute: IEF-TypeTemplateMapping

      Function: Map CAD types to ENOVIA template types for the Start Design function

      Syntax: CAD_TYPE|TEMPLATE_TYPE

      Example:

      component|SW Component Template

      assembly|SW Assembly Template

      drawing|SW Drawing Template

    • Attribute: IEF-Pref-IEF-UseBulkLoading

      Function: Sets the default state of the Use Bulk Loading check box on the Checkin page to enable or disable bulk loading. Only users with the Integration Bulk Loader role can access this capability.

      This attribute is supported only for ENOVIA Collaborative Design for CATIA V5.

      Possible Values:


      • True--applies Bulk loading during Checkin, bypassing all the collaborative rules.
      • False--no bulk loading is allowed.

      Default Value: False

    • Attribute:IEF-Pref-IEF-ApplyViewToChildrenOnly

      Function: Setting to apply the view to child nodes during checkout

      Possible Values:


      • True--applies views to child nodes during checkout.
      • False--views are not applied to child nodes during checkout.

      Default:[DEFAULTVALUE]true

    • Attribute: MCADInteg-MxToCADRelAttribMapping

      Function: Map ENOVIA relationships to CAD relationships

      Syntax: Matrix-Relationship-Type, Matrix-Attribute|CAD-Relationship-Type, CAD-Attribute

      Examples:

      CAD SubComponent,Spatial Location|CADSubcomponent,relativeXform

      The relativeXform attribute represents the relative transform of a component with respect to its immediate parent assembly. Do not change this name. The mapped ENOVIA attribute can be any attribute defined on the CAD SubComponent relationship. The Local Configuration Object includes these attributes:


      • MCADInteg-CopyRelAttribOnCheckout
      • MCADInteg-CopyRelAttribOnCheckin

      These attributes allow you to enable/disable this feature on an individual user basis. See Entering LCO Attribute Values.

    • Attribute: MCADInteg-CreateDerivedOutputObj

      Function: Defines if derived outputs are associated to the parent object using a relationship to another object, or as a file checked into the parent object

      Possible Values:

      • True--Designer Central creates an object for each derived output formats and connects it to its respective parent CAD Model using the Derived Output relationship
      • False--the Derived Output file is checked in into its parent CAD Model in a different format

    • Attribute: MCADInteg-TypeDerivedOutputMapping

      Function: Map the business type to derived output types

      Syntax: CADBusinessType|DerivedOutputType

      DerivedOutputType can be a comma-separated list of the types that have been defined for the specified object.

      Example:

      component|image_jpg,png,image_tif,cgr

    • Attribute:IEF-Pref-IEF-SelectedBackgroundDerivedOutputs

      Function: Enables or disables the selection of background derived outputs in the Preferences page.

      When set to (DEFAULT)none, the checkboxes for each derived output file type under Selected Background Derived Outputs column in the Preferences page is available for selection.

      When set to (ENFORCED)none, the selection is disabled for all options under Selected Background Derived Outputs column in the Preferences page.

      Default Value: (ENFORCED)none

    • Attribute: IEF-Pref-MCADInteg-LockObjectOnCheckout

      Function: Enable or disable the default setting for lock object on checkout

      Possible Values:


      • True--Object is locked by default (but can be changed)
      • False--Object is not locked by default

      Default Value: False

    • Attribute: IEF-Pref-MCADInteg-SelectedDerivedOutputs

      Function: 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.

      Syntax:

      Integration Name1|<derived output format1>,<derived output format2>

      Integration Name2|<derived output format2>,<derived output format3>

      Example:

      SolidEdge|image_jpg,image_tif

      SolidWorks|cgr,image_jpg,image_tif

    • Attribute: IEF-Pref-MCADInteg-LoadObjectsInCADTool

      Function: Defines whether or not checked out files are loaded into the CAD tool, or checked out to a directory on the user's local computer. This attribute works with the Load Files on Checkout check box on the Checkout page.

      This is not supported in Collaborative products using Native UI.

      Possible Values:


      • True--loads checked out objects into the CAD tool
      • False--the files are checked out to the directory

      Default Value: True

    • Attribute:IEF-Pref-IEF-SelectedManualDerivedOutputs

      Function:

      Holds the preference for the Selected Manual Derived Outputs option. The specified derived outputs have to be manually created and placed in the checkin directory, from where they are picked by the integration and checked in.

      Syntax:

      Integration Name1|<derived output format1>,<derived output format2>

      Integration Name2|<derived output format2>,<derived output format3>

      Example:

      SolidEdge|image_jpg,image_tif

      SolidWorks|cgr,image_jpg,image_tif.

    • Attribute:IEF-Pref-IEF-DefaultFolder

      Function: This value is polulated when the administrator specifies a default folder through the Global Preferences.

      Syntax:

      (DEFAULTVALUE)<FolderType>,<FolderName>,<Revision>

      Example:

      (DEFAULTVALUE)Workspace Vault,F1,643C83190000240C4C8867FE000003DE

      Default Value: [DEFAULTVALUE]

    • Attribute: MCADInteg-ExpandedSubComponent

      Function: Define whether to use multiple CAD SubComponent relationships between each assembly and its shared components, or to use the Quantity attribute on the relationship. The default value is TRUE.

      Note: Once a value (TRUE or FALSE) is set for this attribute, it is strongly recommended that this value is not modified, since these changes will impact the way data structures are created in ENOVIA and they will not be applied on any data created before the value was changed.

      Possible Values:


      • TRUE--create a CAD SubComponent relationship between the shared component and the assembly for each occurrence of the shared component.
      • FALSE--create one CAD SubComponent relationship between assembly and shared component, and set the Quantity attribute to the number of occurrences of the shared component.
    • Attribute: MCADInteg-TypeClassMapping

      This is a system level attribute and this attribute is generally not modified.

      Function: Define the class for business types (can provide a comma-separated list)

      Syntax: BusinessTypeClass|CADBusinessType

      Examples:

      TYPE_CADMODEL_LIKE|assembly, component, drawing, assemblyFamily, componentFamily

      TYPE_COMPONENT_LIKE|component,componentInstance

      TYPE_ASSEMBLY_LIKE|assembly,assemblyInstance

      TYPE_FAMILY_LIKE|assemblyFamily,componentFamily

      TYPE_INSTANCE_LIKE|assemblyInstance,componentInstance

      TYPE_DERIVEDOUTPUT_LIKE| preview

      TYPE_COMPONENT_FAMILY_LIKE|componentFamily

      TYPE_ASSEMBLY_FAMILY_LIKE|assemblyFamily

    • Attribute: IEF-Pref-MCADInteg-DeleteLocalFileOnCheckin

      Function: Sets the default state of the Delete Local Files check box on the Checkin page.

      Possible Values:


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

      Default Value: False

    • Attribute: MCADInteg-EnableHashcodeComputation

      Function: Enable or disable hashcode computation during checkin and checkout

      Possible Values:


      • True--Hashcode computation enabled and the file transfer happens only after comparing the hashcode value of the local file and the hashcode stored in the corresponding business object in the database
      • False--No hashcode computation is done

      Default Value: False

    • Attribute: IEF-Pref-MCADInteg-CopyRelAttribOnCheckout

      Function: Enable or disable copying of relationship attributes at checkout.

      Possible Values:


      • True--Copies relationship attributes
      • False--Does not copy attributes

      Default Value: (DEFAULTVALUE)false

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

    • Attribute: IEF-Pref-MCADInteg-ShowDetailsPopUpOnCheckin

      Function: Enable or disable pop-up of details page after checkin

      Possible Values:


      • True--after every Checkin, the new Object Details page for the checked in design is displayed as a pop-up page
      • False--details page does not open after checkin

      Default Value: False

    • Attribute: MCADInteg-CADToMxRelAttribMapping

      Function: Define the CAD-to-Matrix relationship attribute mapping for attribute synchronization during checkin.

      The Title attribute should not be mapped from the CAD Tool to ENOVIA.

      Syntax: CAD-Relationship-Type, CAD-Relationship-Attribute| Matrix-Relationship-Type, Matrix-Relationship-Attribute

      Examples:

      CADSubcomponent,relativeXform|CAD SubComponent,Spatial Location

    • Attribute: MCADInteg-BusTypeMapping

      Function: Map CAD business types to ENOVIA object types

      Syntax: CADType|MatrixType

      Examples:

      assembly|SW Assembly

      component|SW Component

      drawing|SW Drawing

      You can change the ENOVIA type, but not the CAD type. The ENOVIA type can be a comma-separated list requiring the user to select a type when the object is created.

      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.

    • Attribute: IEF-Pref-MCADInteg-SelectChildItems

      Function: Enable or disable the ability to select all children in the Checkin, Promote, SaveAs, and Checkout pages

      Possible Values:


      • True--Enable
      • False--Disable

      Default Value: Enable

    • Attribute: MCADInteg-TypePolicyMapping

      Function: Define the policies available for each ENOVIA object type (can provide a comma-separated list)

      Syntax: Type|Policy

      Examples:

      SW Component|Design Policy

      SW Assembly|Design Policy

      SW Versioned Component|Versioned Design Policy

      SW Versioned Assembly|Versioned Design Policy

      SW Versioned Drawing|Versioned Design Policy

      SW Drawing|CAD Drawing

      SW Engine Component|Design Policy, CAD Model Engine Policy

    • Attribute: MCADInteg-RelationShipClassMapping

      Function: This system-level attribute determines if the relationship should be treated as an Assembly, Family, or External Reference.

      Syntax: CADrelationship|RelationshipClass

      Possible/Default Value:

      CADSubcomponent|AssemblyLike

      CADDrawing|AssemblyLike

      CADInstanceOf|FamilyLike

      JoinPart|AssemblyLike,ExternalReferenceLike

      This attribute is not generally changed.

    • Attribute: MCADInteg-EnableMajorRevCreation

      Function: Enable or disable the requirement to create a major revision during the first checkin

      Possible Values:


      1. True--Uses an existing major object at checkin, or creates the major object if it does not exist
      2. False--Uses an existing major object at checkin, if it does not exist, shows an error message to the user. The Start Design, SaveAs, and Checkin features do not function if this attribute is set to false.

      Default Value: True

    • Attribute: IEF-Pref-MCADInteg-UseZipInFileOperations

      Function: Enable or disable zip compression during checkin and checkout. When enabled, the system uses the zip utility included with Java (platform-independent). No additional zip utility is required on the client or server systems.

      Possible Values:


      1. True--Compress files during checkin and checkout using Zip file compression
      2. False--Do not compress files during checkin and checkout

      Default Value: (DEFAULTVALUE)true

    • Attribute: IEF-Pref-IEF-LocalCheckout

      Function: Set befault behaviour to download files locally during RFA checkout. Incase of locked objects, the file is downloaded to the local disk by default.

      Possible Values:


      1. True.The file is downloaded to local disk during RFA checkout.
      2. False. The file is not downloaded to the local disk. Incase of locked objects, users have the option to change this value during checkout in the Checkout page.

      Default Value: (ENOFORCED)false

    • Attribute: IEF-Pref-IEF-SelectRequiredChildren

      Function: Enable or disable selection of required children during checkout

      Possible Values:


      1. True. The required children are selected upon checkout.
      2. False. The required children are not selected during checkout.

      Default Value: (DEFAULTVALUE)false

    • Attribute: IEF-Pref-IEF-UserDirectoryAlias-Mode

      Function: For CATIA V5 users, choose how to select alias directories

      Possible Values:

      • Current--The directory chooser lists and allows selection of ALIAS directories. If ALIAS directories are not registered by the CSE, then the directory chooser supports system directories but the user must specifically select the system directory using the directory chooser.
      • Allowed--The directory chooser allows selection of system directories as well as ALIAS directories. If ALIAS directories are not registered by the CSE, then directory chooser supports the selection of system directories only.
      • Not Allowed--The IEF applet ignores the ALIAS directories.

    • Attribute: IEF-UsePreviousObjectStore

      Function: Enable for silent checkin

      Possible Values:

      • True--during revision of an object, the files in the new revision are checked in into the store where the previous revision files existed
      • False--the object is checked into default policy store

      Default Value: False

    • Attribute: IEF-CSEDisabledCommandsList

      Function: List menus (comma-separated list) to disable in the CAD tool when connected to ENOVIA (for SolidWorks, SolidEdge, Microstation, and AutoCAD integrations only)

      Syntax: menuname1,menuname2

      Examples: Save,Open

    • Attribute: IEF-PartCADObjectAttrMapping

      Function: Maps between attributes of Part and CAD objects

      Syntax:

      <EC Part Type>,attribute|<ENOVIA Type>,attribute

      Example:

      Part|Originator|SW Versioned Component|Author

      Part|Originator|SW Versioned Assembly|Author

      Part|Test01|SW Versioned Component|$$Description$$

      Part|Originator|SW Versioned Assembly|$$Description$$

    • Attribute: IEF-PartCADRelAttrMapping

      Function: Map attributes on relationships between Part objects to attributes on relationships between CAD objects.

      Syntax: Part,attribute|ENOVIA Type,attribute

      Example:

      EBOM|Reference Designator|CAD SubComponent|Reference Designator

    • Attribute: IEF-ReleasedState

      Function: Set the state of Release for an object.

      Syntax: PolicyName Policy|StateName

      Example: Design Policy|Release

    • Attribute: IEF-CheckObsoleteAcrossRevisions

      Function: Checks for obsolete nodes across revisions during the check in or save operation.

      Possible Values:


      • True-- Save operation checks for obsolete objects in all existing revisions of the object.
      • False--Save operation will NOT check for obsolete objects in all existing revisions of the object. Check for obsolete object is done only in the current revision stream.

      Default Value: True

      Local Workspace Management and Update will not honor the IEF-CheckObsoleteAcrossRevisions flag. Whatever the value of the flag IEF-CheckObsoleteAcrossRevisions, Local Workspace Management always checks for obsolete nodes across object's revision and the Update functionality always updates across object's revision.

    • Attribute: IEF-EnableBatchProcessorForRename

      Function: Enables or disables the ability to rename files in a batch process

      Possible Values:


      1. True--Enables
      2. False--Disables

      Default Value: False

    • Attribute: IEF-Pref-IEF-DeleteFilesBehaviourOnCheckin

      Function: Sets the function that shows on the Checkin page, delete all or delete selected, the user can check or clear the check box

      Possible Values:


      • Delete all local files--All selected files plus files with a status other than Modified or New in the checkin list are deleted after the checkin process
      • Delete selected local files--Only those files that are selected are deleted after the checkin process

      Default Value: Delete selected local files

    • Attribute: IEF-UUIDConflictAdminRole

      Function: For CATIA only: When conflicts occur with IEF-UUID (universally unique identifier) attributes, this role is granted the ability to resolve the conflict of UUID

      Possible Values: Matrix Roles

      Default Value: Integration Administrator

    • Attribute: IEF-CheckUUIDConflict

      Function: For CATIA only: Checks the validity of IEF-UUID (universally unique identifier) attribute of the ENOVIA object before checkin.

      Possible Values:


      • True--Check is done
      • False--Check is not done

      Default Value: True

    • Attribute: IEF-Pref-MCADInteg-PreCheckInEvaluation

      Function: Determines whether or not to execute a JPO that evaluates if an object can be selected for checkin. The return value of the JPO determines whether or not that object can be selected for checkin.

      Possible Values:


      1. True--JPO is used to evaluate selection of objects
      2. False--JPO is not used

      Default Value: (ENFORCED)false

    • Attribute: IEF-Pref-MCADInteg-PreCheckOutEvaluation

      Function: Determines whether or not to execute a JPO that evaluates if an object can be selected for checkout. The return value of the JPO determines whether or not that object can be selected for checkout.

      Possible Values:


      • True--JPO is used to evaluate selection of objects
      • False--JPO is not used

      Default Value: (ENFORCED)false

      Pre-Checkout evaluation functionality is not supported in Collaborative Design products that use immersive UI and therefore will not work for integrations which have an immersive UI. Pre-Checkout evaluation is supported only for ENOVIA Collaborative Design for CATIA V5 version V6R2012.

    • Attribute: IEF-Pref-IEF-DefaultExpandLevel

      Function: Defines the default expand level shown on the Checkin, Checkout, and Promote pages.

      Default Value: 1

    • Attribute: IEF-Pref-IEF-AllowAutoGenerationForManualDerivedOutput

      Function: Defines whether or not to automatically generate a derived output file if the user selected manual generation but the manually-generated file does not exist in the defined location

      Possible Values:


      • True--Generates the derived output for a design if the manually-generated file cannot be found
      • False--Does not generate derived output; if the manually-generated file cannot be found, no derived output is checked in with the design.

      Default Value: True

    • Attribute: IEF-MappedInterfaceAttributes

      Function: Lists the interface attributes mapped in the IEF-CADToMxMandatoryAttrMapping attribute to prevent checkin from failing if the attributes are not present. If present, the listed attributes are updated after checkin.

      Possible Values: A comma-separated list of interface attributes mapped in the IEF-CADToMxMandatoryAttrMapping attribute

      Example: $$Author$$,mandatory

    • Attribute: IEF-AssignCADModelNameFromPart

      Function: Determines if the Assign Part column shows on the Checkin page, and if so, uses the selected Part name to name the CAD object being checked in for that Part. The true value is supported only for CATIA V5 collaboration tool. For other CAD tools, this value can be changed to true after the client-side extensions are installed.

      Possible Values:


      • True--Shows the Assign Part column
      • False--Hides the Assign Part column

      Default Value: False

    • Attribute: IEF-EBOMSynchOnDesignCreation

      Function: Defines whether or not to the EBOM synchronization process is initiated whenever a CAD object is checked in

      This attribute is supported for Checkin, Save As and Start Design features.

      Possible Values:


      • True--EBOM Sync will be done whenever a CAD object is checked in
      • False--EBOM Sync must be manually initiated

      Default Value: False

    • Attribute: IEF-DerivedOutputParameterObjTypeMapping

      Function: Maps a Derived Output Parameter object to the derived output types it supports. Displayed in the Derived Output page (when checking in designs) as the list of Parameter Objects associated with a specific derived output format.

      Syntax: DerivedOutputType|ParameterObject

      where:


      • DerivedOutputType--The image format used for derived output
      • ParameterObject--The type, name, revision of the Derived Output Parameter object

      Example:

      image_jpg|Image DOP Parameter

      cgr|CGR DOP Parameter

      image_tif|Other DOP Parameter

    • Attribute: IEF-DerivedOutputTypeDefaultParameterObjectMapping

      Function: Defines the default derived output type for Derived Output Parameter objects. Shows on the Derived Output dialog (when checking in designs) as the default Parameter Objects for a specific derived output format.

      Syntax: DerivedOutputType|DefaultParameterObject

      where:


      • DerivedOutputType--The image format used for derived output
      • DefaultParameterObject--The type, name, revision of the Derived Output Parameter object to be used as the default

      Example:

      image_jpg|Image DOP Parameter,myImageDOPParameterObj1,A

      cgr|CGR DOP Parameter,myCGRDOPParameterObj1,A

      image_tif|Other DOP Parameter,myOtherDOPParameterObj1,A

    • Attribute: IEF-MassPromote-RegistryTNR

      Function: Stores the Type, Name, and Revision of the Mass Promote configuration object.

      Default: IEF-MassPromoteConfig|IEF-MassPromoteConfig|-

    • Attribute: MCADInteg-FileReadOnlyBehavior

      Function: This attribute governs the Read-Only file behavior.

      If "MCADInteg-FileReadOnlyBehavior" flag is set to "TRUE" then depending on the lock status of the design object in Designer Central, the file is made read-only or writable.

      If the flag is set to "FALSE", then there are no behavior changes to any feature.

      See Behavior Changes - Read Only Flag section on details of impact of this attribute on the features.

  3. Save any changes.

  4. If the GCO you edited had been assigned to any users, update the assignment as described in Updating Assignments and Assigning GCO.