I have a process with a SAIL start form. The form field values are saved into prhttps://community.appian.com/discussions/f/process/3428/i-have-a-process-with-a-sail-start-form-the-form-field-values-are-saved-into-prI 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.en-USTelligent Community 12RE: I have a process with a SAIL start form. The form field values are saved into prhttps://community.appian.com/thread/11996?ContentTypeID=1Mon, 15 Sep 2014 02:04:24 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:a06ba252-a7c9-4096-b2d0-c0ee53c4fbafamoddThanks that worked!!<div style="clear:both;"></div>RE: I have a process with a SAIL start form. The form field values are saved into prhttps://community.appian.com/thread/11992?ContentTypeID=1Sat, 13 Sep 2014 11:51:16 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:37db738c-713b-4221-bef7-4e88f43532a2GouthamKrishnaUnlike a start form a task form(in you case Modify request?) can only save component values to ac&#39;s. So first check if you are directly saving into pv&#39;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&#39;s or pv&#39;s while you are calling this rule in form nodes.<div style="clear:both;"></div>RE: I have a process with a SAIL start form. The form field values are saved into prhttps://community.appian.com/thread/11990?ContentTypeID=1Sat, 13 Sep 2014 00:35:04 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cd0a855e-8a48-43a3-9eb8-5592f1891ab4Sahil GuptaHi, can you attach a screenshot of the issue and also please provide the SAIL code in question to better understand the issue.<div style="clear:both;"></div>