User Guide > Objects > Alphabetical Listing > General Tab

General Tab

You can use the General tab in order to assign an alias name and to set time checkpoints for 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."] tasks. If a taskAn executable object that is running. Tasks are also referred to as activities. has not started until the specified time, the objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task that is defined in the Do section will be activated. 

Note that the checkpoint will be verified even when the task is inactive.

 

For example:
The above task activates the object MM.CALL.DAY if it has not started until 4 am at the next day.

Description

Field/Control

Description

Alias

The name of the workflow task. This name should be displayed instead of the actual object name.

The alias name is used in the Workflow Monitor, the Activity Window and in the statisticsThis is a list of a task's previous runs.. Messages use the actual object name.

The same rules apply for the alias and for an object name. They are limited to 200 characters and only the following characters are allowed: A-Z, 0-9, $, @, _, -, . 

You can use the setting ALIAS_SPECIAL_CHARACTERS in the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_CLIENT_SETTINGS in order to allow more characters in the alias name.

Predefined variables, placeholdersfor Variable objects, PromptSetvariables and object variables can be used in an alias name. These variables always refer to the workflow. The characters &, { and } must not be used in alias names. Variables are replaced when the workflow is activated. When you specify an invalid variable, an error will occur when you start the workflow. Click in order to call the variable dialog.

Predefined variables that are used within the Variable object (in SQL statements), and whose values were accessed through placeholders in the alias names, refer to the workflow.

In the UserInterface settings, you can determine whether the dialog in which you can define an alias should open when you add a workflow task using the drag and drop functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,…, and when.

No alias can be used for the START and END object of workflows.

If you searchfor object uses of workflow, you must specify the alias name if there is one. If this alias name includes variables, you must also specify them in your search.

You cannot change the alias name in the modification mode of active workflow. The same rule applies for tasks that are newly added.

Time Checkpoint

Activate this check box in order to set a time checkpoint.

The following settings are available if Time Checkpoint is active:

If start until + ... Day(s)

The number of days starting on the  real date(= top workflow's generation time).

Examples:
0 days = At the day of the real date.
2 days = Two days after the real date.

Allowed values: 0 - 99

Time: ... not possible

Checkpoint time.

If the task has not started before this time, the object that is specified in the Execute section will be activated.

TimeZone

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

Execute

The object that should start if the checkpoint is exceeded.

Enter the object name or call it directly from a small Explorer window (refer to the three dots to call it).

Rollback  
Enable Rollback

Activates or deactivates the Rollback function for this task.

A Rollback also requires the settings of the Rollback tab to be activated and defined.

Deployment These options are only available when the clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type.'s Deployment function is active (UC_CLIENT_SETTINGS - DEPLOYMENT_CLIENT setting).
Run per Patch

Only useful when the task is part of a component workflowA workflow which should be executed for a component of an application within one ore more application workflows for installing, udating or removing the application..

Setting this option has the effect that the task will be processed in a serial order for each patch that is defined in the Automic Release AutomationAutomic Release Automation (ARA), is an end-to-end solution for planning, coordinating and automating software release processes, including automated deployment of applications across large-scale server environments and covers all mentioned use cases. [Formerly called "Application Release Automation", "Release Manager" and "Deployment Manager"].

Run per Deployment Target

Only useful when the task is a component workflow.

Possible options: "n/a", "serial" and "parallel"
Depending on the option that you select, the component workflow will be processed serially or in parallel order for each Deployment Target.

Task Prompts

For more information about these options, see the description of the Variables & Prompts tab.

Note that these settings will also affect whether the parameter dialog of RA jobs is displayed or not.

Request task parameters Displays the PromptSet dialogs of the workflow task.
Parameter evaluation at workflow generation With this option being activated, the PromptSet dialogs will already be called and PromptSet values be resolved when the workflow is generated.

Display in the Workflow and its Monitor

The tooltips (properties) of the workflow tasks display the time checkpoint's usage with a P character.

 

 


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

Copyright © 2016 Automic Software GmbH