Configurable Revision Links
A Configurable Revision Link is a revision to revision relationship. When a configurable revision link is created, you can initialize a soft attribute defined on the link.
You can configure the default values that can be set for each attribute via an XML configuration file. The IBA framework APIs are used to load the IBA attributes, so the name must be the attribute name of the IBA attribute.
The value1 is a required attribute which specifies the value for the attribute. The value2 attribute is optional and is required to pass in additional value (for example precision in float). If the XML file is not configured, no operations are performed.
The supported type for which IBA attributes can be set is ConfigurableRevisionLink.
Events
Events that are configured to set\reset the values of IBA attributes and the respective tags that hold values are:
Event
Tag
Creation of Configurable Revision Link. The value is only set if value is not already set.
onCreation
Copy forwarded Configurable Revision Links on the revise of Role A.
onReviseOfRoleA
Copy forwarded Configurable Revision Links on the revise of Role B. This option is only available if the preference is set to True.
onReviseOfRoleB
Supported IBA Attribute Types
Supported IBA attributes types for both standard and global IBAs and the format for the value:
Type
Context
Sample Value
String
Standard and Global IBAs
value= "StringValue"
Integer
Standard and Global IBAs
value= "IntegerValue"
Real Number
Standard and Global IBAs
value= "RealValue|Precision"
Real Number with Units
Standard and Global IBAs
value="RealValue|Precision|Units"
Boolean
Standard and Global IBAs
value= "BooleanValue"
Date & Time
Standard and Global IBAs
value= "YYYY-MM-DD HH:MM:SS.S" (the time is GMT)
URL
Global IBAs
value= "hyperlink|label"
* 
If there are multiple parts to an attribute (for example Real Number with precision), the parts must be delimited by '|'.
The delegate only supports setting the attribute if the attribute has a single value. In the case of a multi-valued attribute that has more than one value, the delegate will not set any value for the attribute.
Attributes values can be defined for the Parent type and are applied to soft types by inheritance.
Defining and Loading Default Values
1. The property that contains the definitions for the default values: wt.configurablelink.DefaultValues=$(wt.home)$(dir.sep)codebase$(dir.sep)wt$(dir.sep)configurablelink$(dir.sep)DefaultValuesForConfigLink.xml
2. If changes are made to the DefaultValuesForConfigLink.xml file you must either:
a. Restart the Method Server
b. Run the wt.configurablelink.ConfigurableLinkUtils utility to load the default values for attributes.
Sample Configuration File
This is a sample xml file for specifying the default values for IBA attributes to be set on creation.
Location: <Windchill>\codebase\wt\configurablelink\DefaultValuesForConfigLink.xml
<type name="WCTYPE|wt.configurablelink.ConfigurableRevisionLink">
<attribute name="std_real_1">
<onCreation value="20|2" />
<onReviseOfRoleA value="20|2" />
<onReviseOfRoleB value="50|2" />
</attribute>
<attribute name="std_real_u1">
<onCreation value="20|1|kg/s**3" />
<onReviseOfRoleA value="40|2|kg/s**3" />
<onReviseOfRoleB value="50|2|kg/s**3" />
</attribute>
<attribute name="std_bool_1">
<onCreation value="true" />
<onReviseOfRoleA value="false" />
<onReviseOfRoleB value="false" />
</attribute>
<attribute name="std_str_1">
<onCreation value="StringND"/>
<onReviseOfRoleA value="StringRoleA"/>
<onReviseOfRoleB value="StringRoleB"/>
</attribute>
<attribute name="std_url_1">
<onCreation value="http://www.ptc.com|PTC"/>
<onReviseOfRoleA value="http://www.ptc.com|PTC"/>
<onReviseOfRoleB value="http://www.ptc.com|PTC"/>
</attribute>
<attribute name="std_ts_1">
<onCreation value="2001-01-30 12:12:12.128"/>
<onReviseOfRoleA value="2001-01-30 12:12:12.128"/>
<onReviseOfRoleB value="2001-01-30 12:12:12.128"/>
</attribute>
<attribute name="std_int_1">
<onCreation value="2"/>
<onReviseOfRoleA value="2"/>
<onReviseOfRoleB value="2"/>
</attribute>
</type>
</defaultValuesForattributes>
Was this helpful?