Expressions and functions side effects

Question

Hello all, 
 I would like to ask for a clarification on the concept of side effects of executing expressions and functions. 
 The section Functions and Side Effects on the Expressions page of the Documentation, states various scenarios where functions and generally expression components can be executed more than once. 
 For that reason, all functions should not modify external systems. 
 However, what is not 100% clear, is whether or not a Rule Expression that is a component of an expression that is being executed falls under the same side effects category as Functions. 
 Any ideas?

davel001150 · Answer

I think the answer to your question is Yes. Appian gives no guarantees about the order of operations, except in a couple of places, so you want to build expression rules in regard to that fact. You want to get the same result regardless of what order the steps should take place. You also want to avoid any consequences to anything else other than the intent of the function / expression only. You don't want saving a PV to another PV to affect your database in any way. 
 For instance, a long time ago I overheard a conversation about two of my colleagues finding a bug. They had a query in a with() variable, and it, in turn, called a rule that also had a query in a with() variable. This is why, they found out, each user was running the same query many hundreds to thousands of times whenever they used the form. It was actually set up to rerun the query; I think it queried the same select statement 101 times every time the user typed a character, and there were something like 20 text fields on the form. The expression, as written, had the unintended side-effect of taking up connection threads from the thread-pool. 
 I believe local variables are evaluated in order from top to bottom, and I know saveInto parameters are evaluated in order from top to bottom. On the process modeler, a script task's inputs are evaluated in random order (perhaps multiple times), and afterward the outputs are evaluated in random order (perhaps multiple times). If you need two outputs to be run in a specific order, you have to make 2 script tasks to ensure they do.