AutoRefresh editable grid

Any time you reload a summary view, all local values should be reloaded.  I assume you're referring to a related action, so is there a chance the user is being returned to the summary view before the data changes in the related action have had a chance to be written to the database?  Can you describe any more about your process flow, or what the user is actually experiencing?

I have a related action-> update.

When I update the values in the editable grid the values are return to DB. When I click submit then it is re-directed to summary view and the editable grid is not updated. Only after I refresh the page, the grid values are updated.

Is there a chance to auto-refresh the summary view.

Can you post a screenshot of your process flow?  I'm >90% sure you just need to enable activity chaining between the completion of the user input, and the WTDS node(s).

Could you please elaborate on this point -> need to enable activity chaining between the completion of the user input, and the WTDS node(s)

 a!writeToMultipleDataStoreEntities -> I'm using this to store values.

Can you clarify as to the configuration of your related action?  Usually when we say Related Action we mean an action which launches a process model, and therefore uses the process model nodes to write to the database.  If you're using some other technique to write to the database then we'll need more details before being able to provide any useful advice.

Can you clarify as to the configuration of your related action?  -> yes 

1. I have a interface to update the grid.

2. I have used a!writeToMultipleDataStoreEntities to store the values.

3. My process model has the start node to launch the "update interface".

4. Once the form is submitted, it is re-directed to summary view where the values are not getting refreshed automatically(need to refresh the page then the values are visible in grid)

In my update interface I have few fields such as name, address. These values are getting updated automatically without refreshing the page. I've used a!refreshVariable. I'm facing this challenge only with editable grid.

Does your process model have anything other than the start form and an end node?

Where and how are you calling a!writeToMultipleDataStoreEntities() within your interface?  I assume you mean that this interface is being used as the related action start form?

Can you post your form code (or snippets of relevant portions of it)?  Please be sure to use "insert code" when pasting code here of any length.

Does your process model have anything other than the start form and an end node? (NO)

 I assume you mean that this interface is being used as the related action start form? (Yes)

Thanks for posting your WTDS code, however just this snippet alone doesn't provide me with the context of where and how in your SAIL form it's being called, which is what i was asking to see in order to provide any meaningful feedback.

Could you please tell how can I Auto-refresh the summary page after performing related action.

I believe I mentioned previously, when you go back to the summary page after completing a related action, it should reload all local values by default (unless your related action is set to open in a pop-up dialog, in which case this changes somewhat). 

The normal reason causing data to appear *not* to refresh is when the form is accessed again before the write has a chance to fully complete - which is why I'm asking to see your code relevant to where and how your WTDS call is being made.

In the case that you're calling your related action as a pop-up dialog, I believe (but haven't done a lot of testing of this personally) that you just need to update your on-form RefreshVariables such that they have "refreshAfter" values of "RECORD_ACTION".

I believe I mentioned previously, when you go back to the summary page after completing a related action, it should reload all local values by default (unless your related action is set to open in a pop-up dialog, in which case this changes somewhat). 

The normal reason causing data to appear *not* to refresh is when the form is accessed again before the write has a chance to fully complete - which is why I'm asking to see your code relevant to where and how your WTDS call is being made.

In the case that you're calling your related action as a pop-up dialog, I believe (but haven't done a lot of testing of this personally) that you just need to update your on-form RefreshVariables such that they have "refreshAfter" values of "RECORD_ACTION".