Change package pre- and post-processing exit points
Change package exit points occur before and after processing an API command for
a change package: Approve, Backout, Create, Delete, Disapprove, Discard, Import, Install, Migrate,
Newcopy, Ready, Unready, and Update.
The pre-processing exit points occur after any security checks.
You can use these exit points to augment change package workflow. For example:
Add standard text to the Description, External reference, or Notes attributes
- Notify users of planned or completed change package activity
- Log information regarding completed activity
- Trigger an event in an external change management system
- Security-check a user's authority to perform the designated action
- Obtain a proceed-or-terminate decision from an external change management system
- Overrule change package processing checks
- Automatically update change package Ready or Approve states
For the pre-processing exit points, you can write user exit programs to disallow or allow the action.
API command | Pre-processing exit point name | Post-processing exit point name |
---|---|---|
Approve | CPPRAP01 | CPPOAP01 |
Backout | CPPRBO01 | CPPOBO01 |
![]() ![]() ![]() ![]() |
![]() ![]() |
![]() ![]() |
Disapprove | CPPRDA01 | CPPODA01 |
![]() ![]() |
![]() ![]() |
![]() ![]() |
Import | CPPRIM01 | CPPOIM01 |
Install | CPPRIN01 | CPPOIN01 |
Migrate | CPPRMG01 | CPPOMG01 |
Newcopy | CPPRNC01 | CPPONC01 |
Ready | CPPRRD01 | CPPORD01 |
Unready | CPPRUR01 | CPPOUR01 |
1
The Edit exit point is executed for the API commands Create, Update, and Delete. An Update command for a change package causes its attributes, such as description or external reference, to change. In the following situations, the Edit exit point does not execute:
- When resource definitions or commands are added to or removed from a change package
- When the attributes of a change package are set by another API command, such as when the status of a change package is set by the Ready API command