Paths are created by Administrators and other authorised users via the left hand panel in the Paths and Workflow app screen.
Figure: Paths within Paths and Workflow.
Paths configuration screen within the ActiveControl Web Platform.
The following properties are available as part of the Path configuration screen:
|A short description of the transport path.
|An optional label to group common transport paths together.
|This field determines whether the transport path may be assigned to new Transport Forms. It also determines whether an inactive transport path (that can no longer be assigned to new Transport Forms) appear in the ActiveControl main screen
|Automatically release transports…
| If this option is enabled, ActiveControl will automatically release a transport request when a Transport Form is completed.
However, if a pending queue is enabled for the transport path, then the transport request is only released after transporting has been approved.
|When completing a Transport Form, check whether the changes conflict with others that are still being transported
| When this option is enabled, ActiveControl will automatically check whether there are other transports still being transported on the transport path with changes to the same content.
The conflicting transports are displayed in a pop-up window.
|Do not allow team members to complete a Transport Form if conflicting changes are found
| This option can only be enabled when the previous option is enabled. When enabled, team members may not complete a new Transport Form if other transports with changes to the same content are still being transported on the transport path.
This option does not apply to Administrators.
For additional control, ActiveControl allows combinations of valid and/or invalid source systems and clients to be defined for each transport path. When a Transport Form is completed for a transport request, ActiveControl will only allow the transport request to be assigned to a transport path if the source system and client of the transport request satisfies the transport path’s source client restrictions
|Valid Source Clients
| In this field you may specify combinations of source systems and clients for the transport path.
For example, if you specify combinations “DEV:100, DEV:200” then only transport requests created in either client 100 or client 200 of SAP system DEV may be assigned this transport path.
|Invalid Source Clients
| In this field you may specify combinations of source systems and clients that may not be assigned the transport path.
For example, if you specify “DEV:300” then transport requests created in client 300 of system DEV cannot have this transport path assigned.
The list of invalid source clients overrides the list of valid source clients, though it is not usually used in conjunction with a list of valid source clients.