UC_SENDTO and UC_SENDTO_ACT - Handling Objects and Tasks Internally

In these two variables, you can define commands for calling internal objects.

This topic provides information on the following:

Overview
Sending Data for Internal Handling

Overview

Client 0 is supplied with a number of variables that you can copy to your own client and customize to meet your needs.

The UC_SENDTO and UC_SENDTO_ACT variables allow you to send the data contained in an object/task to another executable object available in the Automation Engine.

With these variables you can create and specify the following:

A new, customized context menu option to send the object data to another object in the client.

You enter the new menu command in the variable Key.
The executable object to which the data will be sent for further processing.

You enter the name of the executable object in the variable Value.

UC_SENDTO affects objects, therefore, the context menu actions you defined here are available in the Process Assembly perspective.

On the other hand UC_SENDTO_ACT affects tasks, therefore, 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 and in the Global Search function.

Example

In this example, two keys have been defined, CSV2VARA and VARA2CSV. They will 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:

Variable	Description
&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 at runtime option is not activated in the Attributes page of the object definition. See Generate Job at.

For example:

:READ &NAME#,,
:PRINT &NAME#

:READ &TYPE#,,
:PRINT &TYPE#

:READ &PARENT_RUN#,,
:PRINT &PARENT_RUN#