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

As a Sender, I want to be able to create a new eSignature envelope 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

      Figma Mockups

      Acceptance Criteria:

      1. Senders should be able to create a new envelope to send to a recipient(s) when viewing the list of requests.
      2. When Senders choose to create a new envelope, 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. Document
            1. Required field, or else display message:  "This field is required."
          3. Recipient Full Name
            1. Required field, or else display message:  "This field is required."
          4. 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.”
          5. Email Subject
            1. Required field, or else display message:  “This field is required.”
            2. 100 characters max
          6. Email Message
            1. Optional field
            2. 10,000 characters max
        3. When filling out the envelope info form, Senders should be able to select one or more documents to attach.
          1. Call to Action:  "Select Document"
          2. When Senders click on “Select Document”, they will be prompted to select one or more existing files from Documents & Media.
            1. Max to select - 10
            2. File types accepted:
          3. Senders should also be able to upload new files to attach.
            1. Max to select - 10
          4. When documents have been selected, Senders should return to the New eSignature Envelope form.
        4. When filling out the envelope info form, Senders should see an option to add additional recipients (Full Name & Email Address).
        5. 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.
        6. Senders should be able to cancel out of completing the form.
        7. Senders should be able to successfully submit the form and send the envelope to the recipient(s)
          1. Success message:  “Your envelope was successfully sent!”
          2. Status = “Sent”
        8. 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."
        9. Once the envelope has been successfully sent, Senders should be navigated to the eSignature main page to view requests.

      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:
              luiz.jardim Luiz Jardim
              Engineering Assignee:
              SE Support
              Recent user:
              Rafaela Nascimento
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.4.2 CE GA3 DXP 7,4
                  Master