Simulation Document Lifecycle

When you create a document inside a simulation process or activity, you create a document that is owned by the simulation process or simulation activity, known as an owned document. The access rights to the document are inherited from the process or activity. Similarly, the lifecycle state of an owned document is inherited from the lifecycle state of the process or activity. This Simulation Document has a "Simulation Document Owned' policy and displays the state "Exists", but the lifecycle state is inherited from the process or activity that owns it.

When you create a document outside of a simulation (for example, in a Bookmark Root), the Simulation Document has a "Simulation Document" policy and a multistate lifecycle. The policy provides access to the owner and any others to whom the owner granted access as per the lifecycle state of the Simulation Document.

For more details about working with simulation processes, see the SIMULIA Process Composer (Web) User's Guide.

The Simulation Document lifecycle includes these states:

This page discusses:

Private

The Private lifecycle state makes an object semihidden and modifiable only by the owner. Private simulation documents are accessible only to the owner and are not shared in the collaborative space. The owner of the simulation document can demote it to the Private state. When the owner promotes the simulation document to the In Work state, members of the collaborative space can access it.

If the simulation document is created in a public collaborative space, users with the Author baseline access role can access the simulation document as can users with a customer-specific access role that allows that you to create simulation documents.

In Process (or In Work)

The simulation document, and new versions of simulation documents, are created in the In Process state and can be modified or deleted by the owner. This state represents the simulation document while it is being developed, and all members of the collaborative space can modify the simulation document. The owner can demote the simulation document to Private or promote it to Complete; the Leader can promote the simulation document to Released.

Complete (or Frozen)

The simulation document is complete and being reviewed for approval. All members of the collaborative space have read-only access. Users can demote and promote simulation documents between the In Work and Frozen states and from the Complete to Released states without creating new versions. The Leader can demote the simulation document to Private or promote it to Released.

Released

The simulation document is available for production or delivery. Other protected collaborative spaces can access the simulation document. Released simulation documents cannot be deleted or demoted. When the simulation document is no longer valid, the owner promotes it to the Obsolete state.

You use the Released state to share the object with other collaborative spaces within the organization. The Released state is most often used with protected collaborative spaces, where the access rights change between the Frozen and Released states. In public and private collaborative spaces, there is no access difference between the Released state and the Complete state.

Obsolete

The simulation document is no longer used and must not be used in a collaborative space. The owner can delete the simulation document in the Obsolete state or create a new version of the simulation document.