Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-131206

As a Sender, I want to be able to locate one file in Liferay and send it to one or more Recipients and collect their digital signatures so I can complete my transaction

    Details

      Description

      Context:

      Based on feedback from sales engineers, sales and GS client engagements, there is a business need to integrate with digital signature tools.  Research concluded that DocuSign was the the most commonly used digital signature provider. 

      Solutions COE aims at providing a way for customers to easily integrate with DocuSign using Liferay.  What started off as a POC from GS has turned into a greater need to add this to a Solutions Library, where GS can utilize the integration with clients and Liferay Product Management can consider adding this implementation to their product roadmap.  

      Design deliverable

      Mockups

      Acceptance Criteria:

      1. Senders should see an option to collect a digital signature for each supported file type in Documents & Media.
        1. Option title:  "Collect eSignature"
        2. File types supported
      1. When Senders choose to collect a digital signature for one or multiple files, they should be presented with a envelope form to input the following information:
         
        1. Form Title:  New eSignature Envelope
        2. Form Fields:
          1. Envelope Name
            1. Required field, or else display message:  "This field is required."
            2. 100 characters max
          2. Recipient Full Name
            1. Required field, or else display message:  "This field is required."
          3. Recipient Email
            1. Required field, or else display message:  "This field is required."
            2. Email addresses should have a “@” and “.” symbols, or else display message:  “Please enter a valid email address.”
          4. Email Subject 
            1. Required field, or else display message:  "This field is required."
            2. 100 characters max
          5. Email Message
            1. Optional field
            2. 10,000 characters max
      2. Senders should be able to see which documents were selected from Docs & Media in the eSignature Envelope form (similar to how Gmail treats email attachments).
      3. When filling out the envelope info form, Senders should see an option to add additional recipients (Full Name & Email Address).
        1. A maximum of 10 recipients can be added.
      4. When filling out the envelope info form, Senders should see an option to delete any additional recipients (Full Name & Email Address).  
        1. At least one recipient is required and all else can be deleted.
      5. Senders should be able to cancel out of completing the form.
      6. Senders should be able to successfully submit the form to send the envelope to the recipient(s).  
        1. Success Message:  "Your envelope was successfully sent!"
        2. Status = “Sent”
      7. Senders should be able to see an error message if the submission was unsuccessful
        1. Error message:  “There was an error in processing your request. Please try again later.”

      The following set of acceptance criteria will be based on DocuSign’s interaction with the Recipient(s) and the Sender:

      1. When the provider has successfully processed the envelope request for collecting a digital signature, the recipient should receive an email from the provider to initiate the collection process. 
      2. If more than one recipient was added by the Sender to the envelope, all recipients should receive an email from the provider.
      3. The recipient’s email should include a link to the provider’s site to digitally sign the PDF document.
      4. The recipient should be able to click on that link and be redirected to the provider’s site to initiate the digital signature collection.  
      5. The recipient should be able to decline to sign.
        1. Status = “Void” 
        2. If Recipient voids in the provider, Recipient should get a void confirmation email from the provider
        3. If Recipient voids in the provider, Sender should get a void confirmation email from the provider
      6. Within the DocuSign UI, Recipients should be able to manually drag and drop signature fields to add their digital signature to the document.
        1. Status = “Signed”
        2. When the Recipient completes signing, they should be able to optionally sign up for a DocuSign Account.
        3. The Recipient will be navigated to the final DocuSign landing page.
      7. When all recipients have completed digitally signing the document, Recipient(s) and the Sender should receive a confirmation email from the provider that the process has been completed.
        1. Status = “Complete”
      8. Within the confirmation email from the provider, recipients should be able to click to view the signed document in the provider and download or print it for their records.

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Code with peer review completed;
      • Validated by QA, Product Designer and/or PM;
      • No critical bug related to Story scope (ex.: similar of FP4, FP5);
      • Make sure that all system documentation were updated (if necessary)
      • Make sure that it has the extensions points needed to allow GS and customers to customize the feature (If applicable)

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              monica.posin Monica Posin
              Reporter:
              monica.posin Monica Posin
              Engineering Assignee:
              SE Support
              Recent user:
              Rafaela Nascimento
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.4.2 CE GA3 DXP 7,4
                  Master