Messages U70xx

Explanation: &01 = Name of the object &02 = RunID

Possible reasons: * The Calendar referred to does not exist. * The keyword referred to could not be found in the Calendar. Solution: Correct ProcessFlow, recreate or expand Calendar &01 = Calendar object

Explanation: The earliest start time is specified in the tab of the same name (ProcessFlow settings). &01 = Name of the object &02 = Earliest start time in the format +TT/HH:MM

Explanation: An error occurred that will be described in more detail in the subsequent message. -> Analyze subsequent message, correct error and re-activate Workflow if required.

The Automation Engine supports agent groups for File Transfer objects as source OR destination. It is not possible to use agent groups as source AND destination.

The activation was interrupted because it was not possible to resolve the AgentGroup (no active hosts for this AgentGroup). Now the activation could continue (hosts active), but the task cannot be found in the activity table anymore.

Explanation: &01 = Name of the object &02 = RunID

Explanation: The number of parallel running tasks which have the group defined as start type may be specified in the Group's attributes. The Group itself, however, must not run parallel. &01 = Group object

Explanation: An attempt was made to start a group manually although a manual start is restricted in the group's attributes. Solution: Change the settings in the group's "Attributes" tab. &01 = Group object

Explanation: The type of the activated event is unknown and/or undefined. Probably, the event was newly created but not yet processed. Solution: Edit the event and select a valid event type.

Explanation: Access was attempted to a calendar date which is not within the valid period. Solution: Change access date and/or calendar and try again.

Explanation: The client 0000 of a UC4 system is also called system client. It serves to administer system-internal objects and central settings.

Explanation: Object execution is not based on the current date but on a pre-determined logical date. Indicating a logical date affects the verification of Calendar conditions. &01 = Name of the object &02 = Logical date

null

Explanation: Forecast names must be unique. &01 = Invalid forecast name

Explanation: Jobs require Login data in order to be executed at the destination system. Solution: Select the adequate Login object in the Job object and restart the Job. &01 = Job object

Explanation: At least one valid user must be specified if Notifications are used. Otherwise, exceptional states cannot be signaled. Solution: Select at least one existing User or UserGroup and add it using the script statement :ADD_ATT.

Explanation: The user specified in the Notification has been deleted meanwhile. Solution: Select another recipient for Notification messages or add it using the script statement :ADD_ATT. &01 = Notification object

Explanation: There is no message text! Solution: Enter the particular message for the user in the "Attributes" tab. You may also specify the text using the script element :PUT_ATT (CALL_TEXT). &01 = Notification object &02 = Client

Explanation: Restarting an object requires the indication of the RunID of an execution that has already ended. &01, &02 = Name of the object &03 = Invalid RunID

Explanation: &01, &03 = Workflow object &02 = Running number within the Workflow

Explanation: &01 = Workflow object &02 = Running number within the Workflow &03 = Name of the object which is the external dependency

An AgentGroup has to be resolved for the calculation of a forecast. This requires a valid statistics entry (user, task, etc.) that is linked to the forecasted task.