We must not stop at this first step and, as with modern GPS, ask ourselves how another way of seeing things could improve the efficiency of a system.
Introducing adaptive capabilities into applications gives them superpowers, making them more scalable, more resilient.
The very concept is in line with an era when a workflow was a robust paper file made up of documents and supporting documents. This file had to be validated by a group of actors (operational, technical, administrative, legal, financial, etc.). By force of circumstances, the workflow was procedural, sequential with a file that passed from office to office to be validated (or refused) with the appropriate stamp and the signature of the manager.
Most digital workflows are built on this paradigm. The advantages are, at a pinch, the readability of the process, but never its efficiency!
One workflow will ask the user for a ton of information to avoid back-and-forths while another will uk telegram data check the supporting documents at each step. Which can lead to interrupted workflows after weeks of instruction!
Worse, some workflows will be instructed up to a stage where they will be automatically rejected. What a waste of time!
It is possible to rethink workflow processes by posing the problem differently. We should not describe a way to validate but we should focus on writing the rules to achieve the validation objective. In this case, we break the sequential approach, and we let the engine (GPS!) take the path that will optimize the instruction time according to the rules provided. The files will be validated or rejected more quickly , for efficiency at the service of both applicants and instructors.