This documentation applies to the 8.1 version of Change Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Planning dependencies for change requests

When planning how to implement a series of change requests, determine in what order, if any, they must be completed. To set dependencies, you assign a sequence number to each request. Requests with a lower sequence number must be completed before those with higher numbers can be completed; otherwise, you are notified by a warning message (by default). More than one request can have the same sequence number; requests with the same sequence number are considered peers. For example, a request with the sequence number 3 can be completed only after all requests with sequence numbers 1 and 2 are completed. Peer requests can be completed in any order among themselves.

To implement sequence numbers in requests, see Assigning sequence numbers to dependent change requests.

Note

Your application administrator can configure the level of enforcement of the change dependency rules. For example, BMC Change Management can be configured so that users see an error, not just a warning, if they complete requests out of sequence. For more information, see Configuring change rules.


A change request can include multiple tasks. When a change request is scheduled, the first task is activated and set to Assigned. When the last task is completed and its status is set to Closed, the request is Completed.

To implement sequence numbers for tasks, see Sequence number in task groups and tasks.

Was this page helpful? Yes No Submitting... Thank you

Comments