What About Security Data?

Security Objects

Security objects involved in the definition of security accesses are (the list is not exhaustive):

• policies
• rules
• filters
• expressions.

These objects make it possible to tailor particular security schemes, including P&O object-specific access, access grouping and access inheritance. Please refer to ENOVIA V6 documentation (e.g. Business Modeler Guide) for details concerning the ENOVIA V6 security model.

In order to perform massive data import, a VPLM administrator should take advantage of MQL scripting, i.e. write text-based import files containing MQL statements, and execute these files using the command-line MQL interpreter.

Note: while the import batch exposes P&O business objects, ENOVIA V6 security applies to P&O administrative objects. As a consequence, when defining security accesses for P&O objects in the Business application or MQL scripts, the VPLM administrator will not manage business persons, contexts, organizations, projects or roles, but administrative persons or roles.

Each administration role object has a particular property type that indicates whether it represents a business context, organization, project or role. Since properties cannot be viewed from the Business application, it may not be possible to distinguish "context" roles from "organization" roles, for instance, in that application. The MQL interpreter provides full access to that information and may preferably be used instead in order to author security data.

Please refer to ENOVIA V6 administration documentation (for example, the ENOVIA V6 Query Language (MQL) Guide) for details concerning the MQL syntax of security commands.

Expressions

The following table lists the expressions are delivered via the ENOVIA VPM Multi-Discipline Collaboration Platform and can be used as security filter expressions in policies and rules: