The use case gets triggered when customer service agent fills and submits refinance form.
The Sign Multiple Forms workflow gets triggers on this form submission and the customer gets an e-mail notification with a link to start the form filling and signing process.
The customer is presented to fill and sign the first form in the package. On successful signing of the form, the customer can navigate to the next form in the package. Once all the forms are filled and signed the customer is presented with the “AllDone” form.
The E-mail notification are sent by Send Email component in the Sign Multiple Form workflow. If any of the steps in this workflow fail, the e-mail notification will be sent. Make sure the custom process step in the workflow is creating rows in your MySQL database. If the rows are being created then check your Day CQ Mail Service configuration settings
The links in the e-mail notifications are generated dynamically. If your AEM server is not running on localhost:4502, please provide the correct server name and port in the arguments of the Store Forms To Sign step of the Sign Multiple Forms workflow
This can happen if the form was not populated correctly by fetching the data from the data source. Check the stdout logs of your server. The fetchformdata.jsp writes out some useful messages to the stdout.
On successful signing of a form in the package, the Update Signature Status workflow is triggered. The first step in the workflow updates the signature status of the form in the database. Please check if the status for the form is updated from 0 to 1.
When there are no more forms to sign in the package, the AllDone form is presented to the user.If you are not seeing the AllDone form, please check the URL used in line 33 of the GetNextFormToSign.js file which is part of the getnextform client lib.