Templates and Simulation Companion Custom Applications

A Simulation Companion simulation process is a process with a Simulation Kind attribute set to adhoc. A Simulation Companion simulation process must contain an Internal Data category. The data stored in the Internal Data category are owned by the simulation process and appear as managed data in Simulation Companion. When you drag data into managed data, you are uploading data into the Internal Data category of the simulation process. Similarly, when you create a reference to data from managed data, you are adding referenced content to the Internal Data category of the simulation process. (The simulation process can contain additional data categories, but the Internal Data category is the only category used by Simulation Companion. See Process Composer (web): Data Categories for a description of data categories.

A Simulation Companion simulation process contains one or more simulation activities, and a simulation activity can contain any of the data categories. The simulation activities are used to create the custom jobs that you see in the Simulation Companion user interface.

When you add a new custom application in Simulation Companion, the custom applications that are available to you are Simulation Companion simulation templates. To be available as custom applications, these templates must be produced from a simulation activity within a simulation process, and not from the process itself. The template is instantiated, and the new simulation activity is added to the simulation process. The simulation activity also contains only an Internal Data category; however, this data is not visible from Simulation Companion. The simulation activity can contain the following steps:

• A step containing a download rule.
• An OS Command adapter that has been predefined to execute a specified command.
• A step containing an upload rule.

When you configure the custom application, such as by selecting the 3DOrchestrate Station station on which to execute or by defining the command line options, Simulation Companion saves that information in the simulation activity's execution configuration. As a result, the same configuration is available when you open the process with Simulation Companion at a later date.

You create a Simulation Companion simulation template by saving a simulation process as an template using Process Composer or Process Experience Studio and by setting the type of the template to be adhoc.