Part Life Cycle State Synchronization

The life cycle state of an E-BOM Part is exported as the value of the <Maturity> element is identical to the 3DEXPERIENCE platform life cycle state.

The export of an E-BOM Part can be controlled based on its maturity state.

The file XPGAdapterConfig.properties located at server\STAGING\<enoviaapplicationname>\WEB-INF\classes\XPG contains properties listing the states from which the part can be exported. There is one property per policy.

Properties can be configured as following:

ValidStatesForXPDMExchange.[symbolic name of the policy]=[list of states separated with commas]

As an example, here is the default declaration for policy EC Part:

ValidStatesForXPDMExchange.policy_ECPart=Preliminary,Review,Approved,Release

When importing an E-BOM Part:

1. the X-PDM lifecycle state name (value of the <Maturity> element) is mapped to an 3DEXPERIENCE platform state name.
2. the part maturity is synchronized until the target 3DEXPERIENCE platform state is reached.

The mapping is based on the policy of the part and described in the pdm-cust-config.xml file (located at server\ STAGING\<enoviaapplicationname>\WEB-INF\classes\XPG). As an example, here is the default mapping provided for policy EC Part:

<Lifecycle ObjectType="policy_ECPart">
<LifecycleStateMap>
		<MapEntry LocalName="Preliminary" RemoteName="In Work" />
		<MapEntry LocalName="Review"      RemoteName="Review" />		
		<MapEntry LocalName="Approved"    RemoteName="Approved" />
		<MapEntry LocalName="Release"     RemoteName="Released" />
</LifecycleStateMap>	
</Lifecycle>

where,

• The value of ObjectType corresponds to the symbolic name of the E- BOM Exchange Part policy.
• MapEntry declarations define how lifecycle state names are translated between X-PDM and 3DEXPERIENCE platform.

For example, an object received from X-PDM with lifecycle state In Work will have life cycle state Preliminary in 3DEXPERIENCE platform.