Differences

This shows you the differences between two versions of the page.

usersideinformation:docusignintegration [2018/02/09 09:02]
atadic [Example of the signing process]
usersideinformation:docusignintegration [2018/11/29 09:19] (current)
bdjordje
Line 1: Line 1:
-====== CPQ and DocuSign Integration ======+====== SAP CPQ and DocuSign Integration ======
 \\ \\
  
Line 11: Line 11:
  
 <note Important> <note Important>
-If CPQ has already been integrated with DocuSign prior to may 2017 Release, some changes within DocuSign should be performed. Prior to this Release, when integrating CPQ and DocuSign, a DocuSign custom field had to be created through the DocuSign setup process. That custom field had the same format as placeholder \signhere_{r}\. This custom field is not needed anymore since all the mappings are performed automatically. Therefore, customers with an existing CPQ-DocuSign integration need to delete this custom field within DocuSign. If it remains in DocuSign, the first signer of each document will have to sign the document twice. +If SAP CPQ has already been integrated with DocuSign prior to may 2017 Release, some changes within DocuSign should be performed. Prior to this Release, when integrating SAP CPQ and DocuSign, a DocuSign custom field had to be created through the DocuSign setup process. That custom field had the same format as placeholder \signhere_{r}\. This custom field is not needed anymore since all the mappings are performed automatically. Therefore, customers with an existing SAP CPQ-DocuSign integration need to delete this custom field within DocuSign. If it remains in DocuSign, the first signer of each document will have to sign the document twice. 
 </note> </note>
 \\ \\
Line 28: Line 28:
  
 ==== DocuSign Envelope Expiration ==== ==== DocuSign Envelope Expiration ====
-When document is sent from CPQ to DocuSign, DocuSign Envelope is created and its expiration time is set. Default expiration time is 120 days. This can be changed in **DocuSign settings** > **Preferences** > **Account Administration** > **Reminders & Expirations**.+When document is sent from SAP CPQ to DocuSign, DocuSign Envelope is created and its expiration time is set. Default expiration time is 120 days. This can be changed in **DocuSign settings** > **Preferences** > **Account Administration** > **Reminders & Expirations**.
 \\ \\
 \\ \\
Line 36: Line 36:
  
 ==== DocuSign time out ==== ==== DocuSign time out ====
