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
  • @thanosm I would like to ask few simple questions as follows in order to dig deep into the issue:

    1. Did the user click 'Save Changes' before moving out of 'Tasks' tab?
    2. What type of the variable is your CDT - PV or AC or local?
    3. Are you assigning any value to the CDT variable in load() or with() once again?
    4. Are you sure that the CDT variable isn't being modified under the 'saveInto' attribute of other SAIL component(s) on the form?
Reply
  • @thanosm I would like to ask few simple questions as follows in order to dig deep into the issue:

    1. Did the user click 'Save Changes' before moving out of 'Tasks' tab?
    2. What type of the variable is your CDT - PV or AC or local?
    3. Are you assigning any value to the CDT variable in load() or with() once again?
    4. Are you sure that the CDT variable isn't being modified under the 'saveInto' attribute of other SAIL component(s) on the form?
Children
No Data