The automatic processing of a client can be stopped. The status of the active tasks such as workflows, Schedules and events changes and finally, these tasks show the status "STOP" - Automatic processing has been stopped.
Client Status Stop
While a client is being stopped, you can still activate tasks. Tasks such as Schedules, workflows, events, groups or recurring tasks also obtain the status STOP. Individual tasks without superordinate tasks are processed.
You can use the Go command in the PerspektiveEigener Funktionsbereich der Automic Web Interface (AWI) - Weboberfläche. „Administration“'s context menu in order to release tasks. In this case, they are processed although the system is stopped.
Handling |
Description |
---|---|
Right-click the client |
You can change the system status of any client in the Perspektive „Administration“ of client 0000. Select the Client Stop command in the client's context menu. |
This script element is used to change the system status (parameter STOP) from within a script. |
The current status is stored in the variable UC_CLIENT_SETTINGS in the global value CLIENT_STATUS.
Client Status Go
A global start of automatic processing has the effect that all active tasks start that are in a STOP status. The system does not distinguish whether they have individually been stopped or through a system-wide stop.
Handling |
Description |
---|---|
Right-click the menu |
You can change the system status of any client in the Perspektive „Administration“ of client 0000. Select the Client Go command in the particular client's context menu. |
This script element is used to change the system status (parameter GO) from within a script. |
The current status is stored in the variable UC_CLIENT_SETTINGS in the global value CLIENT_STATUS.