-Clicking on link received through email, DocuSign recepient token is created for current recipient / signer. Recipient token expires five minutes after it is issued by DocuSign. If a recipient token URL is accessed after token expiration, the user is redirected to CPQ callback URL with event code //"TTLExpired"//.+Clicking on link received through email, DocuSign recepient token is created for current recipient / signer. Recipient token expires five minutes after it is issued by DocuSign. If a recipient token URL is accessed after token expiration, the user is redirected to SAP CPQ callback URL with event code //"TTLExpired"//.
 \\ \\
 For more details, please refer to the [[https://www.docusign.com/p/APIGuide/Content/Embedding%20Group/Pre-DocuSign%20Operations.htm |DocuSign Time Out]] page. For more details, please refer to the [[https://www.docusign.com/p/APIGuide/Content/Embedding%20Group/Pre-DocuSign%20Operations.htm |DocuSign Time Out]] page.
Line 47: Line 47:
  
  
-====== The CPQ side  ======+====== The SAP CPQ side  ======
 \\ \\
 Go to **Setup** > **Providers** > **Providers**. A page containing available providers appears.\\ Go to **Setup** > **Providers** > **Providers**. A page containing available providers appears.\\
Line 55: Line 55:
 {{:usersideinformation:docusign_parameters.png?500}}\\ {{:usersideinformation:docusign_parameters.png?500}}\\
 \\ \\
-<note>Integration parameters - email, password and login URL must be provided by DocuSign support. Besides these three parameters, you also need the Integrator key to be set for your tenant. This is preformed by CPQ support. When requesting the integrator key let the support know whether your tenant is on sandbox or production environment.+<note>Integration parameters - email, password and login URL must be provided by DocuSign support. Besides these three parameters, you also need the Integrator key to be set for your tenant. This is preformed by SAP CPQ support. When requesting the integrator key let the support know whether your tenant is on sandbox or production environment.
 </note> </note>
 \\ \\
Line 79: Line 79:
 ===== Integration statuses ===== ===== Integration statuses =====
 \\ \\
-Integrating CPQ and DocuSign, three new statuses must be defined by CPQ admin. These statuses will be used in DocuSign process, as starting and ending statuses of DocuSign integration actions. Three statuses can be named as follows, but CPQ admins are free to pick their own status names:+Integrating SAP CPQ and DocuSign, three new statuses must be defined by SAP CPQ admin. These statuses will be used in DocuSign process, as starting and ending statuses of DocuSign integration actions. Three statuses can be named as follows, but SAP CPQ admins are free to pick their own status names:
 \\ \\
   * **DocuSign Accepted**   * **DocuSign Accepted**
Line 86: Line 86:
 ===== Integration actions ===== ===== Integration actions =====
 \\ \\
-DocuSign integration brings four built-in actions that are available in CPQ Setup : +DocuSign integration brings four built-in actions that are available in SAP CPQ Setup : 
  
   * **Generate Document E-Sign **   * **Generate Document E-Sign **
Line 96: Line 96:
 ==== Action "Generate Document E-Sign" ==== ==== Action "Generate Document E-Sign" ====
 \\ \\
-The only action from this group that is visible in quote layout and that can be triggered by CPQ user is **"Generate Document For E-Sign"**. Note that this action should not change the quote status. In order to make this action visible in quote layout, you must enable it by setting a Workflow Permission for it.\\ +The only action from this group that is visible in quote layout and that can be triggered by SAP CPQ user is **"Generate Document For E-Sign"**. Note that this action should not change the quote status. In order to make this action visible in quote layout, you must enable it by setting a Workflow Permission for it.\\ 
 \\ \\
 To do so, go to **Setup** > **Workflow/Approval** > **Workflow Permissions** and assign permission for this action to the particular user type(s). To do so, go to **Setup** > **Workflow/Approval** > **Workflow Permissions** and assign permission for this action to the particular user type(s).
Line 123: Line 123:
 ==== Guest User ==== ==== Guest User ====
 \\ \\
-DocuSign process is performed by a CPQ guest user. Guest user is set in **Setup** > **Quotes** > **Email Customers / Quote Acceptance Settings**.\\+DocuSign process is performed by a SAP CPQ guest user. Guest user is set in **Setup** > **Quotes** > **Email Customers / Quote Acceptance Settings**.\\
 {{:usersideinformation:3.1.png?500}}\\ {{:usersideinformation:3.1.png?500}}\\
 \\ \\
Line 134: Line 134:
 \\ \\
  
-The CPQ integration with DocuSign supports signing by more than one signer. This is called **multisign process**. The following section provides you with the information what should be done on CPQ side to enable the multisign process. +The SAP CPQ integration with DocuSign supports signing by more than one signer. This is called **multisign process**. The following section provides you with the information what should be done on SAP CPQ side to enable the multisign process. 
 \\ \\
 The only setup activity needed to enable the multisign process is to add signature placeholders for all signers to the document generation template(s). Note that if this step is omitted, the multisign process will still be available and functional. That is because DocuSign enables users to put their signature anywhere in the document if no signature placeholder was found. However the general recommendation is to insert placeholders into template documents at the desired place in order to keep the document generation templates well organized and formatted. The only setup activity needed to enable the multisign process is to add signature placeholders for all signers to the document generation template(s). Note that if this step is omitted, the multisign process will still be available and functional. That is because DocuSign enables users to put their signature anywhere in the document if no signature placeholder was found. However the general recommendation is to insert placeholders into template documents at the desired place in order to keep the document generation templates well organized and formatted.
Line 153: Line 153:
 ====== Countersign process ====== ====== Countersign process ======
 \\ \\
-The countersign process is used by companies that want to use CPQ to also put their own signatures on the document. To set up the process, signers must be defined through CPQ administration first. In CPQ terminology these signers are known as “countersigners”.+The countersign process is used by companies that want to use SAP CPQ to also put their own signatures on the document. To set up the process, signers must be defined through SAP CPQ administration first. In SAP CPQ terminology these signers are known as “countersigners”.
 \\ \\
 As an administrator you define a list of potential countersigners and then after generating the document users select which (if any) countersigners are needed for the particular document.  As an administrator you define a list of potential countersigners and then after generating the document users select which (if any) countersigners are needed for the particular document. 
Line 160: Line 160:
 {{:usersideinformation:counter-signer-01.png?700}}\\ {{:usersideinformation:counter-signer-01.png?700}}\\
 \\ \\
-Besides the list of countersigners, the CPQ administrator should modify the Document Generation Template by adding placeholders where countersigners will sign the document. The placeholder format is **\countersign_{r}\** where **{r}** should be the ordinal number of the countersigner. Countersign placeholders, definitions and signing processes are the same as described in the multisign section above. +Besides the list of countersigners, the SAP CPQ administrator should modify the Document Generation Template by adding placeholders where countersigners will sign the document. The placeholder format is **\countersign_{r}\** where **{r}** should be the ordinal number of the countersigner. Countersign placeholders, definitions and signing processes are the same as described in the multisign section above. 
 \\ \\
 The detailed example is provided in the **Examples** section of this page. The detailed example is provided in the **Examples** section of this page.
Line 166: Line 166:
 ====== DocuSign Document Revoke ====== ====== DocuSign Document Revoke ======
 \\ \\
-CPQ supports the Revoke Document feature, for users who want to void a document that has already been sent to signers, avoiding the need for signers to review an obsolete document. +SAP CPQ supports the Revoke Document feature, for users who want to void a document that has already been sent to signers, avoiding the need for signers to review an obsolete document. 
-This action can be triggered from the Quote page since it has been developed as standard CPQ Quote action. Action name is “**Void Document**”.+This action can be triggered from the Quote page since it has been developed as standard SAP CPQ Quote action. Action name is “**Void Document**”.
 \\ \\
 Workflow should be modeled to move the quote back from “Waiting for DocuSigning” to the previous status, after the Void Document action is triggered. Once the signer clicks on the link received through an email, they will be informed that the document has been revoked. (Figure 11) Workflow should be modeled to move the quote back from “Waiting for DocuSigning” to the previous status, after the Void Document action is triggered. Once the signer clicks on the link received through an email, they will be informed that the document has been revoked. (Figure 11)
Line 173: Line 173:
 {{:usersideinformation:figure_2.png?600}} {{:usersideinformation:figure_2.png?600}}
 \\ \\
-When the CPQ user generates a new document, a new link will be sent to the signer.+When the SAP CPQ user generates a new document, a new link will be sent to the signer.
  
 ====== Examples ====== ====== Examples ======
Line 180: Line 180:
 ===== Example of the signing process ===== ===== Example of the signing process =====
 \\ \\
-To test DocuSign process, create new CPQ quote and click on the **Generate Document for E-Sign** action.+To test DocuSign process, create new SAP CPQ quote and click on the **Generate Document for E-Sign** action.
 \\ \\
 {{:usersideinformation:4.png?400}} {{:usersideinformation:4.png?400}}
Line 279: Line 279:
 The form is used to define both the signers and countersigners.\\  The form is used to define both the signers and countersigners.\\ 
 \\ \\
-The multisign feature also allows users to instruct CPQ to request signers to sign in a defined order. If the **Complete in Order** toggle switch is enabled, an email with the DocuSign link is sent to signers successively, not at once. This means that the signer will receive the link only after all signers listed before them sign the document. Alternatively, if the toggle switch is not enabled, the DocuSign link will be sent to all signers at once.\\+The multisign feature also allows users to instruct SAP CPQ to request signers to sign in a defined order. If the **Complete in Order** toggle switch is enabled, an email with the DocuSign link is sent to signers successively, not at once. This means that the signer will receive the link only after all signers listed before them sign the document. Alternatively, if the toggle switch is not enabled, the DocuSign link will be sent to all signers at once.\\
 \\ \\
 It is also possible to mark a signer as required. The image below shows that two signers are defined and that the **Complete in Order** toggle switch is active. One signer is required, whereas the other is optional.\\ It is also possible to mark a signer as required. The image below shows that two signers are defined and that the **Complete in Order** toggle switch is active. One signer is required, whereas the other is optional.\\
Line 326: Line 326:
 {{:usersideinformation:counter-signer-03.png?600}}\\ {{:usersideinformation:counter-signer-03.png?600}}\\
 \\ \\
-The CPQ user has the ability to control if the countersigners should sign the document before signers and if countersigners should sign the document in the defined order.+The SAP CPQ user has the ability to control if the countersigners should sign the document before signers and if countersigners should sign the document in the defined order.
 \\ \\
 {{:usersideinformation:counter-signer-04.png?600}}\\ {{:usersideinformation:counter-signer-04.png?600}}\\
Line 340: Line 340:
 {{:usersideinformation:counter-signer-06.png?600}}\\ {{:usersideinformation:counter-signer-06.png?600}}\\
 \\ \\
-After countersigners complete the signing process, the link is sent to signers. The particular CPQ quote is still in the //Waiting for DocuSign// status since the signing process has not yet been completed on the signers’ side.\\+After countersigners complete the signing process, the link is sent to signers. The particular SAP CPQ quote is still in the //Waiting for DocuSign// status since the signing process has not yet been completed on the signers’ side.\\
 \\ \\
 The process is completed once the required signer signs the document and the optional signer either signs or clicks **Finish**. The quote moves to the //DocuSign Accepted// status.\\ The process is completed once the required signer signs the document and the optional signer either signs or clicks **Finish**. The quote moves to the //DocuSign Accepted// status.\\
  
You are here: SAP Sales Cloud CPQ Online HelpUser Side HelpSAP CPQ and DocuSign Integration