About the Store Chooser

Prior to 3DEPXERIENCER2014x, the PLMPolicyChooser.xml file defined the chooser for both the policy and store. As of 3DEPXERIENCER2014x, the policy is determined using a business rule. For information about defining the policies used for objects, see 3DEXPERIENCE Platform Customization Roadmap: Customization Upgrade.

A single policy can govern multiple object types, and a single object type can be governed by multiple polices. A single instance of an object, content created by users, can only be governed by a single policy. The choice of policy determines the lifecycle and security aspects of the content.

In many web apps, when a user creates or modifies content, the user can often select from the list of policies that could govern that object, and the vault used to store files checked into content. Depending on the specific use case, the app page can define which policies are available, or restrict the policy to a single choice that cannot be changed. For native apps, users cannot choose the policy when they create content and they cannot choose the store used to save files checked into content.

Usually, the business process determines which policy should be used for specific content and which store should be used to save files. The policy and store chooser lets you define these business processes, and prevents users from accidentally selecting a wrong policy or store.

The policy choice defined by the chooser is invoked when a user creates content, either by creating or duplicating content, or by importing the content (Import As Ref), but not when versioning content. The versioned content always uses the same policy.

The store choice is invoked each time a file must be saved.

The store chooser is defined in one of these files:

• Baseline behavior: PLMPolicyChooser@team.xml
• Customer-specific environment: PLMPolicyChooser@vpm.xml
• No specified solution: PLMPolicyChooser.xml

The file must be deployed in the server runtime view. At installation, the default file is deployed in your web application path:

<application_server>/webapps/enovia/WEB-INF/classes/vplm/policychoice

You can edit these files to define the store chooser for your business processes. The file contains a <stores> definition that includes a series of case conditions and an optional default case. When saving a file, the app checks for a matching case condition, and if not found, it uses the default. If no cases match the context of saving the file and no default has been defined, the file cannot be saved.