Hello,
I have a form that needs two approvers. I am adapting the example of https://docs.appian.com/suite/help/19.4/Process_Modeling_Tutorial.html for a first approval:
Thanks for your help in advance.
Discussion posts and replies are publicly visible
After first user input task add XOR condition to check approver status. If approved then add one more user input task for second approver showing first approver status.
Thanks for all the help.
Are the conditions that I have added correct?
That looks good to me! I'm assuming the pv!approval is a Boolean value? You also have to make sure this value is saved as part of the output from your first User Input Task.
Configured like this Peter Lewis?
Is there something in your form where the user is choosing to approve or not approve? If this approval decision comes from the form, then you need to create an input for your approval (most similar to this step: https://docs.appian.com/suite/help/latest/Process_Modeling_Tutorial.html#add-an-approval-step-with-a-user-input-node)
On the 1st approval on the bottom there are radio buttons, pretty much followed the tutorial, but data for one of the sections of the form is blank (the data missing has numeric values):
Kind of clueless here...
There's two things to check in this case. First, make sure that you provide a value for your variable in the inputs tab for the second approval task. For example, I provided details about a vehicle (that I saved in pv!vehicle) in form 1. In form 2, I now display this by adding the value to display as pv!vehicle
If you have this set correctly, also check the forms tab to make sure your form has the rule input mapped to the variable you created in the first tab.
The data is blank because either user has not provided it or not selected any value from radio button. In this case check if the data found is blank, then provide default value. Also, you can provide default values in the activity class parameters so that radio buttons would not be blank on page load.
Hi Peter<Yep you were correct, the issue was with the second form, the rule inputs were not mapped to the variables at all.
Thanks for the great help!
However I still have an issue with a section of the formula that has a calculation variable. The data on those fields is not being passed on.
local!sumBuyOnly: sum(