How to Implement the Import Export Attributes Valuation Business Logic?

This business logic can be invoked in 2 different contexts:

1. During an import: the business logic allows to customize the valuation of the public PLM attributes on imported PLM entities,
2. Export context: the business logic allows to extract information from the public PLM attributes of the exported PLM entities.

 This Business Logic is called:

1. In the PLM Export File command for file attributes valuation. Public PLM attributes of the Component can be used to pre-valuate the File Reference Id,
2. In the PLM Import File command to initialize mandatory attributes or customize the free PLM attributes by reading the input file information,
3. In the 3DXML Export command to add freely-defined information to exported objects' description
4. In the 3DXML Import command to initialize of update custom attributes on imported objects

This section describes the objects defining the PLM opening: its global information, its kind of input object, its context object parameters.

The Business Logic can be invoked for the listed PLM Component Type. It means that your implementation can safely use the PLM attributes of the default PLM Component.

The following BL samples show how to:

1. initialize the naming of a Representation Reference from the naming of a File containing only geometry (PLM_ExternalID attribute is suffixed by a time stamp)
2. initialize the naming of a File from the naming of a Representation Reference as PLM_ExternalID value.
3. initialize the value of a custom attribute from the PLM_ExternalID value, during a 3DXML Import.
4. add a freely-defined export information based on a custom attribute value, during a 3DXML Export.
5. use this freely-defined information to valuate another custom attribute, during a 3DXML Import.

To achieve this particular business logic implementation, a CATRuleExit file, known as family, declares the script to run each time a PLM Import/Export command is started:

<Scripts>
    <Script OpeningID="PLMImportExportAttributesValuation"
            Type="MyCustoType"
            ScriptName="MyRepDataExchangeImportScript">
            <Condition Attribute="OperationId" Value="DataExchangeImport" />
</Scripts>
    <Script OpeningID="PLMImportExportAttributesValuation"
            Type="MyCustoType"
            ScriptName="MyRepDataExchangeExportScript">
            <Condition Attribute="OperationId" Value="DataExchangeExport" />
</Scripts>
   <Script OpeningID="PLMImportExportAttributesValuation"
            Type="MyCustoType"
            ScriptName="My3DXMLImportScript">
            <Condition Attribute="OperationId" Value="BriefcaseImport" />
</Scripts>
</Scripts>
   <Script OpeningID="PLMImportExportAttributesValuation"
            Type="MyCustoType"
            ScriptName="My3DXMLExportScript">
            <Condition Attribute="OperationId" Value="BriefcaseExport" />
</Scripts>
</Scripts>
   <Script OpeningID="PLMImportExportAttributesValuation"
            Type="MyCustoType2"
            ScriptName="My3DXMLImportScript2">
            <Condition Attribute="OperationId" Value="BriefcaseImport" />
</Scripts>

This family references the script that contains the business logic implementation, which looks like the following CATRule file:

Sample 1 (MyRepDataExchangeImportScript.CATRule) :

The script is based on a user knowledge package which provides a function DateFormat to get a time stamp.

Let Name(string)
Name = ""
 
if (Parameters->HasAttribute("iFileId")== true)
{ 
    Name = Parameters->GetAttributeString("iFileId")
}
 
if(Name <> "") 
{
    if ( ThisObject->HasAttribute("V_Name") == true )	
	{
		ThisObject.V_Name = Name 
	}
	ThisObject.PLM_ExternalID = Name + "_" + DateFormat("%Y-%m-%d_%Hh%M")
}

Sample 2 (MyRepDataExchangeExportScript.CATRule) :

Let Name(string)
Name = ""
 
if (Parameters->HasAttribute("oReferenceId")== true)
{ 
    if ( ThisObject->HasAttribute("PLM_ExternalID") == true )	
	{
		Name = ThisObject.PLM_ExternalID
	}
	Parameters->SetAttributeString("oReferenceId",Name) 
}

Sample 3 (My3DXMLImportScript.CATRule) :

Let Name(string)
Name = ""
 
if (Parameters->HasAttribute("FirstImport")== true)
{ 
    if ( Parameters->GetAttributeBoolean("FirstImport") == true )	
	{
		if (ThisObject->HasAttribute("PLM_ExternalID")== true)
		{ 
			Name = ThisObject.PLM_ExternalID
		}
		ThisObject->SetAttributeString("MyCustomAttribute",Name) 
	}
}

Sample 4 (My3DXMLExportScript.CATRule) :

Let Value(string)
Let ExInfo(feature)
Value = "sampleValue"
 


if (ThisObject->HasAttribute("MyCustomAttribute")== true)
{ 
	Value = ThisObject.GetAttributeString( "MyCustomAttribute" )
}

if (Parameters->HasAttribute("ExchangeInfo") == true) 
{
	ExInfo = Parameters->GetAttributeObject("ExchangeInfo")
	ExInfo->SetAttributeString( "sampleKey", Value )
}

Sample 5 (My3DXMImportScript2.CATRule) :

Let Value(string)
Let ExInfo(feature)
Value = "sampleValue"
 

if (Parameters->HasAttribute("ExchangeInfo") == true) 
{
	ExInfo = Parameters->GetAttributeObject("ExchangeInfo")
	if (ExInfo->HasAttribute("sampleKey") == true) 
	{
		Value = ExInfo->GetAttributeString( "sampleKey" )
	}
}

ThisObject.SetAttributeString( "MyOtherCustomAttribute", Value )