Hi,
We have implemented the Adobe Sign Document Component under the workflow model and connected that workflow to the required adaptive form and tested that form on TST(version 6.5.8.0) instance and it worked as expected. So, we got that sign document mail and after signing the document we got the further next workitems.
Now the thing is, when we implemented the same thing on PROD instance we are facing an issue.
The issue is even after signing the documents, we are not receiving the further workitems.
Previously it was working. But suddenly it has stopped. We tried clearing the previous expired items. But it didn't work.
We couldn't get to know whether its an issue from AEM end or Adobe support end? Or it is any kind of Config issue?
So, what may be the solutions that we can try?
Thanks!
Views
Replies
Total Likes
Hi @kapil_rajoria , Any insights on this...
Hi @Shreyas_tm did you check the logs?
Hi @Shreyas_tm ,
How did you create the adobe sign configuration on the prod instance. Please try recreating the adobe sign cloud configuration to check if the issue gets resolved. And as @kapil_rajoria suggested, please check and share what are the error logs you are getting when a workflow is started.
We are not creating adobe sign on prod instance. We are just publishing it from PR node and selecting it as cloud config and checking for it. We are not receiving any logs as well. Still looking into it.
Thanks!
Can you please try creating the adobe sign cloud config on prod instance directly? Any reason why are you not creating the config on prod instance? If you are publishing it from some other instance they issue might be with the HMAC keys, and it should throw a crypto exception. You can follow this page to replicate the HMAC keys https://experienceleague.adobe.com/en/docs/experience-manager-65/content/security/security-checklist...
Is this error just on the author instance or the publish instance ? Can you please share the jcr:content of your adobe sign cloud config. Also, SP8 is very old can you try upgrading to the latest SP ?
@Shreyas_tm , did you try @navneeta's suggestion? is the issue resolved?
The issue is not yet resolved. Still we are checking on it.
Thanks!
@Shreyas_tm Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies