Process Behaviors

This task describes the various process behaviors you can use depending on the different scenarios.

The table below describes the process behavior parameters.

Parameter Name (in XML script) Purpose Values Required
TargetEnvironment Defines the default PLM environment where data is written to the target.

For more information, see Understanding the PLM Environment in the CAA documentation under Infrastructure / VPM Multi-Discipline Collaboration / PLM Concepts.

Existing PLM environment, declared and available on the 3DEXPERIENCE server NO
TargetLevel Specifies the target CATIA level to be used in downward compatibility scenarios.

For more information, see Release Compatibility.

Existing CATIA V5 level, compatible with the current 3DEXPERIENCE level YES
Mode Defines whether the source provider (TransferMe) orders the transfer. TransferMe YES
StopRestart Defines the number of PLM objects per save transaction. Divides the transfer process into smaller pieces in order to lighten the load of each save transaction on the target provider database. Number NO
Context A Coexistence mapping context can be seen as the association between a mapping table string and a logical/physical location. The Coexistence scenarios are managed in a given mapping context called the main context. Coexistence YES
MultiPDM Activates the reconciliation of data coming from several PDMs, for example, ENOVIAvpm and XPDM. On/Off NO
RefreshData Allows a target data update without taking into account whether the source data has been modified or not. On/Off NO
CustoAttributesProtection Allows you to protect Extended Enterprise attributes from being updated after running a Coexistence update.

You can choose to edit customized attributes on the non-Master PDM side.

On/Off NO
ExecutionLog Creates an execution log (in CSV format) with stable information about the transfer.

For more information, see Launching the Resource Generator During Installation.

On/Off NO
CheckMode Allows you to check the data to be transferred before launching it. On/Off NO
BLMandatory Stops the transfer if a problem occurs with BL execution. On/Off NO
ProxyVaultFileAccess Transfers in Proxy mode (stream referencing in the vault instead of a copy to 3DEXPERIENCE). This option is limited to VPM V5. For more information, see ENOVIA VPM V5 Data Transition Tables. On/Off NO
Warning: It is mandatory to:
  • have a different mapping context for each PDM you want to exchange with
  • have the same mapping context when exchanging with a PDM in both V5 -> 3DEXPERIENCE and 3DEXPERIENCE -> V5 scenarios.
Otherwise, you may get transfer errors such as:
  • The object already exists.
  • The object you want to update does not exist.