Implementing a Quality System Document

Once a document has been approved, you can implement that document.

Important: This app uses electronic signatures to provide an audit trail for certain approvals, as is often required in highly-regulated industries. You cannot delete or modify the personal data contained in the electronic signatures. You should carefully review your use cases associated with electronic signatures to ensure that the specific business requirements associated with them are being met, while still adhering to good personal data management practices.

Before you begin: Open the My Implementations tab. For more information, see My Implementations.

The ESIGN (one-step validation) will be enabled if:

  • The context object has a route and the attribute 'Requires ESIGN' is true for route objects.
  • The context object does not have a route template, ESIGN will be enabled based on the following:
    • If the global E-Signature value is configured as 'Required for approval tasks' or 'Specified in route template,' ESIGN will be enabled.
    • If the global E-Signature value is configured as 'Not required for approval tasks,' ESIGN will not be enabled.

  1. Navigate to My Implementations tab.
  2. From the page toolbar, click Actions > Complete Implementation .

  3. Enter these details:

    Field Name Description
    Implementation Summary Enter an explanation of the implementation of this quality system document.
    Implementation Date Use the calendar tool to select a date.

  4. Click Done.
  5. If ESIGN is enabled, you can validate the implementation using two factor authorization. From the User Verification dialog box, enter your 3DEXPERIENCE ID and password.
  6. Select the check box to confirm that your electronic signature is the equivalent to your handwritten signature.
  7. Click Validate.
    Once your credentials are verified, the 3DEXPERIENCE - Access Control dialog box opens.
  8. Enter the code that you received on the configured device.
  9. Click Validate.

All implementing organizations for a document must complete the implementation before the change action that releases the document can be completed.