MaestroPreviously known as Transact Maestro. | Form Builder | v5.1 & Higher This feature is related to v5.1 and higher.
In this topic, we're going to create a save challenge from scratch. This will provide insight into how to create your own save challenges and how to customize save challenges in existing templates.
To setup this feature:
In earlier versions of Maestro, the Save Challenge component was named TRN Save Challenge.
You should end up with a View pane that looks like this:
Based on these changes, the save challenge feature is now functional. If you render the form and click the Save and Close button, you'll see the reference code assigned to the transaction. Then, if you click the Open Saved Form button and enter the reference code, the saved form will open.
If you enter an incorrect reference code, an error will be returned:
If you receive this error after entering a correct reference code, it's probably because you're using an earlier version of Maestro. In this case, you'll need to add a security question for the save challenge feature to work. Fortunately, adding a security question is considered a best practice.
Security questions ensure an extra layer of protection for users who save their forms. Rather than simply entering a reference code, they're required to enter an additional piece of information to verify their identity.
To add a security question to the Save Confirm dialog:
Then, to allow users to provide their security answer via the Save Challenge dialog:
It's important to note that only the first text field — the text field in the Save Confirm component — should be mapped using the Form Data Config Mapping dropdown. If you map the second text field, the original mapping will be lost, as only one field can be mapped to the Save Challenge option at any one time.
Based on these changes, users will now be required to answer a security question when saving and opening a form.
The reason the Save and Close and Open Saved Form buttons automatically open the relevant dialogs is because of the IDs associated with the components. The Save Challenge component, for instance, has an ID of "savechallenge", and the Open Saved Form button has a rule that opens a dialog with the ID of "savechallenge":
If a dialog isn't opening for whatever reason, it's worth verifying that the IDs are setup correctly. The easiest way to do this is to open the Google Chrome DevTools before attempting to open the dialog. If there's an error with the ID, it will appear via the Console: