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

thanosm over 10 years ago

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?

Discussion posts and replies are publicly visible

Parents

0 thanosm over 10 years ago

Even if the SAIL form modifies the value of that CDT field while the user is working it BUT does NOT submit it, the next time the SAIL form is loaded won't that CDT field have the value it had the first time it loaded?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 thanosm over 10 years ago

Even if the SAIL form modifies the value of that CDT field while the user is working it BUT does NOT submit it, the next time the SAIL form is loaded won't that CDT field have the value it had the first time it loaded?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data