Skip to main content
C
cedricj425261
July 20, 2021
Question

Refresh issue when calling a process

  • July 20, 2021
  • 12 replies
  • 0 views

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.

12 replies

gayathris111098
gayathris111098
July 20, 2021

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.

C
cedricj425261Author
July 20, 2021

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

stewart.burchell
stewart.burchell
July 20, 2021

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.

    C
    cedricj425261Author
    July 20, 2021

    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 ?

    stewart.burchell
    stewart.burchell
    July 20, 2021

    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

    stefanhelzle0001
    stefanhelzle0001
    Brainy
    July 20, 2021

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

    C
    cedricj425261Author
    July 20, 2021

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

    stefanhelzle0001
    stefanhelzle0001
    Brainy
    July 20, 2021

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

    Terms & ConditionsAccessibility statement