About Policies

A policy is a set of rules that govern simulation objects. Policies define the lifecycle of an object and the conditions required to move through the stages of its life. A combination of the policy and specific access permissions defines who has access to an object, what levels of access are available, and when access is permitted. For more information, see 3DEXPERIENCE Web Apps - Classic: Lifecycles.

Process Composer objects use the following policies:

Simulation Process

The Simulation Process policy provides five lifecycle states, as shown in the following figure:

The Private state represents the simulation process before it is made available. The In Process state represents the simulation process while it is being worked on. The Complete state represents the simulation process after it is complete. The Released state represents the simulation process after it is released. The Obsolete state represents the simulation process when it is no longer relevant.

Simulation Activity

The Simulation Activity policy provides three lifecycle states, as shown in the following figure:

The In Process state represents simulation activity while it is being worked on. The Complete state represents the simulation activity after it is complete. The Obsolete state represents the simulation activity when it is no longer relevant.

Experience, Attribute Group, and Connector

The Experience, Attribute Group, and Connector policies provide five lifecycle states, as shown in the following figure:

Document

The Document policy has one state, called Exists, as shown in the following figure:

Job

The Job policy has one state, called Created, as shown in the following figure:

Simulation objects can be modified only when they are in the Private, In Process, or Development state. Access to the object is read-only when it is in any other state.

For more information, see the People & Organizations and Content Guide.