Skip to main content

Hi,  There are four ‘groups’ ( sections ) on my form.  I am using the URL line to tell the form based on URL parameter(s) which form group(s) to show or hide.  Looking at the URL and the form that opens, the form is parsing correctly, and form rules pick up the parameter seen here and show only the section(s) I want opened when the form opens.   That’s the ‘=Yes’ you see here.

The form properly is doing just that and one or many groups are hidden. Here is how the field is defined:  

 

The field in the list though shows ‘No’ - should be ‘Yes’. Yet, The Forms rules are doing fine to properly open / close groups. My workflow though, in a ‘Branch by condition’ step is seeing what is coming over from the list for that checkbox-ApplicationOnly as ‘No’ and goes down the ‘No’ path.

 

@LandsEnd Does your rule just read the url parameter and hide/show? or is it setting the value of that column? If the column is hidden on the form the rule also won’t update the value.


Hi Leighburke,  I found myself my answer, but it was not what I expected.  I got to understand fast that parameters on the URL WILL affect how the form presents, meaning show this / don’t show that, BUT params on the URL will NOT update that list item / column in the list itself. 

So, how to do you change / update what is on the URL as a param into the list itself ?   

I found that a value on a list can be changed by a URL value, but you have to do more than just expect the URL param to change a columns’ value.

First, do add a hidden column that is the parameter from the URL ONTO the form. Without that you won’t find it in any rules dropdowns.

Second, create a new rule that will in the IF statement of the new rule allow you to change actually a list items ‘value’. 

Third, When you do that, you’ll find your workflow now has a newly ‘set’ value for that URL parameter now updated onto the list column of interest upon a new ‘submit’, meaning also the workflow can now act against in a conditional statement in your workflow the new value ostensibly coming from a URL by way of a new rule.  Go figure that. 

What you see here is how to set a list items’ value based on what is coming in from a parameter on the URL.  BIG NOTE:  The then statement has options for what you can use as a ‘value’, in my case just a choice filed (true or false).  Just know that the list item you are interrogating is defined in the list settings, so what you’ll get as options for the dropdown for value will be what ‘type’ you set that list item value to in your list configurations.  Hope this helps someone out there. You can use URL parameters to affect a difference in a workflow.  The default value was false for that hidden field, but now changed to true, and that is what made the workflow react the way I needed it too. 

 

 

 

 

 


Hi, Just to follow up, here is the result of a new form submit, a new record I submitted just now.  The lists’ column/element is now Yes.  So it worked, and yes got a positive on the conditional test in the workflow and got a notification email.  

 

 


Reply