...
As the JSON Tool plugin is not a form validator nor form store binder type of plugin, we will need to use the workaround shared earlier, which is writing the bean shell code from scratch or calling the JSON Tool plugin programmatically.
Why Form Validator?
Form Validator Plugin expects a true/false to be returned. We may try to avoid the need of designing a process flow and achieve the same JSON result checking by making the JSON call through the validator plugin. The problem that would arise from this appraoch are:-
- Same form content may get submitted repetitively as other form fields' validators may kick in too (i.e. mandatory field checking).
- If the external API system becomes unresponsive, the Joget app will stop working.
- Increased wait time. Response time includes JSON Tool's turnaround time.
Why Form Store Binder?
To avoid calling the API repetitively, let's move down to the next layer, store binder.
...
- If the external API system becomes unresponsive, the Joget app will stop working.
- Error message is not friendly.
- Increased wait time. Response time includes JSON Tool's turnaround time.
How can we ensure that form submission captured, without the need for potential customer to wait for the JSON call to be completed and to continue to receive form submissions when the external API is not reachable at the point of form submisison?