Does anyone know if the a!save operations in a saveInto always happen in order f

when we do multiple variables data >output > saveinto pv!s , it was always a race condition. the variables are not saved top down. I would think same thing happening here a!save, if we have a some calculations , do it first and then save.

I know for output on nodes its a race condition. But I have built quite a bit of SAIL where the saveInto order matters completely to the logic of the SAIL code and it usually works fine. I recently experienced an issue and looking at my code, the only thing I could figure out is that the saveInto order may be a race condition that almost always follows order but occasionally does not.

a!save()'s within a element saveInto are done in order. That's how it's been for me.

Thank you. That is exactly what I needed to know.

For anyone checking out this thread after switch to Community, I think documentation is here stating that saveInto does in fact save values from top to bottom.

The expression in the saveInto parameter evaluates when the user interacts with the component. Each item in the saveInto array evaluates one at a time. Therefore, if an a!save() parameter uses a variable that was updated higher in the list, a!save() evaluates with the variable's updated value. (Taken from page "SAIL Design" in the documentation on this site)

Hi Mark,
We are using 16.2 and we haven't faced any issue till now. If the execution order is not maintained we might face undesired behavior that will not be good.

saveInto for a component always works in Top to Bottom approach. In a script task the outputs doesn't evaluate in Top to Bottom Approach.