Hello All,
We have created a record type and some related actions. The related action is based on process model and process model is activity chained. When we configure this record actions using "DIALOG BOX" then after record action gets completed, The data inside summary view is not getting refreshed automatically. User has to refresh the page to get updated data. Does anyone has any idea as to why is this happening? Or is it something appians default behavior?
Discussion posts and replies are publicly visible
When this is a plain setup of a record, a record view and a record action, then my first suggestion would be: "Check chaining!". For everything else, I would need more details.
Unknown said:For everything else, I would need more details
I believe the "dialog box" style related action behaves differently w.r.t. chaining, compared to "traditionally" configured related actions. Hence my suggestion above for checking the Refresh After setting.
Chaining behavior with record actions is consistent whether you open an action in the same tab or a dialog. You have to check 3 things:
1. Are you chaining through the write to DS node in your process?2. Is your local variables configured as a refresh variables to refresh after RECORD_ACTION?
3. Is your local variable using an expression rule? Within that expression rule, are you using a!localVariables() and making sure your variables always refresh? docs.appian.com/.../Local_Variables.html
Danny Verb said:Chaining behavior with record actions is consistent whether you open an action in the same tab or a dialog
Are you referring specifically to the "refresh" behavior of the subject record upon return to the interface following completion of the related action? Because if so, I was under the impression that this might not really be true (though I haven't specifically tested in a while).
I am using this exact functionality in a user input task to implement file upload which survives a "Save Draft". A record action opens a dialog, which uploads the files, stores to DB and the a local variable fetches the files after the action is completed.
Yes, docs.appian.com/.../Record_Action_Component.html
Danny Verb said:Yes, docs.appian.com/.../Record_Action_Component.html
I dunno, the details I'm finding there seem to kinda agree more with what I was saying before. Am I missing something?
Yes, the current page state is retained since we don't refresh the browser page like related action used to. Local variables set to refresh after record action will still update and then propagate through the page.
Most of the time the issue is that an underlying expression rule is using a!localVariables() which causes the first evaluation of that rule to get cached.