Configuring the Content to be Displayed for Each Type

To navigate to various ENOVIA folders in Collaboration for Microsoft client, types have to be mapped with either relationships or menu in typeNavigationMappings string of IEFDesktopConfigurations program.

The type navigation mappings are specified in typeNavigationMappings string member of the JPO IEFDesktopConfigurations and MSOITypeRelationshipMappings attribute of GCO.

If a menu is mapped to a type in typeNavigationMappings string, then no modifications are required in the MSOITypeRelationshipMappings attribute.

If a type is mapped to a relationship in the typeNavigationMappings string in the IEFDesktopConfigurations program, then the attribute MSOITypeRelationshipMappings also needs modification in the GCO to perform check-in and check-out of a file, without this mapping only navigation is possible.

  1. Create and map a command to the IEF ENOVIA Root Menu.

    For more information, see Configuring the Root Folders to be Displayed in Collaboration for Microsoft

  2. If type and menu mapping is required, do the following:
    1. Run the following MQL commands.
      Run MQL from the Live Collaboration Server folder or from 3DSpace. For more information, see Installation and Setup | Administrate | 3DEXPERIENCE Platform | 3DSpace | Collaboration and Approvals | Adminstrative Utilities | Running MQL
    2. Create a Msoitype_<TYPENAME> menu such as Msoitype_Incident.
    3. Navigate to the Items tab. Add the required commands such as PRCIncidentReferenceDocumentsTreeCategory and PRCIncidentTestCasesTreeCategory. Click Edit to save the changes.
    4. Register the above menu with a symbolic name of the format, menu_Msoi<TYPENAME> and fill in all the other details.

      Example:

      For Msoitype_Incident, the symbolic name can be menu_MsoiIncident.

    5. Edit the IEFDesktopConfigurations JPO.
    6. Modify the typeNavigationMappings string member with the following entry: SymbolicTypeName|SymbolicMenuName

      Example: type_GeneralClass|menu_Msoitype_GeneralClass

      Class Menu

      Classified Items

      Reference Documents

      Subclasses

  3. If a type is mapped to a relationship, then you must modify the MSOITypeRelationshipMappings attribute in the GCO to perform file checkout and check-in using Collaboration for Microsoft. Do the following:
    1. Modify the typeNavigationMappings string of the IEFDesktopConfigurations JPO with the following entries: SymbolicTypeName|SymbolicRelationshipName@symbolicCommandName

      Example:

      type_Incident|relationship_ReferenceDocument@command_IEFDesktopDocumentSummary

    2. Modify the GCO attribute MSOITypeRelationshipMappings with the following entries: SymbolicTypeName|SymbolicRelationshipName

      Example: type_Incident|relationship_ReferenceDocument

  4. Restart the platform server and the application server.

    By default, typeNavigationMappings has the following values:

    • type_PersonalWorkspace|relationship_ProjectVaults@command_IEFDesktopObjectSummary\n
    • type_ProjectSpace|@command_MsoiPMCFolders\n
    • type_Project|relationship_VaultedDocuments@command_IEFDesktopTMCFolder\n
    • type_Library|relationship_ReferenceDocument,relationship_Subclass@command_IEFDesktopObjectSummary\n
    • type_PartLibrary|relationship_ReferenceDocument,relationship_Subclass@command_IEFDesktopObjectSummaryIEFDesktopObjectSummary
    • type_GeneralLibrary|relationship_ReferenceDocument,relationship_Subclass@command_IEFDesktopObjectSummary\n
    • type_DocumentFamily|relationship_ReferenceDocument,relationship_ClassifiedItem,relationship_Subclass@command_IEFDesktopObjectSummary\n
    • type_GeneralClass|relationship_ReferenceDocument,relationship_ClassifiedItem,relationship_Subclass@command_IEFDesktopObjectSummary\n
    • type_LogicalFeature|relationship_ReferenceDocument,relationship_FeaturesSpecification,relationship_LogicalFeatures,relationship_FeatureTestCase,relationship_FeatureUseCase,relationship_RequirementSatisfiedBy,relationship_ManufacturingFeatures@command_MsoiDocumentSummary\n
    • type_ManufacturingFeature|relationship_ReferenceDocument,relationship_FeaturesSpecification,relationship_LogicalFeatures,relationship_ManufacturingFeatures,relationship_FeatureTestCase,relationship_FeatureUseCase,relationship_RequirementSatisfiedBy@command_MsoiDocumentSummary\n
    • type_ConfigurationFeature|relationship_ReferenceDocument,relationship_FeaturesSpecification,relationship_ConfigurationFeatures,relationship_FeatureTestCase,relationship_FeatureUseCase,relationship_RequirementSatisfiedBy@command_MsoiDocumentSummary\n
    • type_Requirement|relationship_RequirementBreakdown,relationship_RequirementUseCase,relationship_RequirementValidation,relationship_ReferenceDocument@command_MsoiDocumentSummary\n
    • type_TestCase|relationship_SubTestCase,relationship_ReferenceDocument@command_MsoiDocumentSummary\n
    • type_UseCase|relationship_SubUseCase,relationship_ReferenceDocument@command_MsoiDocumentSummary\n
    • type_Task|relationship_Subtask,relationship_TaskDeliverable,relationship_ReferenceDocument@command_IEFDesktopObjectSummary\n
    • type_Part|menu_MsoiPart\n
    • type_Products|relationship_ReferenceDocument,relationship_ProductSpecification,relationship_ProductBuild,relationship_ConfigurationFeatures,relationship_LogicalFeatures,relationship_ManufacturingFeatures,relationship_ProductRequirement,relationship_ProductConfiguration,relationship_AssociatedManufacturingPlans,relationship_RoadmapTask,relationship_ProductVersion@command_MsoiDocumentSummary\n
    • type_Builds|menu_MsoiBuilds\ntype_ProjectVault|relationship_VaultedDocuments,relationship_VaultedDocumentsRev2,relationship_SubVaults@command_IEFDesktopObjectSummary\n
    • type_PartFamily|relationship_ClassifiedItem,relationship_PartFamilyReferenceDocument,relationship_Subclass@command_MsoiDocumentSummary\n
    • type_ProductConfiguration|relationship_ProductConfigurationBuild@command_IEFDesktopObjectSummary\n
    • type_ManufacturingPlan|relationship_ReferenceDocument@command_IEFDesktopObjectSummary\n
    • type_Meeting|relationship_MeetingAttachments@command_IEFDesktopObjectSummary\n
    • type_HardwareBuild|relationship_ReferenceDocument@command_IEFDesktopObjectSummary\n
    • type_SoftwareBuild|relationship_ReferenceDocument@command_IEFDesktopObjectSummary\n
    • type_ControlledFolder|relationship_VaultedDocumentsRev2@command_IEFDesktopObjectSummary\n
    • type_Phase|relationship_Subtask,relationship_ReferenceDocument@command_IEFDesktopObjectSummary\n
    • type_Gate|relationship_Subtask,relationship_ReferenceDocument@command_IEFDesktopObjectSummary\n
    • type_Milestone|relationship_Subtask,relationship_ReferenceDocument@command_IEFDesktopObjectSummary";

    By default, MSOITypeRelationshipMappings has the following values:

    • type_ProjectSpace|relationship_ReferenceDocument
    • type_Project|relationship_VaultedDocuments
    • type_Book|relationship_HasDocuments
    • type_Task|relationship_TaskDeliverable
    • type_ProjectVault|relationship_VaultedDocumentsRev2
    • type_GeneralClass|relationship_ClassifiedItem
    • type_DocumentFamily|relationship_ClassifiedItem
    • type_ControlledFolder|relationship_VaultedDocumentsRev2
    • type_Phase|relationship_ReferenceDocument
    • type_Gate|relationship_ReferenceDocument
    • type_Milestone|relationship_ReferenceDocument