Support for AssureSign Child Accounts in Salesforce DocGen Integration

In our organization, we use AssureSign child accounts to represent our different business entities under a single parent account. Each child account is used by a distinct Salesforce org.

Current limitation:
The Nintex DocGen integration in Salesforce currently only supports a single AssureSign default account, and does not support child (sub-)accounts. When attempting to use a child account in the "Delivery Option" configuration for eSignature, the following error occurs:

System.NullPointerException: Attempt to de-reference a null object (Loop)

This limitation also causes issues in scenarios where:

• A user attempts to initiate signing from the default (parent) account, but they are only a member of a child account. The signing process may complete, but a similar error is returned afterward due to account mismatch.

Suggested improvement:

• Extend the Nintex DocGen + AssureSign integration to support multiple AssureSign accounts, including child accounts.

• Allow DocGen Packages to target a specific AssureSign child account for signature delivery.

• Handle account scoping and permissions gracefully to avoid null pointer exceptions or post-signature failures.

Why this matters:

• Many organizations use AssureSign’s child account structure to separate entities, brands, or legal units.

• Being restricted to a single account undermines this architecture and forces workarounds that compromise user access, visibility, and compliance.

• Supporting child accounts would unlock more flexible, enterprise-grade use of eSignature across Salesforce orgs.

This enhancement would significantly improve scalability, maintainability, and user experience for businesses using multi-account AssureSign structures within Nintex DocGen.