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 "FileTransfer" objects. All settings that are necessary to execute a file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object). are defined in this tab.
Object: FileTransfer
Object class: Executable objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task
Object
type (short name): JOBF
Field/Control |
Description |
---|---|
Attributes | |
Group |
If the file transfer 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. If there is no entry, the file transfer is activated immediately. Note that the entry that is specified here is not considered if the file transfer starts through a Workflow object, a Schedule object or as a recurring task. |
Queue | Selection of a Queue object in which the file transfer should be processed. The file transfer automatically starts in the Client Queue (object name: CLIENT_QUEUE) if nothing has been specified in this field. |
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 it in your processes. |
Consumption ... (Resources) |
Resources that are consumed during the execution. Allowed values: "0" to "99999"
|
AE priority ... (0-255) |
Priority that should be used to execute this file transfer in AE. Allowed values: 0 to 255
|
TimeZone |
The time zoneIt defines a local time. A particular Automation Engine object type. that should be used. |
Attribute Dialog |
If this check box is selected, a dialog will be displayed at activation in which you can modify the attributes for the current execution of the file transfer. |
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 check box if the object should not be generated at activation time but at runtime. |
Tasks running parallel |
|
Max ... |
Setting that defines the maximum number of parallel executions for this file transfer. Allowed values: 0 to 99999 Examples: Max. "1" - At any time, not more than one file transfer execution must be available. |
Else: Wait Abort |
Instruction that defines how this file transfer should be handled if the execution exceeds the specified maximum number of tasks that can run at the same time. Wait = The file transfer waits until execution
is possible. |
Deactivate autom. when finished |
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 settings for automatic deactivation apply for file transfers that are processed as part of this workflow. These settings overrule the settings of subordinate tasks. If the Activity Window includes many tasks that are not automatically or manually deactivated when they are finished, this can negatively affect performance and the Activity refresh cycle. |
Never |
The file transfer is not automatically deactivated and remains visible in the Activity Window after it has been executed. |
After error-free execution |
The file transfer is automatically deactivated after its successful execution. Interrupted file transfers remain visible in the Activity Window and must be deactivated manually. You can additionally specify a particular statusThis represents the condition of a task (such as active, blocked, generating). for the error-free execution and a time delay for de-activation. Do so by using the fields Error-free status and/or Time delay ... Minutes. If this value is set also via the UC_CLIENT_SETTINGS, the setting in this field will be considered according to the following rules:
|
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 file transfer is automatically deactivated after a successful restart. Previously interrupted file transfers are also deactivated. You can additionally specify a particular status for the error-free execution and a time delay for de-activation. Do so by using the fields Error-free status and/or Time delay ... Minutes. If this value is set also via the UC_CLIENT_SETTINGS, the setting in this field will be considered according to the following rules:
|
Error-free status |
Status that confirms a successful file transfer execution. If no status is selected, the system-return codes 1900 - 1999 (ANY_OK) represent error-free execution. |
Always |
The file transfer is always automatically deactivated after it has been executed. Additionally, you can specify a time delay for a deactivation in the "Time delay" field. If this value is set also via the UC_CLIENT_SETTINGS, the setting in this field will be considered according to the following rules:
|
Time delay ... Minutes |
The file transfer is automatically deactivated after a specified number of minutes. You can manually deactivate it before this time is over. The time difference only affects file transfers whose execution also resulted in an automatic deactivation. |
Some of the settings that are specified in this tab can be read and modified at runtime. Attributes of this object are accessed by using script elements. If the checkbox "Attribute Dialog" is active, the userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. can influence the attributes. The script accessed the attributes subsequently.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |