Script Function: Supplies the run number (RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component .) of the superordinate taskAn executable object that is running. Tasks are also referred to as activities..
SYS_ACT_PARENT_NR ([Activation type])
Syntax |
Description/Format |
---|---|
Activation type |
Allowed values: |
Return codes |
---|
RunID of the superordinate taskThere are various ways of activating objects. The originator of the activation is referred to as the superordinate task (parent). |
This scriptA particular Automation Engine object type. functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… supplies the run number (RunID) of the superordinate task (parentThere are different ways of activating objects. The originator of an activation is referred to as the superordinate task (parent). See also: Child; Children). In the case of manual activation, this is 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.'s Session-ID.
If no activation type is indicated, this script function supplies the processor.
In order to facilitate that the name of a groupAn Automation Engine object type that integrates tasks so that they can be processed together. may be retrieved, "Generate at Runtime" (Attributes tab) must be activated in the task using this script function. Otherwise, the name can only be retrieved for jobs in post process.
The first example checks whether the task runs in a group, 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."] or schedule. If so, the run number (RunID) of this task is written in the activation protocol. If there is no superordinate task, the corresponding entry is made to the activation protocol.
:SET &NR#
= SYS_ACT_PARENT_NR()
:IF &NR# =
" "
: PRINT "No parent"
:ELSE
: PRINT "RunID of parent is
&NR#."
:ENDIF
The second example determines the Activator of a task. If it was activated by a task, the run number (RunID) of this task is shown in the activation protocol. In the case of manual activation, the protocol shows the RunID of the particular user session.
:SET &NR#
= SYS_ACT_PARENT_NR(ACT)
:PRINT "RunID of parent is &NR#."
See also:
Script element | Description |
---|---|
Supplies the name of a superordinate task. | |
SYS_ACT_PARENT_TYPE | Returns the 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 of the superordinate task. |
Script Elements - Activation Data
About Scripts
Script Elements - Alphabetical Listing
Script Elements - Ordered by Function
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |