We have an adaptive form that's triggering a pretty simple workflow, emailing the users on the form, collecting their signatures via Sign API, and then sending both parties a 'thank you' message with the completed/signed form, and CC'ing an email address for our agency. The problem is that Adobe Sign does not seem to be notifying our AEM instance that the signing process is complete, nor is the completed Document of Record being returned to AEM. This makes it so our last email workflow step never fires. I can't figure out if this is an AEM or Sign issue. Has anyone run into this?
Here's the gist of our Workflow steps:
1.) The form is submitted.
2.) Both users are sent a 'thank you for your submission' email via the 'Send Email' workflow step.
3.) User1 is sent a request to Sign via Adobe Sign api.
4.) User2 is sent a request to Sign after User1 has signed.
5.) The completed document of record is then sent via email to User1, User2, and CC'd to a third address. (this is the step that never seems to work)
If I look at the Workflow instance that's created upon submission, the process stalls at the 'Sign Document' step. The initiator is listed as 'null', and no end time is specified (since it never completes).
In the AEM config manager, I did check that the Adobe Sign Configuration Service is setup, it looks like it's set to fire every 5 minutes (
*/5 * * * *).
Views
Replies
Total Likes
Is this workflow processing further successfully after a restart?
I recall a similar issue was fixed in the latest branch i.e SP12 wherein the Sign document step in the workflow is stuck intermittently and proceeds further only after a restart, SP12 installers can be found here[0].
Please upgrade and let us know in case the issue persists.
Thank you for the reply! We just tried restarting AEM and unfortunately the workflows stall out at the same point. We actually have a workflow on another AEM instance that's doing the same process successfully, but can't figure out why Sign isn't getting back to AEM with document status on this instance.
Thinking about this more. I wonder if there's a way to check on the Adobe Sign side whether or not it's able to communicate with our instance? Maybe it's some sort of firewall/access issue? The AEM instance can definitely make Sign requests, but i'm not sure how 'Adobe Sign Configuration Service' communicates with the server once the document has been signed.
Just throwing out ideas at this point...