Hi,
I would have a question about a refresh aspect.
I have an interface (let's call it "Form A") displaying many sub interfaces depending on many conditions.
In one of theses sub-interfaces, there is a RecordType grid and for each line I've set a RecordAction (called "Edit row") that triggers a process.
(The user has to make few clicks on different components to see that grid)
When the user clicks on this row RecordAction, it triggers the process which displays a start form Interface (let's call it "Form B").
This "Form B" interface has 2 buttons "Cancel" and "Save" (I've set submit = true for each one). When the user clicks on the Cancel button, the process simply goes to the end node (XOR step decision is used).
If the user clicks on Save, the process store data in DB and end the node.
My question is :
When I click on the cancel button of "Form B", how may I do, to having NO refresh of the "Form A" ?
I need the user to stay on the same grid, same sub-interface of "Form A".
It seems that the Process triggers a refresh of the last Interface displayed.
Discussion posts and replies are publicly visible
Seems like a huge and complex interface. Are you sure this is a good design decision? Just asking ...
Yes Stefan, this a very huge and complex interface... we may probably leave this as it, as the customer will not ask/pay us to make a rework on the existing interfaces...
OK. Why not embed the record modification interface into the overall interface. Then saving could be done in background and state is stable.
Yes, it is already the case, but a little modification require a lot of user clicks (put the interface in edit mode, navigate to the good menu, the correct sub-interface, the grid...)So my question in that post, was to try to have a more direct access for some functionalities...