Customizing Logic to Determine the Default Configuration Specifications
You can develop customized logic to determine the default configuration specification used by various applications. For example, this could be used to implement custom logic that will be used to create a default configuration specification for when adding objects to a Work Package.
WTDocumentGetConfigSpecForDelegate2 is the delegate that is used by {@link ConfigService#getConfigSpecFor(NavCriteriaContext)} to create the list of ConfigSpec. The delegate is looked up using service name = wt.vc.config.GetConfigSpecForDelegate and requestor = {@link NavCriteriaContext#getApplicableType()} and optional selector = {@link NavCriteriaContext#getApplicationName()}.
The delegate can be registered with or without selector but the system will give precedence to a delegate registered with a selector that matches the {@link NavCriteriaContext#getApplicationName()}.
To create a custom delegate, extend one of the classes {@link wt.part.WTPartGetConfigSpecForDelegate}, {@link wt.doc.WTDocumentGetConfigSpecForDelegate}, or {@link wt.epm.EPMDocGetConfigSpecForDelegate}. Then register that delegate using the xconfmanager with the service name, selector, and requestor as defined above.
 |
For more information on the xconfmanager, see Using the xconfmanager Utility
|
Please refer to Javadoc for more information about the delegates.