实际签署流程与模板配置不符的技术问题咨询

It sounds like your sent document isn’t following the signing workflow you set up in your template—let’s work through the most likely causes and fixes:

1. Double-check the template’s built-in signing order #

First, go back to your template’s configuration and confirm the signing sequence for your roles. If the template itself is set to parallel signing (both participants get the request at the same time) or has the roles ordered incorrectly, that’s going to override any assumptions you have about the flow.

2. Verify the templateRoles order in your API request #

Many e-sign platforms prioritize the order of roles listed in your templateRoles array over the template’s saved order, especially if you don’t explicitly lock in the template’s workflow. In your current request, you’ve listed Paticipant B first, then Paticipant A. If you expect A to sign first, reorder the array like this:

"templateRoles": [
  { 
    "email": "paticipantA@example.com", 
    "name": "Paticipant A", 
    "roleName": "Paticipant A" 
  },
  { 
    "roleName": "Paticipant B", 
    "name": "Paticipant B", 
    "email": "paticipantB@example.com" 
  }
]

Test this adjusted request to see if the flow aligns with your expectations.

3. Fix role name typos (critical!) #

I spotted a spelling error in your role names: Paticipant instead of Participant. If your template uses the correctly spelled Participant A/Participant B, the API won’t match the roles properly. This mismatch can cause the platform to default to a random or incorrect signing order. Correct the spelling in your roleName, name fields to match the template exactly (some platforms are case-sensitive too!).

4. Check for unintended workflow overrides #

Look for any hidden parameters in your request that might be overriding the template’s settings. For example, some platforms let you add a signingOrder flag or parallel signing toggle in the API call. Even if you didn’t include it explicitly, double-check that your API client isn’t injecting default parameters that alter the flow.

5. Test with a minimal request #

Strip down your request to only the essential fields to rule out interference from optional parameters. Try sending this simplified version:

{
  "emailSubject": "Test company - Custom Rates Letter",
  "status": "sent",
  "templateId": "xxxxxxx-yyyy-zzzz-aaaaa-bbbbbbbbb",
  "templateRoles": [
    { 
      "email": "participantA@example.com", 
      "name": "Participant A", 
      "roleName": "Participant A" 
    },
    { 
      "roleName": "Participant B", 
      "name": "Participant B", 
      "email": "participantB@example.com" 
    }
  ]
}

If this works, you’ll know the issue was tied to an optional parameter or formatting quirk in your original request.

If none of these steps resolve the problem, share more details about your template’s exact workflow configuration (e.g., sequential vs parallel signing, role order settings) and any API response messages you’re getting—we can dig deeper from there.

内容的提问来源于stack exchange，提问作者hua tang