There is a process of several consecutive steps, where the user selects on the forms that he needs.
There is a process of several consecutive steps, where the user selects on the forms that he needs. It is necessary to implement the “back” button, by clicking on which the user would have to return to the previous form with the data that he was introduced to her.
it can be implemented without using the branch after each task to verify the need to return?
Actually it can be implemented without any transition that allow process flow to get back to previous steps.
You might want to consider the option of doing the pageflow within a single task by hiding part of the form based on user action. Note with such solution saving data can happen only when you submit the task.
Here you build one form for all pages and have one submit button to submit all, note that saving data between forms will not happen (unless you reprogram the example).
However if you MUST have 3 steps to do your task as in your diagram then you are stuck with a transition and the necessary loop back. This is normal.
Bonitasoft empowers development teams with Bonita, the open-source and extensible platform to solve the most demanding process automation use cases. The Bonita platform accelerates delivery of complex applications with clear separation between capabilities for visual programming and for coding. Bonita integrates with existing solutions, orchestrates heterogeneous systems, and provides deep visibility into processes across the organization.
