Adobe Sign via workflows

how it works to validate adobe sign functionality create 2 workflows + adobe sign form adobe sign process (use process + process properties jsons from adobe sign implementation md file below) and webhook process (use webhook process + process properties jsons from adobe sign implementation md file) create new form (templates forms adobe sign) use adobe sign form json from adobe sign implementation md file) environment setup to setup test user open https //secure adobesign com/public/login https //secure adobesign com/public/login ask illya to provide creds to login open link https //eu1 documents adobe com/account/accountsettingspage#pageid access tokens https //eu1 documents adobe com/account/accountsettingspage#pageid access tokens and generate new integration key add new user to all relevant nodes f e title adobesign name authorization value bearer {integration key} ⚠️ most common registration failure adobe verifies a webhook url with an https get before it ever delivers events if the trigger node is already set to post at that moment, verification failure and the webhook is never created qa verification walkthrough run adobesignprocess trigger a fresh run and let it complete through to generate form url sign the document open the generated url, sign the agreement in the embedded widget, and confirm the signature refresh webhookprocess refresh the process's run table and open the most old created row (trace from the bottom row upward) check the first event open the process overview for that run and inspect the webhook node's request body rows list oldest first, so — "event" "agreement created" trace the status progression step through the following rows in order and confirm event advances until the final row reads "event" "agreement workflow completed" cross check in adobe sign on the adobe sign home page, confirm the agreement now shows as signed ( https //eu1 documents adobe com/account/homejs https //eu1 documents adobe com/account/homejs ) find the record in hyperportal in the workflows dashboard, search for form adobe sign and open the corresponding row confirm the signed copy contractsigned should read yes open signlink to confirm the executed document acceptance criteria pdf generated in hyperportal is uploaded to adobe sign as a transient document and converted into an active agreement the signing link opens a working, mobile responsive pop up with no login required signature is captured and adobe sign returns a completed/signed status the webhook is received and correctly updates the internal document/customer record the fully executed pdf is automatically retrieved and stored in hyperportal against the correct record at least one downstream action (e g status visible to the dealer) fires on completion expired, already signed and declined states are handled gracefully in the ui document with the technical implementation