Understanding What is Captured by an Experience

The following figure shows the structure of a simulation process:

The structure of a simulation process.

A simulation process saved as an experience contains the following:

Content

The experience captures all of the content of the simulation process. Referenced content can be either documents or VPM data. A captured document can contain both owned and referenced files; however, only the active version of a file is captured. The experience will become invalid if you delete content that is referenced by the experience.

Simulation Activities

The experience captures all of the simulation activities, including the order in which they appear. The captured simulation activity contains connectors; connector options and their values; and export, import, and delete rules.

Attribute Groups

The experience captures a simulation's attribute groups and the attributes inside the group. In addition, the Leader can add attribute groups to an experience. When the Leader adds an attribute to an attribute group, they can specify whether the Simulation Analyst must provide a value when they instantiate the experience. The Leader can also specify the default value and a range of possible values.

Parameters

The experience captures any parameters that are defined in a simulation process or simulation activity.

Images

The experience captures a simulation's images.

Impact Graphs

The experience captures the relationship of the input to and output from the simulation process.

Jobs

Jobs are not captured by the experience.

Access

By default, additional access rights are not captured by an experience. However, the methods developer with the Author role can configure the experience to capture its additional access rights from the object that is used to create the experience.

History and Issues

The experience does not capture the history or issues from the simulation process.

Routes

The experience captures any routes that are defined in a simulation process or simulation activity.

Process Composer allows a Simulation Methods Developer to sanitize an experience before making it available to a Simulation Analyst by resetting the Impact Graphs, Lifecycle, and Revisions to an initial state. See Preparing an Experience for Release for more information.

The following figure shows the structure of a simulation activity:

The structure of a simulation activity.

A simulation activity saved as an experience includes similar information to a simulation process saved as an experience. In addition to the objects captured by a simulation experience, a experience saved from a simulation activity captures the following:

Connectors and Connector Options

The experience captures the connector that is used by the activity along with the connector options and their values.

Export, Import, and Delete Rules

The experience captures the export, import, and delete rules that are defined by the activity.

Execution Options

The experience captures the execution options that were most recently defined by the activity, such as the execution server and execution directory. The execution options include the step options (whether to continue, pause, or skip a step) and the command line arguments. You cannot switch between SSH and SIMULIA Execution Engine execution servers. See Configuring a Simulation Activity's Execution Options for more information.