About Business Logics Supporting New Typing System in FBDI

In File-based Design Import (FBDI), you can use openings business logic (BL) that supports new typing customization. This BL helps you to choose the type, extensions and attribute values of the migrated 3DEXPERIENCE components.

See Also
FBDI Principles

The CustoTypeMapping business logic is used to get customized discipline type for migrated 3DEXPERIENCE components. The input proxy 'ThisObject' is the discipline type of the object to be created. You can write a script to determine the customized discipline type using CustoTypeMapping .CATRuleExit and .CATRule files. Scripts depend on the input discipline type of the business logic. The output parameter 'TargetCustoName' provides name of the type instead of the customization name. This business logic is used during the DeclarePLMEntities step. Initially, the policy is stored in mapping and it is retrieved when the component is migrated.

The PLMImportExportAttributesValuation business logic is used to get attribute values for primary type and the deployment extension. While importing CATIA V5 document using FBDI, file path is made available to the attribute valuation BL. This BL helps in distinguishing between an internal component inside a CATProduct and a CATProduct. The value of IsInternalComponent should be set as TRUE.

You can write scripts valuating primary type attributes and add a deployment extension. For this business logic, ImportExportAttributesValuation, CATRuleExit and CATRule files are used.