Hello, We have seen occurrences in Appian 7.6 where a chain of nodes

Hello,

We have seen occurrences in Appian 7.6 where a chain of nodes leads to a Script Task that changes the value of a specific field of a CDT variable in the process model (which is confirmed in the process history of the process instance) and the User Input Task (a SAIL form) that comes immediately after the Script Task uses that new value properly.

However, if the user changes menus in the Tempo interface, without submitting or saving the SAIL form, and then goes back to the same Task and opens the form, then the value of the modified CDT field has its previous value. And we see in the Variables of the Process Details that the CDT field has its previous value where the Process History shows that is has been modified to the new one.

Any ideas how this can be happening?

OriginalPostID-148077

OriginalPostID-148077

  Discussion posts and replies are publicly visible

Parents
  • The strange thing is that when the SAIL form loads for the first time (at the end of the chain) the value of the CDT field is the updated one and the SAIL form shows the extra components it's supposed to based on that value. But, when the user loads that same instance of the SAIL form (without having submitted it) at a later time the CDT field has the old value and therefore the SAIL form doesn't show the extra components it showed the first time.
Reply
  • The strange thing is that when the SAIL form loads for the first time (at the end of the chain) the value of the CDT field is the updated one and the SAIL form shows the extra components it's supposed to based on that value. But, when the user loads that same instance of the SAIL form (without having submitted it) at a later time the CDT field has the old value and therefore the SAIL form doesn't show the extra components it showed the first time.
Children
No Data