Object Checks When Releasing Requests
The following section only applies to Workbench requests.
When you release a Workbench request, you can subject the objects in the request to various checks.
The object checks currently consist of an extended program check and documentation.
Setting the Object Checks
As a user with the CTS administration authorization (S_CTS_ADMIN), you can do the following:
- Activate or deactivate the object checks for all users
- Leave it up to the user to decide whether to activate or deactivate the checks
For more information, see
Setting Object Checks.
To check the objects in the Transport Organizer before the request is released, position the cursor on the request or task, and choose Request/task
Objects (syntax check).
Object Checks When Releasing the Request
If you have activated the checks, the following occurs when you release the request:
- If the check results in the cache are up-to-date and no errors were found, the release process is continued.
- If the check results in the cache are up-to-date and errors were found, a dialog box informs you that there were errors. You can then:
- continue the release process anyway
- cancel the release and display the errors
- cancel the release and return directly to the request overview.
- If the check results in the cache are not up-to-date, the remaining checks must now be made. You can either start the checks immediately or - recommended for large requests due to the long runtime - schedule them in the background:
- If you run the checks in the foreground, the results of the checks are displayed automatically. You can then continue with the release.
- If the checks are run in the background and the objects do not contain any errors, the release is started automatically in the background afterwards. After the background processing has been completed, a dialog box informs you about what actions have been performed.