Data Editability

There are some concepts you must be familiar with when editing data in a Coexistence context. General attributes and lifecycle attributes (versioning, maturity and P&O) along with operations such as creating, updating and deleting new versions are concerned by the sections below.

This page discusses:

How to Protect
What to Protect
Common Rules

How to Protect


	Responsibility	Actor	Description
Methodology	Customer	End user	Specific scenario to be set by customers depending on their specific needs
Deployment customization	Customer	Administrator	For example, P&O rights are available for purposes of data protection. Customization can be based either on a customer type or specific P&O settings.
Embedded product core functionality	Dassault Systèmes	None	Protection is provided by Dassault Systèmes.

What to Protect


Attributes / operations to be protected	Protection
Core and Customer attributes	Protected by P&O rules on dedicated user, customer type or customer attribute
Lifecycle attributes	Protected by P&O rules on dedicated user, customer type or customer attribute
Versioning operations	Protected by P&O rules on dedicated user, customer type or customer attribute
Delete operations	Protected by P&O rules on dedicated user, customer type or customer attribute

Common Rules

Important: Data shared by multiple PDMs is considered to have one and only one Master PDM.


	Master PDM Side	Non-Master PDM Side
Granted	Core and customized attribute edition Maturity and P&O edition Create, update, delete and new version operations	Customer attribute edition. Even if a specific behavior is activated or customized attributes do not belong to the Master PDM. Maturity and P&O edition. As far as the given edition does not interfere with the Coexistence process. Neither options nor Business Logics must be edited. See Data Behaviors. Create operations Update operations. Restricted to specific customer attributes only. Even if a specific behavior is activated or customized attributes do not belong to the Master PDM.
Not granted		Core attribute edition Maturity and P&O edition. Whenever the edition is used within the Coexistence process through either options or Business Logics. See Data Behaviors. Update operations on core attributes Either deletion or creation of new version operations

Warning: Maturity and P&O can be managed differently depending on the targeted scenario. See Data Behaviors.

In scenarios such as Synchronized management - ISO and Synchronized management - Mapping, maturity and P&O can be edited on the Master PDM using the common rules.
In a scenario such as Autonomous management, maturity and P&O are managed independently either on the Master or non-Master PDMs. Therefore common rules do not apply.