This information details how to support closure for change object associations using flexible change process associations.

In prior releases change object associations were prescriptive in that problem reports can associate to a change request and change requests to a change notice. The supported API’s for closing the change objects are also specific to the supported relationships. Flexible change process associations now allow for configurable change object associations. Updated APIs are now available to fully support flexible change process associations.

A change object is considered closed when the resolution date and resolved state (i.e. Canceled or Resolved) are set on a change object. The two ways to close change objects are forced and synchronized closure. Synchronized closure is when a change object listens for an event and checks to see if it can close itself. Forced closure is when a different change object’s workflow process closes another related change object, forcing the state and resolution date to be set. For most cases synchronized closure is a better practice as this technique avoids dead lock and stale object issues that can sometimes occur when using forced closure for change objects having their own workflow process.

The scope of this information is to outline recommendations for supporting closure of change object associations using flexible change links.

The intended outcome of this information is to help provide guidance on how to configure workflows to work with flexible change process associations.