Value not saving to PV in the process model

Hi ,

 

I have two forms

1) form - user will select the search filter (i.e. Decisionrequiredbydate operator =Between/Before/After) and selects records and submit (enabled default step back in other tab of this smart service)

2)second form - confirmation screen ,when user click on back button , the first form with selected search results should display (i.e.Decisionrequiredbydate operator =Between/Before/After)

 

To save the user selected operator value from first form , I have used operator pv.

But , I don't see the value is saving.

initially , I thought issue with the default back button. But , I have added a timer before the second form. I don't see the pv values are saving on submitting the first form itself.Screenshots.docx

PFA

 

ENHC0017141 - Patch - 2018-04-02_0218.zip

  Discussion posts and replies are publicly visible

  • Hi Soujanya B ,

    Please check the value in the form tab

    are you place the proper values

    Please check once.

    Thank,
    Bhanu.
  • Yes ,I am passing activity class parameter to form as a rule input and saving that value to pv.
    When passing the activityclass param to form (given value of ac param as pv!value)
  • I am very familiar with debugging this type of issue. In nearly every case that ever happened to me I was calling a rule that I had written using keyword [ rule!myRule( param1: ri!one, param2: ri!two, param3: ri!three, paarm4: ri!four ]. I'd always find that I had misspelled one of the keywords (like I just did up there for demonstration) and Appian is perfectly fine with that. It just ignores any that you've misspelled and doesn't mind that you have some of your params undefined.

    Start checking with the smallest sub-piece you can and see if values are saving properly, then go up one level, make sure they're still being saved properly, then go up one level, and repeat until you confirm they're saving into the process model when you're monitoring, then go down, down, down into the form that's supposed to receive the data. Once you find out how far upstream or downstream the issue occurs it should be a cinch to find the cause.
  • 0
    Certified Lead Developer

    Your screenshot document contains screenshots of the forms from the user's point of view, but for us to help debug it would be most helpful to see screenshots of the way you're saving your filter values within your SAIL form, as well as the configuration for saving such values back into the process PV's as configured in the user input task node.

    I understand basically what you're trying to accomplish here, but I'm afraid the solution is not overly simple or straightforward, and requires fairly strong understanding of SAIL forms and their setup within a process.