Traceability

Traceability ensures logical data integrity, that is, you can trace your data across your entire system, from its current status back to its original source. In PLA 3.0, you can require users to specify why they modify documents and protected values to improve traceability and protect data from intentional and unintentional changes.

Changes to documents section

Tip: You can edit the list of available templates by clicking Edit.

The following items are available:


Item	Description	Notes
Templates for reasons for change	Provides users with a list of valid reasons for making changes to documents.	When users save a document, they can either type the reason into a text box or select an option provided by the Template list.
Request reason for change	Specifies whether users who save documents need to explain why they made changes. If so, the Reason for change dialog opens. Available options: Never: Users cannot provide a reason for their changes. Optional: Users can enter a reason for their changes. Always: Users cannot save documents without entering a reason for their changes. Always after initial saving: After saving new documents for the first time, users cannot save documents without entering a reason for their changes.	Users can leave the Reason for change dialog empty and still save the document.
Templates for reasons for move	Provides users with a list of valid reasons for moving documents.	When users move a document, they can either type the reason into a text box or select an option provided by the Template list.
Request reason for move	Specifies whether users who move documents need to explain why they want to do so. Available options: Never: Users cannot provide a reason for the move. Optional: Displays the Template list and Reason text box when users move documents, allowing them to enter a reason for the move. Always: Users cannot move documents without entering a reason for the move.	Users can leave the Reason empty and still move the document.
Templates for reasons for delete	Provides users with a list of valid reasons for deleting documents.	When users delete a document, they can either type the reason into a text box or select an option provided by the Template list.
Request reason for delete	Specifies whether users who delete documents need to explain why they want to do so. Available options: Never: Users cannot provide a reason for the deletion. Optional: Displays the Template list and Reason text box when users delete documents, allowing them to enter a reason for the deletion. Always: Users cannot delete a document without entering a reason for the deletion.	Users can leave the Reason empty and still delete the document.

Changes to protected values section

Values imported using Data Acquisition Modules and Import Modules are considered as protected values in PLA 3.0.

Tip: You can edit the list of available templates by clicking Edit.

The following items are available:


Item	Description	Notes
Templates for reasons for change	Provides users with a list of valid reasons for making changes to protected values.	When users change a protected value, they can either type the reason into a text box or select an option provided by the Template list.
Manual change	Specifies whether users can change protected values and, if so, whether users need to explain why they made changes and whether they have to provide their user name and password. Available options: Forbidden: No changes are permitted. In the Observations table and related data views, protected values are grayed out and not available for editing. Permitted with reason and signature: Changes are permitted, but users need to provide a reason for their changes and enter their user name and password. Permitted with reason: Changes are permitted, but users need to provide a reason for their changes. Permitted: Changes are permitted.	With this setting, the dialog displayed to prompt users depends on how signatures are set up. Users are always prompted to enter a reason for their changes and their password. In addition, users need to enter their user name if the Requires user name option is enabled on the Signatures tab. Irrespective of the option you select, PLA 3.0 adds an annotation to protected values that have been modified. To display the annotation, right-click the value in the Observations table and select the Show annotations option from the context menu.
Change by import	Specifies whether data acquisition processes are permitted to change protected values. Available options: Forbidden: No changes are permitted. In the Observations table and related data views, protected values are grayed out and cannot be modified by another import or data acquisition. Permitted: Changes are permitted.	Irrespective of the option you select, PLA 3.0 adds an annotation to protected values that have been modified. To display the annotation, right-click the value in the Observations table and select the Show annotations option from the context menu.
Change technical outlier state	Specifies whether users can change the technical outlier state (true or false) of observed values and, if so, whether users need to explain why they made changes and whether they have to provide their user name and password. Available options: Forbidden: No changes are permitted. In the Observations table, technical outlier states are grayed out and not available for editing. Permitted with reason and signature: Changes are permitted, but users need to provide a reason for their changes and to enter their user name and password. Permitted with reason: Changes are permitted, but users need to provide a reason for their changes. Permitted: Changes are permitted.	With this setting, the dialog displayed to prompt users depends on how signatures are set up. Users are always prompted to enter a reason for their changes and their password. In addition, users need to enter their user name if the Requires user name option is activated on the Signatures tab. Irrespective of the option you select, PLA 3.0 adds an annotation to technical outlier states that have been modified. To display the annotation, right-click the value in the Observations table and select the Show annotations option from the context menu.