Refresh issue when calling a process

RE: Refresh issue when calling a process

cedric02 — Wed, 21 Jul 2021 07:37:59 GMT

Yes Stewart, before my post, I was already study how to do it with local variable... and I will do it if it does not break too much components ;-)

Thank you

RE: Refresh issue when calling a process

Stewart Burchell — Wed, 21 Jul 2021 07:28:16 GMT

As I said, you could persist context in a local variable. Save the values you want to save and use them again to load your interface components when the interface is refreshed. With the a!refreshVariable() you also get to decide which variables are refreshed when and under what conditions.

RE: Refresh issue when calling a process

cedric02 — Tue, 20 Jul 2021 14:52:54 GMT

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...

RE: Refresh issue when calling a process

Stefan Helzle — Tue, 20 Jul 2021 13:58:19 GMT

OK. Why not embed the record modification interface into the overall interface. Then saving could be done in background and state is stable.

RE: Refresh issue when calling a process

cedric02 — Tue, 20 Jul 2021 13:56:00 GMT

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...

RE: Refresh issue when calling a process

cedric02 — Tue, 20 Jul 2021 13:51:53 GMT

Yes I was considering to save data in DB, but this seems to be too much effort vs what this functionality is offering...

RE: Refresh issue when calling a process

Stefan Helzle — Tue, 20 Jul 2021 13:46:50 GMT

Seems like a huge and complex interface. Are you sure this is a good design decision? Just asking ...

RE: Refresh issue when calling a process

Stewart Burchell — Tue, 20 Jul 2021 13:38:26 GMT

Like any context, if you want to persist it between interactions you need to....persist it! You can save to local! variables (although that would be lost if you close the interface); or you persist in a database and retrieve it again when you refresh the interface

RE: Refresh issue when calling a process

cedric02 — Tue, 20 Jul 2021 13:30:57 GMT

Thank you gayathris but I'm not sure to understand how to do

RE: Refresh issue when calling a process

cedric02 — Tue, 20 Jul 2021 13:29:21 GMT

Thank you
You're right Stewart, the "X" works perfectly, but I would prefer to use a Cancel button, as I need to display a confirmation message.

If running a process from an interface always causes that interface to be refreshed, that means if the user click on the Save button, he will lost the context of components (components and grid already displayed) of the previous interface.
In this case, how to keep that context ?

RE: Refresh issue when calling a process

Stewart Burchell — Tue, 20 Jul 2021 10:19:07 GMT

Running a process from an interface will always cause that interface to be refreshed. If the process model that is referenced by your Record Action does have an actual Start From configured, then you do not need a 'Cancel' button as the process will not be started until you hit a button that has submit: true configured. Such a form has an 'x' top right which allows it to be closed. This will not refresh your original interface.

RE: Refresh issue when calling a process

gayathris111098 — Tue, 20 Jul 2021 10:04:02 GMT

Try like,

When user click on 'Form A', route the user to appropriate sub process based on what button/link was clicked(Form B), and then routed back to the original task(activity chained) (a new instance thereof, technically) once the sub process is done and make sure you have grid selection saved, so that in 'Form A' you can show selection as it is.