Selecting another Signatory flow is not working

[jarias-lfx]

Summary

Assigning another person as SIgnatory, the flow doesn't complete after the Signatory completes the signature.

Background

1. Access CLA Corporate Console
2. Start Signature process.
3. When asked "" Are you authorized to sign the CLA for your organization", select No
4. Add the Name and Email for the signatory person
5. The page spins forever
6. The signatory person receives a docusign email
7. The signatory completes the signature
8. Nothing happens

Expected behavior

After the signatory completes the signature the following must happen, but it doesn't after v2.0.150 release

1. The CCLA gets updated in the signatures table. Marked as signed=true, docusing data, signatory date.
2. The signed PDF gets uploaded to S3 bucket.
3. The Initial CLA Manager receives an email with the signatory completion
4. The initial CLA Manager gets the cla-manager role

Screenshots

Adding the Signatory person spins endlessly:

Environment

Please complete the following information:

• Environment:
  • ALL
  • DEV
  • STAGING
  • PROD
• Browser:
  • [x ] Chrome/Brave
  • Firefox
  • Opera
  • Vivaldi
  • LibreWolf
  • SRware Iron
  • Dissenter
  • Slimjet
  • Midori
  • Edge
  • Lynx

[thakurveerendras]

Issue is working fine on dev site but on prod we are getting 500 server error for "RequestCorporateSignatureResult"

{
"data": {
"requestCorporateSignature": {
"code": 500,
"message": null,
"success": false,
"data": null,
"__typename": "RequestCorporateSignatureResult"
}
}
}

• Refer video clip for dev:another Signatory.webm

[sjparkinson]

Worth noting the Docusign is still sent to the recipient. I accidently sent it more than once as a result!

[mlehotskylf]

@nickmango is looking into this.

[jarias-lfx]

{
    "data": {
        "requestCorporateSignature": {
            "code": 500,
            "message": null,
            "success": false,
            "data": null,
            "__typename": "RequestCorporateSignatureResult"
        }
    }
}

[nickmango]

@thakurveerendras This has been resolved. Kindly verfiy

[thakurveerendras]

@nickmango , The Issue is not reproducible as reported on the dev site, But after completing the signup easycla page is not loaded properly

• Refer to the video clip:

4247.mp4

[nickmango]

@thakurveerendras
The CCLA gets updated in the signatures table. Marked as signed=true, docusing data, signatory date.
The signed PDF gets uploaded to S3 bucket.
The Initial CLA Manager receives an email with the signatory completion
The initial CLA Manager gets the cla-manager role

Werent these expectations met ?

[thakurveerendras]

Tested with the documents received at email but after signing the document, CCLAs remain not signed
Refer to the video clip:

4247_flow.mp4

[mlehotskylf]

@nickmango is working on the fix.

[mlehotskylf]

"500 response" issue is resolved, now @nickmango is working on DocuSign callback issue as part of this ticket.

[nickmango]

@thakurveerendras kindly verify

[thakurveerendras]

Tested this issue on the dev site at the parent & child project level and found that it is fixed as expected. So updating the issue status

4247.2.mp4

[thakurveerendras]

Tested on the prod site and found that it is deployed properly. So moving issue status QA-Done
Refer to the video clip
4247_prod.webm