Mapping Identification and Customer Discipline Attributes During Import

This section describes how to modify and distribute the local identification and customer discipline attributes during import of PLM objects from Site1 to Site2.

For example, the objects to be imported can have the same supplier identification attributes such as PLM_ExternalID or V_Name to enable User1 of Site1 and User2 of Site2 to work on the same platform. Moreover, when you deploy any solution on any site, the imported objects are consistent with the similar enterprise Discipline Management policy. These attributes are mapped by declaring and implementing a business logic named PLMAttributeMapping. You can use this BL to map other attributes. Such as, maturity that can be executed during 3D XML with authoring or synchronization of a PLM Channel.

This page discusses:

Map Identification Attributes

This section describes how to map the identification attributes.

Required baseline access roles: Author, Leader.

One of the PLM_ExternalID or V_Name attributes are defined to retain the identification of the supplier in a customized attribute during the first import. You can determine and map the identification values of PLM_ExternalID and V_Name of the imported object through business rules. Administrator defines business rules by default, and these get executed during Import As Reference or synchronization of a PLM Channel.

Business Logic

The tables below demonstrates the business logic and context object parameters for customization of Identification during import:

PLM Opening ID PLMImportExportAttributesValuation
Operation Id BriefcaseImport
Customization Intent Computation

Context Object Parameters

Parameter Names Description
Operation Id Used for identifying the context of mapping
First Import Used for initializing the customized attribute values during first import
This Object Used for retrieving the original attribute values
Id String Used for evaluating the identifier attribute
iFileId Used for prevaluating the identifier attribute
Exchange Info Used for describing additional information on an exported PLM object
oReferenceId Used for evaluating the identifier attribute
File Name Used for evaluating the identifier attribute
File Type Used for evaluating the identifier attribute
NativeV5Properties Used for evaluating the identifier attribute
UserV5Properties Used for evaluating the identifier attribute

As an example, here is the PLMImportExportAttributesValuation.CATRule delivered to customize the identification attribute during import: 

Let ExInfo        (feature)
Let vSupplierName (string)
Let vExternalId   (string)

vSupplierName = ""
vExternalId   = ""
if( Parameters->HasAttribute("ExchangeInfo") == true ) 
{
 ExInfo = Parameters->GetAttributeObject("ExchangeInfo") 
   if( Parameters->HasAttribute("FirstImport")== true )
   { 
      if( Parameters->GetAttributeBoolean("FirstImport") == true )	
      {
         if( ThisObject->HasAttribute("PLM_ExternalID") == true )
         {
            vExternalId   = ThisObject->GetAttributeString("PLM_ExternalID")
            vSupplierName = "Old: " + ThisObject->GetAttributeString("PLM_ExternalID")
	          if( ExInfo->HasAttribute("PLM_ExternalID") == true )
            {
              vExternalId = "New_" + vExternalId
	            ExInfo->SetAttributeString( "PLM_ExternalID" , vExternalId )	
            }
         }

         ThisObject->SetAttributeString( "V_SupplierName" , vSupplierName )
      }
   }
}

Map Customer Discipline Attributes

This section describes how to map the customer discipline attributes.

Required baseline access roles: Author, Leader.

The V_CustoDiscipline attribute is defined locally on each ENOVIA database to set an authorized value during import when object to be imported is unknown from the local database. You can determine the discipline value of V_CustoDiscipline of the imported object through business rules. Administrator defines business rules by default, and these get executed during Import As Reference or synchronization of a PLM Channel.

Business Logic

The tables below demonstrates the business logic and context object parameters for customization of Customer Discipline during import:

PLM Opening ID PLMCustoTypeMapping
Operation Id BriefcaseImport
Customization Intent Computation

Context Object Parameters

Parameter Names Description
Operation Id Used for identifying the context of mapping
Source Used for providing an accurate context of mapping with the content source
Target Used for providing an accurate context of mapping with the content target
Source Object The PLM Proxy corresponding to the source object
Custo Discipline Used for valuating V_CustoDiscipline. This value can be used only if value is not set and if the value is different from the assigned value $RESET$
This Object Used for retrieving the corresponding source attributes values
TargetCustoName Used for returning the name of the Customization for the target entity after Rule computation

Note: The customization type is not available for mapping the Customer Discipline (V_CustoDiscipline attribute).