Automapping context items with called process inputs and  outputs


The TrueSight Orchestration Development Studio application can automatically map local context items in a process to the input parameters of a called process. TrueSight Orchestration Development Studio can also automatically map the output parameters of a called process to local context items.

Input parameters for the called process

If local context items from the calling process have the same names as the input parameters for the called process, TrueSight Orchestration Development Studio automatically maps them to each other. The program makes the mapping when you connect the called process to the calling process with the gray process line. TrueSight Orchestration Development Studio displays a message stating the number of items automatically mapped.

Tip

An automapped status message is displayed for 20 seconds in the corner of the window. This message can be viewed by clicking the History link on the bottom of the window.

If any of the input items were not automatically mapped, you can map them by hand.

Output parameters for the called process

If local context items from the calling process have the same names as the output parameters for the called process, TrueSight Orchestration Development Studio automatically maps them to each other. The program makes the mapping when you drag the called process to the process canvas.

If there are no local context items with the same names as the output parameters from the calling process, TrueSight Orchestration Development Studio creates matching context items and automatically maps them to the output parameters. You do not need to map any output parameters by hand.

TrueSight Orchestration Development Studio does not automatically create a mapping to a global context item, even if the name of the global context item matches the name of the output parameter.

Related topic

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*