Local Save and Restore

Local save is the capability to save your session content in a local storage area (on the computer where the code is executed). It differs from a normal save, which publishes modifications for all users to the database.

The Local Save capability comprises the following functionality:

  • Local save
  • Restore

This page discusses:

Overview

Local Save

The local save capability enables you to save locally, on your disk drive, authoring content loaded in a session but not committed in the database.

It stores the content modified in authoring apps, the layout of the windows, or any content required to recreate the authoring session as it was before the exit.

This capability is activated by default. Specific options allow you to configure local saves. For more information, see Local Save & Exit.

Restore

If you perform a local save, exit your session, and then restart a session using the same logon (same user, role and server), the content restoration dialog appears. You can restore the previously saved session, or start a new session.

If you choose to start a new session, the local save is deleted automatically to ensure persistent content consistency.

If you choose to restore the session, your original session is rebuilt by reopening the content in the same authoring tabs as before the local save. All the content is restored in the same state as before the local save:

  • Authoring modifications that you did not save are restored in the session.
  • Even if the content has been modified by another user in the database, the content reopened is the content that was opened before the local save.
  • Product Finder tabs (Query result, Expand) are not reopened.

The restore capability is also useful as a warm start mechanism after a system crash.

Note: When restoring a session that requires shareable licenses, you can use the different apps only if all shareable licenses granted when you locally saved your session are also granted at restore. If one of these licenses cannot be granted, for example because it is no longer available, no apps can be used, even those associated with a shareable license that has been successfully granted.

Where Is the Local Save Mechanism Visible?

The local save mechanism is visible in the following areas:

  • In the Local Save tab
  • When starting a 3DEXPERIENCEsession
  • In the Share > Save > Local Save commands
  • When you exit the session automatically after a preset period on inactivity, using the Auto Exit option
  • At a planned date and time, using the Planned exit option.

Persistent Content

The local save capability does not prevent full access to the original database. Logging into the database is mandatory before starting to restore content from the local save area.

During a local save, the content saved is all the content opened in the session authoring tabs, including:

  • Opened content, modified or not: product structures, parts, applicative content, processes
  • The layout of the authoring tabs (position and size).

The following content is not saved:

  • Product Finder "silver" tabs (Query Result, Expand)
  • Preferences: CATSettings files are the only reference
  • The undo log
  • Volatile parameters like the viewpoint or the tree expansion

All the session is saved to ensure model integrity and content consistency. Nothing is added in the app to save only a subpart of the session.

Each local save is identified by:

  • The name of the logged user
  • The name of the app
  • The date when the process was started

The local save capability supports upward or downward content compatibility, and local save content is deleted by the migration process from one release to another.

Local save images can contain some required content for the database. Do not delete them directly without using a specific application. It is particularly true when using the editability context. A by-pass is to start a session and refuse to restore the old session image. This action leads to the destruction of the associated files.

Content Restoration

Restoring Content When Starting the 3DEXPERIENCE Normally

If you performed a local save in a previous session, and then restart 3DEXPERIENCE, you can choose to start a new session or restore the previous session, only if:

  • The local save capability is activated.
  • The user attempting to log on already performed a locally saved session, if this session has not been deleted previously, and if the directory used to store the session is available and the files are accessible.

Otherwise, a normal start from scratch is performed.

If the conditions are met, you can choose either to:

  • Restore the session (Restore)
  • Cancel the restore and start the standard session login (New Session)
  • Exit (which allows you to restore the current local save image later)

Moreover, on the left, there is a small preview of the image to restore, informing you when the image was created and the time of last modification. The dialog box also indicates the user owner of the local save image, the server, and the role used to create the image.

Whichever option you choose, you must enter your logon password.

Restoring the Locally Saved Session

First, you have to authenticate by providing your logon password. If the login is successful, authoring content stored in the Temporary Save are restored in session and authoring tabs are reopened with this content. The session is in the same state as it was when the last local save was performed, regarding authoring content only.

Because only one local save session is available, this session will be overwritten the next time you perform a local save.

When logging in, if your username, role, or server does not match the local save information, a message appears, and you can try again.

Starting a New Session

If you start a new session, your own locally saved session is deleted and the 3DEXPERIENCE starts as a regular empty session. The standard login panel appears.

The local save software identifies the Windows session owner and memorizes the application user and the rorolele (not the password). Consequently, each Windows user has its own local save file.

Exit

By selecting this option, the user exits the 3DEXPERIENCE session without login.

Restoring Your Session after a Crash: Warm Start

If a 3DEXPERIENCE session crash occurs, the local save capability lets you restore the locally saved content. When you restart the 3DEXPERIENCE, you can also choose between starting a new session or restoring the previous session.

Deactivating the Local Save Capability

The local save capability is activated by default and you cannot deactivate it during a session. To deactivate the local save capability, clearing the options in the preferences is not sufficient. You must specify the following environment variable in your runtime environment using the Environment Editor: 

PLM_DeactivateLocalSave=TRUE

When you start a 3DEXPERIENCE session, you can no longer choose between restoring a session or starting a new session. When you select the Local Save tab, the following message is displayed: 

Local Save is not activated

To reactivate the local save capability, delete the variable you specified using the Environment Editor, and restart a session.

Limitations

The following limitations apply to local save:

  • Any modification of P&O or security (sharing, security masks,...) between the creation of the local save image and the next start of the 3DEXPERIENCE when the local save capability is activated may lead to unpredictable results. In this case, the local save image is no longer valid. In that case, restart the 3DEXPERIENCE without using local save.
  • The local save capability does not prevent full access to the original database. Logging into the database is mandatory before starting to restore content from the local save area.
  • There is no lock management in the local save area. Concurrent engineering questions are handled between the database and running sessions. Editability is not fully supported.
  • Local save images can contain some required content for the database. They must not be deleted directly without using a specific app. It is particularly true when using the editability context.

    A by-pass is to start a session and refuse to restore the old local save image. This action deletes the associated files.

  • When the Create widget in new tab option is cleared in Me > Preferences> Common Preferences > User Interface > Widget Layout, all the widgets created in different tabs and saved through local save or in offline mode are restored in the same tab.