Objects can easily be handled through the Explorer. There are four object classes: executable, active, passive and system objects.
Executable objects are objects that can be processed manually or through control mechanisms of superordinate objects. They experience the stages of activation, start and execution.
Symbol |
Object |
Description |
---|---|---|
|
Visualizes various values and conditions within AE or from the systems that are monitored or controlled. |
|
|
Determines conditions and reaction to occurring conditions. |
|
|
Exchanges files of any kind between systems and system platforms. |
|
|
Executes sporadic tasks. |
|
|
Determines the process steps to be executed in a target system. |
|
|
Notifies an operator of an interruption in a taskAn executable object that is running. Tasks are also referred to as activities., the completion of which represents a necessary precondition for the execution of further tasks. |
|
|
Monitors and controls external jobs that were not started by your system. |
|
|
Starts executable objects at regular intervals. |
|
|
Contains processing instructions that are not processed on a target system and implemented exclusively with scriptA particular Automation Engine object type. elements. |
|
![]() |
Workflow | Compiles single tasks for combined execution via defined conditions and dependencies. |
Active objects are objects whose contents can be modified manually or while processing an executable objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task.
Symbol |
Object |
Description |
---|---|---|
|
Defines calendarAn Automation Engine object type that defines a set of days based on calendar keywords. days that can be considered as starting conditions when executing tasks. |
|
![]() |
Queue |
Defines the maximum number of parallel running tasks and the corresponding priority. |
|
Synchronizes executable objects on the basis of defined conditions and actions. |
|
|
Stores values statically or retrieves them from a data source dynamically. |
Passive objects are objects whose contents are defined by 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.. They are static. Their contents cannot be modified when processing an executable object but they are still used.
Symbol |
Object |
Description |
---|---|---|
|
Defines a complete set of characters. |
|
![]() |
Dashboard | This represents a dashboardQuick overview, depending on context. Holds zero or more widgets which is used in the product Enterprise Control CenterAutomic's web application that provides a single, browser-based interface for the ONE Automation platform.. |
|
Administers documentation that do not refer to a single object. |
|
![]() |
Filter | Contains filter definitions for the contents of reports and external files. |
|
Contains commonly used processing instructions from AE Script for shared use through objects. |
|
![]() |
Period | Used to further determine the "Execute Recurring" option available for executable objects. |
![]() |
PromptSet | Input mask that can be assigned to executable objects and which reads user values during the activation process. |
![]() |
Storage | Central file storage (binary data). |
![]() |
StyleSheet | Formats XML reports. |
System objects serve to administer your system.
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |