• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 22 replies
  • Subscribers 8 subscribers
  • Views 7377 views
  • Users 0 members are here
Related Discussions
Home » Discussions » User Interface

with() declarations refresh on any user action regardless of connection

marky
Hello:

I have noticed that anything declared in a with will get refreshed on any action the user takes on an interface, even if the with is unrelated to the action (such as a summary section at the top of the screen and a comments text box at the bottom, with no connection between the two).

Is this expected behavior for Appian?

It seems like with declared variables/rules/components should only refresh if one of the input variables changes.

If you see in the attached interface, changing the value in the textbox is refreshing the with variable, even though they are not related.

OriginalPostID-251823


example_interface.txt

  Discussion posts and replies are publicly visible

Parents
  • 0
    Carlos - C developers having to free the allocated memory is a restriction built upon the programming language. It's also a simple and straightforward solution to a devastating problem (running out of memory). Appian doesn't offer an easy, simple, or straightforward way to avoid performance problems. This is no real alternative for enterprise development. You either write un-maintainable code not using with() and relying on only saveInto, or you use with() and have performance issues. If it was as easy as putting a few free() in the code, we wouldn't be having this discussion, would we?
Reply
  • 0
    Carlos - C developers having to free the allocated memory is a restriction built upon the programming language. It's also a simple and straightforward solution to a devastating problem (running out of memory). Appian doesn't offer an easy, simple, or straightforward way to avoid performance problems. This is no real alternative for enterprise development. You either write un-maintainable code not using with() and relying on only saveInto, or you use with() and have performance issues. If it was as easy as putting a few free() in the code, we wouldn't be having this discussion, would we?
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.