Solution
Use the Type Manager to constrain the types of objects that can be associated in the affected and resulting objects tables associated to the change object.
Prerequisite Knowledge
To perform this task, you must have an understanding of the following:
Using the Type Manager and creating association constraints.
Basic Knowledge of the change objects and the role they play in the change process.
The section below includes references to many or all of these subjects.
Solution Elements
Element
Type
Description
wt.change2.ReportedAgainst
Link class
The link class for associating affected objects on a Problem Report or Variance
wt.change2.RelevantRequestData2
Link class
The link class for associating affected objects on a Change Request
wt.change2.AffectedActivityData
Link class
The link class for associating affected objects on a Change Task
wt.change2.ChangeRecord2
Link class
The link class for associating resulting objects on a Change Task
wt.change2.HangingChangeLink
Link class
The link class for associating hanging changes on the resulting objects of a Change Task
StandardardChangeService
Default change service
The default implementation of the change service for creating, updating, deleting for change objects and associations.
Package: wt.change2
ChangeMgmtConstraintHelper
Helper class
A helper class for managing constraints within change.
Package: wt.change2.constraints
When defining the association constraint the Change Object type is the driver for what relationship link is used. The ChangeService2.storeAssociations will derive the correct link type given the Change Object and the base link class and update the link to use the right type for the defined constraint.
Was this helpful?