The table shown below describes the XML-file structure of an Include objectAn Automation Engine object type for a script that is frequently used in more than one object. and explains the individual elements.
Element |
Description |
---|---|
uc-export |
Main element of the export file clientvers = Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. version in which the export file was created |
JOBI |
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. = The client. |
HEADER |
XHEADER in executable objects HEADER = in active, passive and system objects see object types The attribute "stateThe state a package or a task currently is in." is used system-internally and must not be changed. |
Title |
User-defined, max. 255 characters |
Created |
Format: |
Modified |
Format:
|
LastUsed |
Format: |
SCRIPT |
only in executable objects Exception: In Event objects, it is the "!Process" tab. The attribute "state" is used system-internally and must not be changed. |
MSCRI |
Content of the Process tab |
DOCU_Title |
in all objects (DOCU_Title) The attribute "state" is used system-internally and must not be changed. The attribute "type" shows the type of documentation: text = normal documentation |
DOC |
Content of the Documentation tab Depending on the documentation type, the CDATA section contains the text or the XML structure. |
See also:
Export file of an Include object
XML-File Structure for Imports and Exports
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |