Global Configuration Objects

The administrator can install a sample Global Configuration Object based on the requirements of the user. For Collaboration for Microsoft, the Global Configuration Object (GCO) is MSOfficeNewArch with TEAM.

The GCOs set by the Server Installation are specific to Collaboration for Microsoft.

Important: If you upgrade the Collaboration for Microsoft server, a new GCO is created and installed on the server. You have to manually update the new GCO with the custom changes made to the previous GCO and use the new GCO.

For a particular GCO to appear in the list of GCOs while performing an Update Assignment operation, MSOffice should be added as a value to the IEF-SourcingDetails attribute in the MSF GCO.

You must only modify the attributes in the Microsoft Office GCO that are listed in the table below.
AttributeDescription

MSOI TypeRelationshipMappings

This attribute maps types to relationships. You must modify it when a type is mapped to a relationship in typeNavigationMappings. You can only map a type to a single relationship so that the document can be saved.

For more information, see Configuring the Content to be Displayed for Each Type.

MSF-MSOIGeneralSearchTypes

This attribute maps the general search types from all Microsoft Office applications to 3DEXPERIENCE. This setting does not map searches for Microsoft Project.

The value of this attribute in the GCO is the default type for search. You can also expand the hierarchy to see subtypes.

MSF-MSPIGeneralSearchTypes

This attribute maps the general search types from Microsoft Project to 3DEXPERIENCE.

MCADInteg-BusTypeMapping

This attribute maps the business types from Collaboration for Microsoft to 3DEXPERIENCE. The Microsoft Office types such as Word, Excel, PowerPoint, and Outlook cannot be changed, but the administrator can change the mapped types such as Microsoft Word Document, Generic Document, and Document. This makes it possible to configure the schema according to the business rules.

If a Microsoft Office type is mapped to more than one 3DEXPERIENCE type, the user must choose the type at the time of initial creation in the Save As dialog box. This is one-to-many mapping, and the mapped types are entered in the form of a comma-separated list after a "|".

For example:

  • msword|MS Word Document, MS Word Template, Document
  • msexcel|MS Excel Document, MS Excel Template, Document
  • mspowerpoint|MS PowerPoint Document, MS PowerPoint Template, Document
  • msoutlook|MS Outlook Document, MS Outlook Template, Document
  • outlookattachment|MS Outlook Attachment

MCADInteg-TypePolicyMapping (Multiline String)

This attribute lists the policies to be shown for a particular type. Each entry is a map of two strings separated by a "|". The types are listed on the left and the list of policies on the right. You can select the desired type in the Save as dialog box.

The policy combo box is updated depending on the type, based on this attribute.

Note: All 3DEXPERIENCE types and policies must be defined before they are entered.

For example, here is a set of standard values:

  • MS Word Document|Document Release
  • MS Excel Document|Document Release
  • MS Powerpoint Document|Document Release
  • MS Outlook Document|Document Release
  • MS Outlook Attachment|Document Release
  • Generic Document|Controlled Design Release Rev2, Controlled Production Release Rev2
  • Document|Document Release

Note: One type can have multiple policies. The different policies can be separated by a comma.

For Example:

Generic Document|Controlled Design Release Rev2, Controlled Production Release Rev2

MCADInteg-TypeFormatMapping (Multiline string)

This attribute maps the Collaboration for Microsoft types to the 3DEXPERIENCE types and formats. Each entry is a map of two strings separated by a "|". The CAD (Microsoft Office) types are listed on the left whereas the 3DEXPERIENCE types and their format are listed on the right.

For example:

If the entry is

msword|Generic Document, generic

then the Microsoft Word documents are checked in to the generic format for the Generic Document type.

Other Examples:

  • msword|MS Word Document,doc
  • msword|Generic Document,generic
  • msword|Document,doc
  • msexcel|MS Excel Document,xls
  • msexcel|Generic Document,generic
  • msexcel|Document,xls

MCADInteg-MxToCADAttribMapping (Multiline string)

This property maps the attributes from 3DEXPERIENCE to Collaboration for Microsoft. It is used to synchronize attributes during checkout and during the From Database synchronization.

The syntax of the attribute is:

ENOVIA-Type,ENOVIA-Attribute|CAD-Type,CAD-Attribute

The possible values for the Collaboration for Microsoft type are msword, msexcel, mspowerpoint, msoutlook, msproject.

For Example:

  • MS Word Document,Title|msword,$$Title$$
  • MS Word Document,$$Description$$|msword,$$Subject$$
  • Generic Document,Title|msexcel,$$Title$$
  • Generic Document,$$Description$$|msexcel,$$Subject$$
  • Document,Title|mspowerpoint,$$Title$$
  • Document,$$Description$$|mspowerpoint,$$Subject$$

This setting maps the attributes of 3DEXPERIENCE types to properties of Office documents. For example,

MS Word Document,Title|msword,$$Title$$

This maps the attribute, Title, of the MS Word Document type to the Office Word Title that is specified as msword

Notes: Note the following points:
  • For built-in 3DEXPERIENCE attributes such as Description, Name, and built-in Office attributes like Summary, the attribute must be enveloped by "$$". For example, $$Description$$
  • Mapping attributes in this setting is not mandatory.

MCADInteg-CADToMxAttribMapping (Multiline string)

This property maps the attributes from Microsoft Office to 3DEXPERIENCE. It is used to synchronize attributes during check-in, and during To Database synchronization.

The syntax of the attribute is:

CAD-Type,CAD-Attribute|Matrix-Type,Matrix-Attribute

The possible values for the CAD-Type are msword, msexcel, mspowerpoint, and msoutlook.

For Example:

  • msword,$$Title$$|MS Word Document,Title
  • msword,$$Subject$$|MS Word Document,$$Description$$
  • msexcel,$$Title$$|Generic Document,Title
  • msexcel,$$Subject$$|Generic Document,$$Description$$
  • mspowerpoint,$$Title$$|Document,Title
  • mspowerpoint,$$Subject$$|Document,$$Description$$

This setting maps the custom attributes from Microsoft Office to the 3DEXPERIENCE system attributes. For example,

msword,$$Title$$|MS Word Document,Title

This maps the Microsoft Office custom attribute, Title to the 3DEXPERIENCE type, Microsoft Word Document's attribute, Title.

Similarly, for msword,$$Subject$$|MS Word Document,$$Description$$

This maps the Microsoft Office attribute, Subject, to the system attribute, Description.

Notes: Note the following points:
  • Similar to 3DEXPERIENCE to CAD mapping, you must envelope built-in attributes by "$$".
  • Mapping attributes in this setting is not mandatory.

IEF-TypeTemplateMapping (Multiline String)

This attribute maps Microsoft Office types to the template types required for the template command. The syntax of this attribute is,

CAD_TYPE|TEMPLATE_TYPE

For Example:

  • msword|MS Word Template
  • msexcel|MS Excel Template
  • mspowerpoint|MS Powerpoint Template

IEF-Pref-MCADInteg-DefaultTypePolicySettings

This setting provides the policy to create document types from Collaboration for Microsoft. The policy can be DEFAULTVALUE or ENFORCED. The user cannot change ENFORCED policies.

IEF-UnsupportedCharacterMapping

This attribute is used to map an entity-specific list of unsupported characters. For more information, see the description of IEF-UnsupportedCharacterMapping from X-CAD Design Management Administration Guide| Configuring and Setting Preferences | Entering GCO Attribute Values.

You can configure the characters that are allowed in the names of projects and tasks.

MSOIUnsupportedExtensions

This attribute is used to list the file extensions that are not supported for file check-in using the Collaboration for Microsoft client.

MSF-ChangeEstimatedSchedulingOnActualDates

This setting decides if the scheduling of 3DEXPERIENCE projects must be changed from Estimated to Actual when actual data is available. You can set the value to False for only Estimated-based scheduling, and to True to support Actual scheduling.

IEF-Pre-MCADInteg-CheckOutDirectory

This attribute defines the default location for downloading the files during checkout.

When you open a document, it is saved to the Checkout Directory path which is specified in the settings.

MSF-DisableCreateObject

This attribute defines the creation of a document.

This attribute when set to True prevents document creation. The Save As New is disabled from Microsoft Office & Create New Object check box is disabled from Windows Explorer.

The default value is False.