Refresh issue when calling a process

Certified Senior Developer

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

Parents
  • 0
    Certified Lead Developer

    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.

Reply
  • 0
    Certified Lead Developer

    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.

Children