Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
We are looking to achieve an in-app eSignature function within our Appian workflow process. Is this available?
DocuSign integrations are available in the AppMarket, but all seem to route the user outside of Appian to the DocuSign platform to capture the approver's signature.
Adobe Sign Utility & Sign PDF Document both seem to be more in line with our request, but I would like to confirm if either are feasible.
Screenshot below shows the PDF embedded in the review pane where we would like to capture the eSignature directly within Appian.
Discussion posts and replies are publicly visible
I currently work with a system using the Adobe Sign integration. Overall it works well. The main issue we keep running into (which is more of a User Training issue, and more of an issue with Adobe Sign itself than with Appian), is that when the user gets their Appian task containing a portal to fill and/or sign their Adobe Sign document, the Adobe Sign integration contains its own "Complete" or "Submit" button, and the users will merely do that and then close the Appian task without hitting any Submit button. This, of course, prevents the Appian process from proceeding which is critical.
This still happens (if somewhat less) even after we've added large, bold, obvious instruction text on the form header explaining that they absolutely must press the button OUTSIDE the integration pane labelled "send to reviewer" (etc). AFAIK there would still be the same type of issue regardless of the type of integration used. For now we're just doubling down on the "user training" angle to solve this issue.
Hi Mike, this is super helpful. If I understand the pain point correctly, it's due to the approver having to complete/submit their signature and also click the submit button for the Appian workflow approval. If that's the case, I personally would prefer that over the user being required to open a separate link to DocuSign to enter their signature while still completing the Appian approval.
To confirm, you have it configured so the Adobe Sign is embedded within Appian, correct? For example, in the screenshot I included in my post, our preference is for the user to enter their signature directly in that PDF pane.
Do you have any screenshots or reference documents you can share?
I don't have any specific insight into the particulars of using DocuSign URLs - i haven't seen an error message similar to the one you describe when designing or testing Adobe Sign documents though.
Hi Mike, our development team is running into some issues with the Adobe Sign integration where the authentication token needs to be manually refreshed every hour. Did you experience this issue as well? If so, any insight on how this was resolved?
We've actually never had an issue with the auth token either way. Are you not using a Connected System into echosign with an API Key? AFAIK we've never needed to change ours since it's been set up.
Are you using "OAuth 2.0: Authorization Code Grant"? That is what we've configured, which has resulted in the recurring issues with the authorization token refresh.
No, our connected system uses API Key.
Hi Mike, thanks again for the helpful feedback on this. Last question (I hope), when the workflow is started, are your users preparing the workflow assignments (e.g.: responsible signers) directly in Appian or a separate window in Adobe Sign?
Generally speaking that's all set up for them in Appian - we try to limit their need to directly interact with Adobe Sign as much as possible, to keep them within the Appian ecosystem mainly.
That's our objective as well. Assuming you're using SSO to authenticate with Adobe?
Do you mean for our personal (admin) login purposes or for authenticating through Appian? If the latter, as I mentioned above, we're using API Key.
Hi Mike,
Thanks for you response.
We have achieved the required connectivity using API KEY. We added an additional functionality “Authoring” in our application. When The user upload the document he get the PDF document in AUTHORING state where he can drag and drop the SIGNATURE BLOCK inside PDF and send the document for signature.
As per the attached screenshot, When we upload the PDF document for e-signature the form should automatically be logged into Adobe.
As we are loading Adobe using the “WEB CONTENT” component the login happens only when we already authenticated Adobe in a different browser.
We are trying to authenticate the user within Appian without Adobe login into another browser.
Our end users in Appian are not users within the Adobe system at all (save for a few admin accounts that create / edit / manage the templates). We handle it all by the "signer email" (and similar) fields that get passed in at document creation.