• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 13 subscribers
  • Views 179 views
  • Users 0 members are here
Related Discussions
Home » Discussions » User Interface

How to Refresh an Entire Interface After a Process Model Execution?

lumi29

I am working on a project where I need to refresh an entire interface after a process model has completed execution. I need to ensure that once this process model finishes executing, the associated interface is refreshed to reflect any changes.

I have tried using the onSuccess property to trigger a refresh, but unfortunately, I have not been successful with this approach.



I would appreciate any advice or examples on how to implement this, whether it involves using specific Appian components, plugins, configurations, or a combination of approaches.

Thank you in advance for your assistance!

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee

    An answer in bite-size chunks:

    • an interface is automatically refreshed after you conduct any human interaction with it (and, of course, you can use auto-refresh to periodically refresh the interface but that's less of interest to this scenario)
    • the onSuccess attribute (and it's correlating onError attribute) only refer to whether the process was successfully started or not, not whether it completed successfully or not. If you need the latter then you'll need to set and pass back a flag to the interface from the process in the fv!processIfno
    • probably the key concept here is that the control is passed back to the interface (i.e. it will get refreshed when) the last chain in the process is reached. So if you need the results from your processing to be available you'll need to chain all the way to the last update in your process that you want to see refreshed in your interface
Reply
  • 0
    Appian Employee

    An answer in bite-size chunks:

    • an interface is automatically refreshed after you conduct any human interaction with it (and, of course, you can use auto-refresh to periodically refresh the interface but that's less of interest to this scenario)
    • the onSuccess attribute (and it's correlating onError attribute) only refer to whether the process was successfully started or not, not whether it completed successfully or not. If you need the latter then you'll need to set and pass back a flag to the interface from the process in the fv!processIfno
    • probably the key concept here is that the control is passed back to the interface (i.e. it will get refreshed when) the last chain in the process is reached. So if you need the results from your processing to be available you'll need to chain all the way to the last update in your process that you want to see refreshed in your interface
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.