In the Release phase you can finally relase a Client Command for use. Only then clients recognize the Client Command version and are able to execute them.
Release phase
In the top view, the Client Commands with the statuses Synchronization or Ready for release are displayed. Once you select a Client Command here, all file repositories are displayed on the right-hand side with the current transmission status of the files associated with the Client Command. At this point, the Synchronization phase overlaps with the Release phase.
You can now select a Client Command and click on the Release button. The Client Command will release the client and assign the status Released. However, you should normally wait with this action until all file repositories have fully synchronized the data of the Client Command. If a client runs the Client Command before its associated file repository is synchronized, the next older version will be used. This may lead to complications.
As soon as you want to release a Client Command, you will be asked if all previous versions are to be disabled (Remove from production – see Version History). If you deny this request, all previous versions will be synchronized, which can present a substantial burden on the network.
Client Command properties |
|
|
Console script Part of the Client Command runs in the ACMP Console. |
|
Client script Part of the Client Command runs on the client. |
|
Released The Client Command has at least one released version. |
|
Protected The Client Command is protected by a password. |
|
Interactive The Client Command can be run from the CommandLauncher. |
|
Run as a task The Client Command is configured as an Agent Task. |
It is possible that to release more than one version of a ClientCommand simultaneously. If this Client Command is executed, the client will access the most recently released version that is available on its assigned file repository.
Note: |
Try to release as few versions of a Client Command simultaneously. |
Last change on 10.03.2014