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
3 replies
Subscribers
6 subscribers
Views
2562 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
I have a process with a SAIL start form. The form field values are saved into pr
amodd
over 10 years ago
I have a process with a SAIL start form. The form field values are saved into process variables. Process Initiator fills the form and submits for approval. Approver rejects, as a result its sent back to user, who submitted the form, for modification. User makes some modification and submits it again. Modify request User Input task reuses the same SAIL form but when the user modifies the form data and submits, the new values are not reflected in the process variables. ...
OriginalPostID-122268
OriginalPostID-122268
Discussion posts and replies are publicly visible
Parents
0
GouthamKrishna
over 10 years ago
Unlike a start form a task form(in you case Modify request?) can only save component values to ac's. So first check if you are directly saving into pv's (saveInto: pv!variable). This works only if it a start form. So to better reuse your form rule in both type of forms you must save into ri!variable and map these rule inputs with appropriate ac's or pv's while you are calling this rule in form nodes.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
GouthamKrishna
over 10 years ago
Unlike a start form a task form(in you case Modify request?) can only save component values to ac's. So first check if you are directly saving into pv's (saveInto: pv!variable). This works only if it a start form. So to better reuse your form rule in both type of forms you must save into ri!variable and map these rule inputs with appropriate ac's or pv's while you are calling this rule in form nodes.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data