Obsidian Workflow Entry Block with Page Parameters doesn’t set Attribute Values

[FrankGrand]

Description

The Obsidian Workflow Entry block doesn’t allow workflow attribute values to be set by page parameters, unlike the Legacy/WebForm block.

This post refers to an approach in which the page parameter key must match the corresponding workflow attribute key, and the value must be provided in the workflow attribute’s field-type raw value format (see the Workflows & Lava reference page).

This post excludes the approach of setting attribute values from page parameters using
{{ 'Global' | PageParameter:'AttributeKey' }}. This method works correctly with the Obsidian Workflow Entry block and is currently the best available workaround for this limitation.

Actual Behavior

The page parameter values are not stored in matching Workflow Attributes if you use the Obsidian Workflow Entry block.

Expected Behavior

If a page parameter matches the key of a Workflow Attribute, the value of the parameter should be stored in that workflow attribute, without requiring an action in the workflow. This is how the Legacy/WebForms Workflow Entry block works.

Steps to Reproduce

1. Go to the Contact Us page on the Rock Demo Site to launch the External Inquiry workflow type (Id: 13)
   a. Currently, it is using the Legacy/WebForm Workflow Entry block.
2. Open the page using this URL (it includes parameters to pre-fill the first and last name fields): https://rockrmsdemo.com/ContactUs?FirstName=Ted&LastName=Decker.
3. Observe that the First and Last name have been prefilled.
4. Repeat Step 2 using the Obsidian Workflow Entry block on that page and note the difference in behavior (the attributes and therefore the inputs remain blank).

Issue Confirmation

• Perform a search on the Github Issues to see if your bug is already reported.
• Reproduced the problem on a fresh install or on the demo site.

Rock Version

18.1.0

Client Culture Setting

en-us