These two Variable (VARA) objects define commands for calling internal objects and allow you to send the data contained in an object/task to another executable object available in the Automation Engine. They are supplied with system client 0000 and can be copied to other clients and customized as needed.
With these variables you can create and specify a new, customized context menu option to send the object data to another object in the Client (Key). You also create the executable object to which the data will be sent for further processing (Value).
-
UC_SENDTO affects objects
The context menu actions you defined here are available in the Process Assembly perspective.
-
UC_SENDTO_ACT affects tasks
The context menu actions you defined here are available in the Process Monitoring perspective.
Once defined, the Send to command is also available from the various monitors, from the Administration perspective perspective and in the Global Search function.
Example
Two keys have been defined, CSV2VARA and VARA2CSV. They result in two additional sub menu options that call the CSV2VARA#SCRI_SENDTO and VARA2CSV#SCRI_SENDTO objects respectively:
As a result, theSend to is available in the Process Assembly perspective. Right-clicking an object and selecting Send to opens a sub menu where the specified executable objects are displayed, to which the data can be sent for processing:
Sending Data for Internal Handling
You can send the object/task code to other executable objects available in the Automation Engine. In this case, in the variable Value you specify the name of the object to be called. It is also possible to select multiple objects/tasks in bulk and send their code to an executable object. In this case, the specified target object is started for each highlighted object/task.
The following variables are automatically supplied in the read/input buffer:
-
&OH_IDNR#
Object code
-
&NAME#
Name of the object/task
-
&TYPE#
Type of the object/task
Additionally for tasks:
-
&RUN#
Run number (RunID) of the task
-
&LNR#
Placement in Workflows and Schedules
-
&PARENT_RUN#
Run number (RunID) of the superordinate task
-
&PARENT_NAME#
Name of the superordinate task
-
&PARENT_TYPE#
Object type of the superordinate task
Use the script statement :READ to read these variables. In this case, make sure that the Generate Task at runtime option is not activated in the Attributes page of the object definition. For more information, see Generate Task at: Activation time / Runtime and Generating at Activation or at Runtime.
Example
:READ &NAME#,,
:PRINT &NAME#
:READ &TYPE#,,
:PRINT &TYPE#
:READ &PARENT_RUN#,,
:PRINT &PARENT_RUN#
See also: