The BE added a new feature where you can use the hidden field to create a confirmation message using token which will be sent by the Post Request Response to the FE. It adds the custom message in the notes field of response data. The reason it couldn't use the existing confirmation message field because that field doesn't know the token value which gets generated after the submission and the exisiting confirmation field sends out the field before form submission.
Returned the response data in webform mixin and used it to show the custom confirmation message with token value that returned from the webform post response by the BE.
Screenshots
How Has This Been Tested?
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Improvement/refactoring (non-breaking change that doesn't add any features but makes things better)
Checklist
[ ] I've added relevant changes to the documentation.
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] My change requires a template update for create-ripple-app.
[ ] I have added template update script for next release.
Motivation and Context
The BE added a new feature where you can use the hidden field to create a confirmation message using token which will be sent by the Post Request Response to the FE. It adds the custom message in the notes field of response data. The reason it couldn't use the existing confirmation message field because that field doesn't know the token value which gets generated after the submission and the exisiting confirmation field sends out the field before form submission.
JIRA issue: https://digital-vic.atlassian.net/browse/SDPAP-6961
Changed
Screenshots
How Has This Been Tested?
Types of changes
Checklist