|Require transport forms to be assigned to related tasks
| When a transport form is completed for a change request, it is always possible to assign the change request to one or more tasks, such as a request for a new report or a logged production support problem.
Tasks provide greater visibility of related change requests and associate technical changes with business requirements. Tasks are necessary if test results are to be entered.
Enable this option to prevent a transport form from being saved if the related tasks section has not been maintained.
|Allow team members to delete transport forms of change requests that have been imported
|By default, in order to avoid losing transport history, only an administrator may delete the transport form of a change request if the change request has already been imported into some target systems. Enable this option to override this behaviour.
|Configured testers only to complete testing
| When this option is enabled Transport Express will only allowed users marked in the Task to ‘Save and Finish testing’. This will also validate testers assigned to specific systems and system roles.
If not set anyone can complete the testing for a task.
|Enable “Add to Control Point” function
| This option switches on the “Add to Control Point” functionality that allows transport forms to be assigned to control points in the transport path. This can be an inbox, outbox or test queue as required.
This is used when a re-approval is required for the relevant transports.
|Cache remote transport data
| This option enables the caching function that stores details of remote transports on the domain controller. This means that Transport Express does not have to make RFC calls to the remote systems to obtain the transport data.
Performance is therefore improved when accessing change requests without a transport form and also when viewing transports in control points. Note: Once switched on the Transport Express GUI will need to be closed and re-started for the caching to take effect.
|Hide Transport originating in ‘hidden’ systems
|This option will not show transports if the target is set as hidden
|This option is used to select whether TE is to perform cross path conflict checks for situations where the same system ID is on more than one TE path
|Planning Status Calculation
|If more than one planning status could be applied to a task, this configures which one the system should assign. Either the one with the earliest sequence or the one with the latest sequence
|Deployment Status Calculation
|If more than one deployment status could be applied to a task, this configures which one the system should assign. Either the one with the earliest sequence or the one with the latest sequence
Thanks for your feedback.