Preparing an Experience for Release

The Simulation Methods Developer may have to experiment with an experience and its simulation process and activities, resulting in files and lifecycle states that should not be instantiated by the experience. To prevent a Simulation Analyst from instantiating an unfinished experience, the Simulation Methods Developer should create the experience in a dedicated protected collaborative space to which the Simulation Analyst does not have access or credentials. In a protected collaborative space, only data that has a lifecycle state of released is visible to users in the same organization outside of the authoring collaborative space.

The table below summarizes the visibility of data across different types of collaborative spaces at different maturity levels. Data that is private is visible to only the Simulation Methods Developer; data that is public is also visible to the Simulation Analyst.

Collaborative Space Visibility	Maturity State
	Private	In Work	Frozen	Released	Obsolete
Public	Private	Public	Public	Public	Public
Protected	Private	Private	Private	Public	Public
Private	Private	Private	Private	Private	Private

If the Simulation Methods Developer creates the experience in a protected collaborative space, other members of the same organization, such as a Simulation Analyst, cannot see or instantiate the experience until it is promoted to the released state. In addition, any content that is referenced by the experience while it is being developed in the private state by the Simulation Methods Developer must also be promoted to the released state, or made available in another public collaborative space, so that it can be accessed by the Simulation Analyst.

A Simulation Methods Developer can copy or revise an experience in the development (in work) state. However, if they need to modify the experience after it has been released, they cannot demote it back to the development state if an object exists that was instantiated from the experience. The experience can be demoted back to the development state only after the object is deleted.

When a Simulation Methods Developer has finished developing a new experience, Process Composer allows them to do the following:

Remove Output Files

Remove any output files that were generated while testing the experience. This operation will remove any file that was set as output or input/output when the Simulation Methods Developer was configuring an impact graph. See About Impact Graphs for more information.

Set Entities up to Date

Set all entities as up-to-date if they became out of date during the testing. When the Simulation Analyst instantiates the experience and views the impact graph for a resulting simulation process or activity, all entities are shown as up-to-date.

A simulation process can reference a simulation document. However, the document has only a single lifecycle state—Exists—and cannot reside in the same workspace as the process. If a Simulation Analyst is creating the process by instantiating the experience, they must be able to access the referenced document. The Simulation Methods Developer should place the document in a public workspace, which will provide access to the entire organization, or they must grant individual access rights to users that need to view the document.