Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Recipients with duplicate emails and no signing order

Explorer ,
Dec 06, 2024 Dec 06, 2024

I have a scenario where the a pdf document is generated dynamically and sending it for signature. I am placing text tags in the pdf document as below

PersonId Name    Signature                                          Date

P1              ABC    {{Sig1_es_:signer1:signature}}         {{Dte1_es_:signer1:date}}

P2            XYZ    {{Sig2_es_:signer2:signature}}         {{Dte2_es_:signer2:date}}

Before sending it for signature, I save the recipient information to a table. In this case, P1 and P2 have the same email address, and both have a signing order of 1. P1 is the child, and P2 is the mother. How can I update the database table when a user signs or rejects?

The webhook response includes the following details:

{
"participantUserId": "CBJCHBCAABAApOhpy5n-9OG4zIUGhW-2l9dAtXFGnv0-",
"participantUserEmail": "mailid@gmail.com"
}

These details pertain to the user who signed or rejected.

Currently, after creating an agreement, I call this API to get the member list:
https://secure.in1.adobesign.com/api/rest/v6/agreements/CBJCHBCAABAAAVfVGu9kybbMbt_0tUUNMiFRiDBt4Fyi...

I update the database table to save the userId from the API response according to the order in which I sent member information during the agreement creation.

When I receive the webhook response, I use the participantUserId to update the status in the database.

However, if Adobe changes the order in which it returns the members, how can I handle this scenario?

Is it possible to pass a unique identifier for each member while creating an agreement and then retrieve that identifier in the webhook response to uniquely identify the user who signed or rejected?

TOPICS
Manage documents , SDK , Send documents
172
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 07, 2024 Dec 07, 2024
LATEST

This is the json request for creating the agreement: 

{
"participantSetsInfo": [
{
"role": "SIGNER",
"memberInfos": [
{
"id": "test1",
"name": "abc",
"email": "sreejeshinapp@gmail.com"
}
],
"order": 1
},
{
"role": "SIGNER",
"memberInfos": [
{
"id": "test2",
"name": "xyz",
"email": "sreejeshinapp@gmail.com"
}
],
"order": 1
}
],
"name": "Test Document",
"signatureType": "ESIGN",
"fileInfos": [
{
"transientDocumentId": "CBSCTBABDUAAABACAABAAhwIjOwQuPDCvbgKrC_FmPrQbIG5fzGhKyoovy-lve0vx9kAZDiuMfUT_lLJZe9ye3oLX5YF6DuF5d8Bjjr_tPy_KvjJGoalqpkK5NzF_RYW5vIH7SZAEpz2nntgOPYSknNP7d7j_aluSMSmgHj3AjSxRwawUDiazH178hOdhffg7H0tPAvJAHGZgm0ZxXcpMBrEmUat03LR5_6UJf-CNA5NxQKrc53nDGLsULFzjabXJFkQQ3PBJfo0aurK917wI3ZWdu3azDjPZ5vIj5QlR-4xLgaL3YrT1c5X5gL3Pf2x-84S8ffg58u4J1tBOsyw0lA26gA2jmEhmuYNtiC2yicrXpQaLB5GyzqCaDDLfMLD9yw3RfQTniAI8NhbEAZxB"
}
],
"state": "IN_PROCESS",
"message": "Please review and sign"
}

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines