Copy Over Framework
When performing certain end user actions in BOM Transformer or SAPSB, it is possible to configure the application to carry over specific attributes and associations with their related data from upstream to downstream. The actions are Create Equivalent Link, Update to Current Upstream Equivalent Object, Update All Downstream Equivalent Objects, and transformation actions, like New Downstream Part, New Downstream Branch, Paste as New Part, and Paste as New Branch. In case of New Downstream Part Variant, New Downstream Branch Variant, and Replace actions, attribute and association information are carried from existing downstream part to the new downstream part.
 |
The values set in the following properties impact the copy over actions. Only those associated documents, standard control characteristics, and alternate and substitute parts that are specified to be included, are carried over to the downstream structure. The associations that are specified to be excluded are not carried over.
• com.ptc.windchill.associativity.reconciliation.includedTypes
• com.ptc.windchill.associativity.reconciliation.excludedTypes
For information on configuring the properties, see Propagating Upstream Changes.
|
You can define the copy over framework for part attributes, usage attributes, and associations such as documents, control characteristics, and Made From associations.
You can configure the following copy over property to define the attributes and associations to be carried over for specified actions.
<Property name="<property key>" multivalued="," default=""/>
<AddToProperty name="<property key>" value="<property value>"/>
Information on defining the property key and property value is explained in the subsequent topics. For more information, see Defining a Property Key, Defining a Property Value.
For BOM Transformer and SAPSB, the properties are defined in the custom.site.xconf file. For more information, see Setting Property Values and Propagating Your Changes.
|
|
The configuration properties described in this topic and its subtopics must be implemented and deployed on the development environment using the Code and Configuration Deployment (CCD) process. For more information, see Deploy Your Customizations on Your Development Environment and Deploying Code and Configuration Package.
|