PLU-489 [FIND-MULTIPLE-ROWS-7]: Compute parameters with wildcard

[kevinkim-ogp]

TL;DR

This PR adds support for wildcard syntax in parameter computation, allowing users to use column values from find multiple rows / get table rows steps in subsequent steps.

What changed?

• Get all values from an array: {{step.id.arrayProp.*}}
• Get specific properties from objects in an array: {{step.id.arrayOfObjects.*.propertyName}}

The implementation includes:

• Updated regex patterns to recognise wildcards in variable paths
• Added logic to handle wildcard substitution in compute-parameters.ts
• Comprehensive test cases for various wildcard scenarios

This enhancement provides more flexibility when working with array data in workflow steps.

How to test?

Setup

• Create a Tile find multiple row step and an Excel get table rows step successfully
• Create another step e.g., Postman / Telegram / Slack

Test

• Use variable for column values in your action, test the step and verify that the output uses the correct values
• Update the Tile or Excel sheet, re-run the action, verify output uses the updated values

Screenshots

Screen Recording 2025-06-02 at 6.25.58 PM.mov (uploaded via Graphite)

[kevinkim-ogp]

• PLU-489 [FIND-MULTIPLE-ROWS-7]: Compute parameters with wildcard #1029 👈 (View in Graphite)
• [FIND-MULTIPLE-ROWS-6] PLU-490 : Refactor output to common table type #1026 : 1 other dependent PR (#1065 )
• PLU-488 [FIND-MULTIPLE-ROWS-5]: Get Excel column values dynamically #1025
• PLU-487 [FIND-MULTIPLE-ROWS-4]: Get Tiles column values dynamically #1023
• PLU-444 [FIND-MULTIPLE-ROWS-3]: Show test step output in table #923
• PLU-429 [FIND-MULTIPLE-ROWS-2]: M365 Excel  #900
• PLU-428 [FIND-MULTIPLE-ROWS-1]: Tiles #899
• trunk/for-each

This stack of pull requests is managed by Graphite. Learn more about stacking.

[linear]

PLU-489 Find multiple row: dynamic column access in other steps

[datadog-opengovsg]

Datadog Report

Branch report: chore/find-multiple-rows/compute-wildcard-parameters
Commit report: 3e38748
Test service: plumber

✅ 0 Failed, 852 Passed, 0 Skipped, 2m 39.78s Total Time
⬆️ Test Sessions change in coverage: 1 increased (+0.44%)

[pregnantboy]

BugBot run

[cursor]

✅ BugBot reviewed your changes and found no bugs!

---

BugBot free trial expires on June 9, 2025
You have used $0.00 of your $1.00 spend limit so far. Manage your spend limit in the Cursor dashboard.

Was this report helpful? Give feedback by reacting with 👍 or 👎

[pregnantboy]

can be slightly stricter to enforce that asterisk (*) must be the only character in the segment

valid: {{step.00000000-0000-0000-0000-000000000000.*.abc}}
invalid: {{step.00000000-0000-0000-0000-000000000000.def*.abc}}

Suggested change

	/({{step\.[\da-f]{8}-(?:[\da-f]{4}-){3}[\da-f]{12}(?:\.[\w* -]+)+}})/g
	/({{step\.[\da-f]{8}-(?:[\da-f]{4}-){3}[\da-f]{12}(?:\.([\w -]+|\*))+}})/

[pregnantboy]

this does not enforce that asterisk cannot be in the last segment. for that the check can be done later.

[kevinkim-ogp]

updated regex and added helper func to validate the step variable.
we only allow 1 wildcard and it cannot be at the start or end of the variable segment, example

invalid: {{step.00000000-0000-0000-0000-000000000000.*.abc}}
invalid: {{step.00000000-0000-0000-0000-000000000000.abc.*}}
invalid: {{step.00000000-0000-0000-0000-000000000000.abc*.def.*.ghi}}
valid: {{step.00000000-0000-0000-0000-000000000000.abc.*.def}}

[pregnantboy]

are there edge cases to be handled here?

[pregnantboy]

will this break if values contain comma?

[kevinkim-ogp]

closing this PR first, we are not allowing users to select the column variable in the find multiple rows output.