Introduction
 

As part of the approval process, the signature is essential for customers that work in a regulatory environment and follow FDA regulations.
Electronic Signatures (ESIGN) is equivalent to handwritten signature, however, the ESIGN is more secure, saves time and money and provides an opportunity to eliminate paper usage, and is more environmentally friendly.

In 3DEXPERIENCE platform, you can enable the support of ESIGN for task approval processes. The authentication is done by 3DPassport based on user name and password input.

E-Signature Management setting

To support the implementation of ESIGN when approving tasks, in both on-cloud and on-premise environments,  a new setting called “‘E-Signature Management’ “ is introduced starting from R2022xGA release,  that is available from the ‘Collaborative Spaces Configuration Center’ widget.
 

Note: This new setting replaces the property key ‘emxFramework.Routes.EnableFDA’, which was available on-premise only.

The E-Signature Management setting consists of three options:

• Option #1 - Not required for approval tasks
   

  

  This is the default option that determines that none of the task approval would need ESIGN authentication.
  
   

• Option #2 - Required for approval tasks 
   

  

  
   

  When this option is set, then all task approvals require ESIGN authentication.
  When approving a task, you need to enter your name and password and check the option that you understand that by doing that you are applying your electronic signature, which is equivalent to your handwritten signature.
   

  

  
   

   

• Option #3 - Specified in route template
   

  

  
  This is a new option that enables the ESIGN authentication on selected Routes only.

  The definition is on the Route Template level.
  When creating a new Route Template of type Approval or Standard, you can define if ESIGN is required or not by using the ‘Approval with Signature’ option.
  This applies for all tasks approvals of Routes created by using this Route Template. 
   

  

  
   

   

  The attached video illustrates a sample use case of the third option ‘Specified in route template’