How to Use the Ideas Feature
What you need to know about Docusign Community IdeasThis guide will walk you through the process of sharing your ideas, voting on existing ideas, and...
23980
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
I recently had a DocuSign Connect fail for almost two months, but didn’t get an email notification until it reached “Active - Pending Deactivation” state, at which point it sent an email to say “Administrator Notification: Docusign Connect Configurations Pending Deactivation”. However, it didn’t send anything ahead of time to let me know it was in process of failing. Some digest email to warn me ahead of time would be very helpful.
The final email that is automated, that goes back to the submitter, looks like the below snapshot.why does the email include “Please REVIEW DOCUMENT to Sign” which is from the step SEND FOR SIGNATURE, in the email message area? It should not include the message from the SEND FOR SIGNATURE.
Folders or some sort of grouping are needed to sort workflows. Right now all workflow are just listed so it is hard to find them without scrolling through the entire list.
Please add methods to track unsigned envelops, end user actions and admin actions using custom filters that go beyond the currently provided reports. Especially tracking unsigned envelops with a way to excluded admins, and service accounts is needed.
Please add documentation on how to use system: fields withing a CLM Workflow. example System:Link. There are many others that a running workflow has that come from esig. I have a figured out how to use it but I would like documentation on how to use any System: field say within a CLM workflow email for instance.
I have a text box field on a CLM Doc Gen Form. The field name is what shows on the form that people will see when they fill out the form. It would be nice if you had a separate item that you could put what you wanted the person who is filling out the form to see in addition to the field name. This would be for all fields, not just text boxs.exampleText BoxField Name-DataPlanField Description-How do you plan to use it on the cluster?Help Text-Explain how you plan to use
Please add documentation on how to use data: fields withing a CLM Workflow. example Data:DeclineReason. There are many others that a running workflow has that come from esig. I have a workaround for using Data:DeclineReason but I would like documentation on how to use any Data: field say withing a CLM workflow email for instance.
I have modified the brand resource files for use with esig. I’m having trouble figuring out how to associate a CLM workflow to a brand with a modified resource file in esig. I do not want to use the default brand in esig because what I need for this workflow is different than what we want for the default brand. I did not see anywhere in CLM to associate the brand with a workflow. I need this due to our customers needing customization for their specific workflows.
I had a workflow open that i needed task groups for. I was creating new task groups. They would not show up in the workflow to choose from. I closed the workflow and reopened it. They showed up then.The should show up even if a workflow is open while the groups are being created.
It would be helpful if we could change the color of the steps. It would be easier for me if the step colors matched the lane color so ability to change step color would be helpful.
Please allow capabilities for calc fields for CLM forms like esig has.
Currently we have obligation management in CLM party Management. but when it comes to adding an obligation on agreement and assigned to a person or putting the due date.that’s where we feel, there has to be a notification set up form obligation due date “reminder’ and the obligation, who we assigned that notification send to the particular user or person or counterparty.
It would be very helpful to have multiselect dropdown attributes in CLM as this would allow greater flexibility in selecting multiple options after the document generation phase. This would make it easier to tag metadata on contracts instead of having multiple single select attributes





Docusign Community
Code of ConductAlready have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.