Copy link to clipboard
Copied
we got Adobe Sign developer account to connect to our SAP Ariba Test system.
I created API / Access token and used it to configure Adobe Sign standard out of box integration solution with SAP Ariba.
Created new contract workspace and created signature task for a document and triggered that task.
Ariba system asks to select which Signature solution and we select Adobe Sign, system shows its processing, navigates to Administration tab of Ariba and back to contract workspace and shows task is in Signing status.
But no document is sent out for signature.
What are we missing ?
Once adobe support team enabled the integration path for SAP Ariba for the account we were using for integration, issue from thier side was resolved.
But when in SAP Ariba we trigger the task for signature, it was not taking to signature page to add tags - this was resolved, as SAP Ariba was opening the Adobe Sign page via SSO as pop-up. And organization wide we have pop-up been blocked. Once we allowed pop-up on the browser, issue is fully resolved.
Copy link to clipboard
Copied
Your Dev account may need some addtiional config for the Ariba integration, which need to be done by Sign support. (click question mark in the upper right corner when logged in your sign account)
Are you using the SOAP or REST version of the Ariba integration?
Copy link to clipboard
Copied
Yes, I raised SR for AdobeSign and they enabled Ariba integration for our AdobeSign account whose API key will be used for integration.
But i am still facing same issue. When i trigger Signature task from SAP Ariba for contracts, it stays in Ariba system and just marks tasks as signing without actually sending the document for signature.
In Ariba configuration i do not see any place to select REST or SOAP. This is standard integration given by SAP Ariba where we just insert user id and API key.
Copy link to clipboard
Copied
Once adobe support team enabled the integration path for SAP Ariba for the account we were using for integration, issue from thier side was resolved.
But when in SAP Ariba we trigger the task for signature, it was not taking to signature page to add tags - this was resolved, as SAP Ariba was opening the Adobe Sign page via SSO as pop-up. And organization wide we have pop-up been blocked. Once we allowed pop-up on the browser, issue is fully resolved.