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
1 reply
Subscribers
6 subscribers
Views
1032 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hi, I have two activity chained user input tasks and there is an xor in bet
bhanuprakashg
over 12 years ago
Hi,
I have two activity chained user input tasks and there is an xor in between them which will re-route to the first user input task if the value entered is negative. Suppose that if I have entered -111 ,-222,333(for each of the instances) values in the first user input task and at the last instance ie at the value 333 since the value is not negative the second user input task is displayed.If I click on previous button the first user input task id displayed with the value 333 but the javascript onload event alert shows the value -222....
OriginalPostID-60744
OriginalPostID-60744
Discussion posts and replies are publicly visible
Parents
0
Sathya Srinivasan
Appian Employee
over 12 years ago
Using the 'previous' button does not roll-back the pv! values you set in your process model. However, the data retained in the form (i.e. the 'previous' form) are retained. This is why you are seeing the discrepancy. When you submit the form again, your pv! will be updated with the new value. Value is set into pv! after the form is submitted.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Sathya Srinivasan
Appian Employee
over 12 years ago
Using the 'previous' button does not roll-back the pv! values you set in your process model. However, the data retained in the form (i.e. the 'previous' form) are retained. This is why you are seeing the discrepancy. When you submit the form again, your pv! will be updated with the new value. Value is set into pv! after the form is submitted.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data