Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
9 replies
Subscribers
4 subscribers
Views
2252 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hello, We have seen occurrences in Appian 7.6 where a chain of nodes
thanosm
over 9 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?
OriginalPostID-148077
OriginalPostID-148077
Discussion posts and replies are publicly visible
Parents
0
rajatm
over 9 years ago
if the CDT type process variable value is updated by a script task , then that value should be retained. If that's not the case it is really strange. Please check the inputs / outputs in user input task to see if the value is not overwritten anywhere.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
rajatm
over 9 years ago
if the CDT type process variable value is updated by a script task , then that value should be retained. If that's not the case it is really strange. Please check the inputs / outputs in user input task to see if the value is not overwritten anywhere.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data