Skip to main content

    637 Ideas

    Scott.Nieman
    Troubleshooter
    Scott.NiemanTroubleshooter

    Enhancement Request - allow a subset of envelope documents to be combined into one PDF by their documentId and sequence to add, while being able to download the remaining as individual documentsParked

    GET {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}/documents/combined is not working for us and we need enhancements.In our contracting process we want to assemble and reuse templates as much as possible.The boilerplate language of the agreement is a template with tabs.Our Exhibit A is a listing of arable fields that a farmer operates and may be eligible for a carbon program.  We generate and add this document via the APIExhibits B, C and D are reuseable templates.We may optionally add sensitive documents such as the IRS W-9 template, and our ACH enrollment forms.  These sensitive documents need to be captured and place in a secure Azure container, with only authorized individuals allowed to see (PII).  The business does NOT want to send multiple envelopes.  These are farmers, and sometimes the only computer they have is in the tractor cab or their cellphone.We need to add query parameters to the combine resource to specify [{“documentId”: “1”, “sequenceId”:”1”},{“documentId”: “2”, “sequenceId”:”2”},{“documentId”: “3”, “sequenceId”:”3”}, “documentId”: “4”, “sequenceId”:”4”}, {“documentId”: “5”, “sequenceId”:”5”}], and retrieve the remaining directly.The existing combine feature is too basic.  Support has suggested use this Idea platform.

    LynnCNew Voice

    P11 Module Enabled - Product Limitation Compliance GapIdea Submitted

    As new users of Docusign operating in a regulated GxP environment, and during our review of monthly software release notes and system behavior, we identified a significant compliance gap related to the use of the Docusign Mobile Application when the 21 CFR Part 11 (P11) module is enabled.Currently, there is no configuration option or administrative control that allows an organization to prevent users from sending and/or signing envelopes using the Docusign mobile application. This limitation is not aligned with the compliance expectations associated with the P11 module and creates a conflict between advertised configuration controls and actual system behavior.Specifically, not all Part 11, related checks and controls appear to be enforced or configurable within the mobile application to the same extent as the web interface. As a result, mobile usage introduces additional compliance risks related to authentication, procedural controls, and intended use, which must be addressed through compensating measures such as expanded validation scope, additional risk assessments, and enhanced user training. These activities would not be required if appropriate system-level restrictions were available.From a regulated user perspective, there should be configurable options that allow organizations to: Fully restrict the use of the Docusign mobile application for GxP-regulated activities, or Limit mobile usage to specific actions (e.g., signing only, sending only), consistent with the organization’s intended use and validation strategy. At present, none of these controls are available, leaving organizations unable to technically enforce their compliance decisions.This limitation also raises concerns regarding the purpose and scope of existing compliance artifacts. For example: What is the intended role of the monthly Validator Report if mobile application functionality is not included or verified as part of Part 11 compliance? What is the practical value of the configuration setting “Allow recipients to sign on a mobile device” if recipients are able to sign via the mobile application regardless of this setting? These inconsistencies make it difficult for regulated customers to rely on system configuration alone to enforce Part 11 compliant behavior and may lead to unintended noncompliant use.Enhancement Request:We formally request that Docusign consider enhancements to: Provide administrative controls to disable or restrict Docusign mobile application usage when the Part 11 module is enabled Clearly align mobile application behavior with Part 11 configuration settings and validation documentation Expand Part 11 validation coverage and documentation to explicitly include mobile application functionality, or clearly state limitations where applicable Such enhancements would significantly improve Docusign’s usability and credibility in regulated environments and reduce the need for procedural workarounds that increase operational burden and compliance risk.