| Customize the data model |
| Defining objects | | You can create:- subtypes
- customer extensions
- deployment extensions
- attributes
| Use Data Model Customization. For more information, see Model Customization and Specialize Data Model. |
| Determining the naming scheme | | You can select revision naming schemes, or object naming schemes. | |
| Manage the Security Model |
| Creating and allocating policies | | You are not allowed to modify baseline policies. You must create new policies and redirect the policy choice of a given type to the new policy. To do so, use Data Setup to overwrite the business rule that computes the policy when creating an object for native apps. The customized type must be associated to a policy that defines the
following information:
- The lifecycle of the objects, for example Draft, In
Work, Released.
- The format of the revision numbers of the objects, for example
1,2,3.. or A,B,C….
- The store in which the associated streams is stored, if
any
- The permissions on the objects
If you want to reuse an existing policy for the newly
created type, modify the policy to specify that it applies to that
type. This can be done in MQL as a system administration user (for
example creator): MQL<> modify policy "Policy1" add type
"CustomType";
If you want to create a policy, you can do one of the
following : | - Use MQL.
- Allocate the policy using the INFRAAuthorizedPolicies opening. For more information about this opening, see Data Setup: List of Resource Set IDs: Social and Collaborative Apps: Business Logic for Object Typing: Selection of a Policy from a Set of Applicable Policies (INFRAAuthorizedPolicies).
|
| Determining the access mode of attributes depending on access roles | | You can determine the access to object attributes based on the access role of the user. | Use masks. |
| Customize the behavior of apps or of the 3DEXPERIENCE platform |
| Customizing apps behavior | | Apps provide you with resources to adapt their behavior depending on your needs. | Use Data Setup to create your business rules. For more information, see Data Setup. |
| Customizing the behavior of the3DEXPERIENCE platform | | The 3DEXPERIENCE platform provides you with openings to adapt its behavior depending on your needs. | Use Data Setup or the Business Rule Editor. For more information, see Data Setup. |
| Using the maturity graph | | | |
| Manage stores | | For administration reasons, you may need to use different stores and select the store depending on the type. | - Create the store in MQL.
- Select the store using the Policy Chooser.
Note:
There is no web tool to manage stores and vaults.
|
| Handle the visilibity of attributes in the user interface |
| Optional: Ordering attributes in a dialog box | | You can order attributes in the following dialog boxes: - New > Content
- Edit Properties
- Attributes1
| - Win side: Save your .mask file on the server and use the mask compiler.
- Web side: use MQL.
|
| Optional: Reducing the list for given attributes | | Depending on the access role granted, you can reduce the list of possible values for given attributes. | Use the Attributes Valuation Propagation (PLMAttributesPropagation) opening. |
| Managing Icons | | You can associate an icon to a specialized type. | Use the dedicated field when creating a specialization type. For more information, see Creating, Editing and Deleting a Specialization Type. |
| Managing NLS | | You can adapt your user interface in different languages. | For native and web apps, use Manage Translation in Model Customization. |
| Transpose customization to a production environment | | After developing and testing a customization, you must deploy it in a production environment. | - When working with the P&O, use
VPLMPosImport (file import). - When working with Data Model Customization, use the Export and the Import commands. For more information, see Exporting Masks and Importing Packages.
- For masks, copy the file generated by the mask generator.
- Copy the icons manually.
|
| Index | | |
|