User Guide > Objects > Alphabetical Listing > Attributes Tab

Attributes Tab

The Attributes tab is object typeAn individual object is provided for the individual activities: There are User, UserGroup, Notification, Cockpit, CodeTable, Documentation, Event, Agent, FileTransfer, Group, Include, Job, Workflow, Calendar, Login, Client, RemoteTaskManager, Schedule, Script, Server, Sync, Variable and TimeZone objects-specific and is only available in "Workflow" objects. You can use it to define the relevant settings for the workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."]'s execution.

Object: Workflow
Object class:
Executable objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task
Object type (short name):
JOBP

Description

Field/Control

Description

Attributes  

Group

If the workflow should be started by a group, you can select this groupAn Automation Engine object type that integrates tasks so that they can be processed together. here. The workflow is activated immediately if no definition has been made.

Note that the definition that has been specified here is ignored if the workflow starts through a Workflow or Schedule object or as a recurring task.

Queue Selection of a Queue object in which the file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object). should be processed. The file transfer automatically starts in the Client Queue (object name: CLIENT_QUEUE) if nothing is specified in this field.
Children queueA particular Automation Engine (AE) object type. In AE, a queue determines the maximum number of concurrent tasks, their priorities and the order in which tasks should be executed. In ARA, queues are containers for workflow executions that should be executed at a certain time one after another.

Queue object that should be used for the workflow's tasks. The queue of the subordinate tasks is replaced by the value that is specified here while the workflow is being processed. The settings that are made in the individual tasks are used if no value has been specified for "Children queue".

If you select *OWN, the workflow's queue (attribute: Queue) is used for the subordinate tasks.

Int. Account

Specification of an internal account.

Contents do not affect the AE system's internal processing. You can access the attribute "Int. Account" with scriptA particular Automation Engine object type. elements and integrate the values in your processes.

Runtime Parameters  

AE priority ... (0-255)

Priority that should be used to execute this workflow in AE.

Allowed values: 0 to 255
Default: 0

The priority that the administrator has specified in the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_CLIENT_SETTINGS with the key "TASK_PRIORITY" is used if you select value "0".

TimeZone

The time zoneIt defines a local time. A particular Automation Engine object type. that should be used.

Generate at runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start).

Select this checkbox if the workflow should not be generated at activation time but at its runtime.

Re-using agent groupAn agent group combines agents of the same platform. The agents that should be included in an agent group are specified by entering the agent name or via filters. A task that runs in an agent group is processed on one or all of the agent group's agents, depending on the specified mode. A particular Automation Engine object type. calculation

Select this checkbox if workflow tasks of the same agent group should use the same hosts.

Tasks running parallel

 

Max ...

Setting that defines the maximum number of parallel executions for this workflow.

Allowed values: 0 to 99999
Default: 0 (no limit for parallel-running tasks)

Examples: 

Max. "1" - The maximum of one active workflow executions must not be exceeded at any time.
Max. "2" - The maximum of two active workflow executions must not be exceeded at any time.
etc.

Else: Wait Abort

Instruction for the workflow whose execution would exceed the maximum number of parallel-running tasks.

Wait = The workflow waits until it can be executed.
Abend = The workflow is canceled.

Automatically deactivate when finished

The workflow settings for automatic deactivation apply for tasks that run in a workflow.

Workflows do not override the settings of subordinate workflows. If a workflow has been deactivated (manually or automatically), all its sub-workflowA workflow that is part of a different workflow.'s are also removed from the Activity Window.

Attention: Deactivate tasks (automatically or manually) when they finish because a huge number of tasks in the Activity Window would negatively affect performance and the activity-refreshing cycle. 

Note that workflows that end with the statusThis represents the condition of a task (such as active, blocked, generating). "FAULT_OTHER - Start impossible" are always removed from the Activity Window. Settings that have been made for an automatic deactivation are ignored in this case.

Never

The workflow and its subordinate tasks are not automatically deactivated after their execution and remain in the Activity Window.

After error-free execution

The workflow and its subordinate tasks are automatically deactivated after their successful execution. An interrupted workflow including its subordinate tasks remain in the Activity Window. They must be deactivated manually.

You can also set a status for an error-free execution or a time delay for deactivation. Use the combo boxes "Error-free status" and/or Time delay ... Minuten for this purpose.

If this value is set also via the UC_CLIENT_SETTINGS, the setting in this field will be considered according to the following rules:

  • Task delay time = 0: The setting in UC_CLIENT_SETTINGS applies.
  • Task delay time > 0: The setting in UC_CLIENT_SETTINGS is ignored.

After an error-free restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts.

The workflow and its subordinate tasks are automatically deactivated after a successful restart. Previously canceled tasks are also deactivated.

You can also set a status for the error-free execution and a time delay for deactivation. Use the combo boxes Error-free status and/or Time delay ... Minutes for this purpose.

If this value is set also via the UC_CLIENT_SETTINGS, the setting in this field will be considered according to the following rules:

  • Task delay time = 0: The setting in UC_CLIENT_SETTINGS applies.
  • Task delay time > 0: The setting in UC_CLIENT_SETTINGS is ignored.

Error-free status

Status that confirms the workflow's successful execution. If no status has been selected, the system return codes 1900 - 1999 (ANY_OK) stand for an execution without errors.

Always

The workflow and its subordinate tasks are always automatically deactivated after their execution.

You can also specify a time delay for deactivation in the control field of the same name.

If this value is set also via the UC_CLIENT_SETTINGS, the setting in this field will be considered according to the following rules:

  • Task delay time = 0, The setting in UC_CLIENT_SETTINGS applies.
  • Task delay time > 0: The setting in UC_CLIENT_SETTINGS is ignored.

Time delay ... Minutes

The workflow and its subordinate tasks are automatically deactivated after a specified number of minutes. You can also deactivate the workflow manually before the specified period of time. The time delay only affects workflows whose execution includes their automatic deactivation.

Result evaluation per single taskAn executable object that is running. Tasks are also referred to as activities.

 

OK status

Selection field for the end status that is expected for the workflow's subordinated tasks.

Else ...

Select an object that should be executed if the defined OK status of one or more subordinated tasks does not occur.

You can read and modify the settings that have been made in this tab at runtime. Script elements are used to access the object's attributes.

 

See also:

System Return Codes of Executable Objects
User Return Codes of Executable Objects

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH