.png)
Validate Submission
- 1 Minute to read
- Contributors
Validate Submission
- 1 Minute to read
- Contributors
Article summary
Did you find this summary helpful?
Thank you for your feedback
Reaffirming transactions can prevent significant errors when dealing with sensitive activities or processes. With this in mind, we came up with the notion of validating records submission in generic and public apps (Embed & Guest) with an OTP. This helps organizations retain security during vital transactions.
This validation now applies only to the process's initial step (first workflow step). There are two aspects that an app creator needs to keep in mind when enabling OTP verification.
NOTE
The OTP validation works for both generic and public apps. However, the configuration varies slightly, as listed below.
- For generic apps, enabling the Validate using the OTP property for the first workflow step-action button will do the job.
- For public apps, along with enabling the Validate using OTP property for the first workflow step-action button. App creators must navigate to App Settings -> Accessibility -> Validate Submission -> OTP Validation.
NOTE
Users will be required to perform OTP validation even before accessing the application, ensuring an added layer of security and user authentication.
Was this article helpful?
