PPR Context Save in Database

It is possible to exclude the PPR Context from the list of objects saved in the database. This significantly reduces the quantity of data created in the database. It also enables working without a persistent PPR Context, even though this is not required.

This page discusses:

Standard Save Mechanism

When the save is done using Share > Save > Save, three scopes are available in the Save dialog box:

  • Current Editor: the list of objects returned by the current editor in the session can be saved
  • Session: the list of objects returned by all editors opened in the session can be saved
  • Selected: the list of objects returned by the UI active object can be saved.

When the save is done using Share > Save > Save All, data is saved according to the Session scope.

Save PPR Context Option

The save of PPR Context data in the database is managed using the Enable PPR Context Propagation in Database option in the Me > Preferences > App Preferences > Simulation > Digital Manufacturing Apps Common Services > Simulation and Planning Apps Common Services > PPR Context.

If this option is selected, modifications made to the PPR Context are saved in the database according to the standard save mechanism.

If this option is not selected, the PPR Context is excluded from the objects to be saved for the Session and Current Editor scopes. This significantly reduces the quantity of data created in the database.

Note: If the option is not selected, it is not possible to change the current Collaborative Space during the session. As to change the current Collaborative Space during a session, all objects in memory must have been propagated to the database.

For the Selected scope, the list of objects to save is still built from the UI active object. This scope enables the support of the functionalities (such as 3D XML import/export and MSR simulation) that require a persistent PPR Context.