Skip to main content
FrankatMSC
Level 4
May 29, 2026
Question

Validating a property value against a list of valid values

  • May 29, 2026
  • 2 replies
  • 11 views

I’m looking for suggestions for validating an issue property against a list of valid values in Fusion.  I considered importing the valid list from a CSV file, but I haven’t been able to determine how to compare the property value to the list and confirm that it is valid.  Any suggestions would be greatly appreciated.

2 replies

tekmera
Level 2
May 29, 2026

Hey ​@FrankatMSC 

I think what you are looking for is the contains() function. (https://experienceleague.adobe.com/en/docs/workfront-fusion/using/references/mapping-panel/functions/array-functions)

 

That's the comparison function. Once you have your valid values in an array, contains(array; value) returns true or false, and you branch on that in a router or filter.

 

If you're sticking with the CSV approach, you may have to run the output through an Array Aggregator first to collapse the iterations into one array. Then the contains check works against it.


Let me know if that makes sense.

David Kershaw | Workfront & Fusion Architecture | Tekmera | https://tekmera.ai/work-with-us/adobe-practice
FrankatMSC
Level 4
May 29, 2026

Thanks ​@tekmera , That way makes perfect sense.  You mention “Sticking with CSV”, is there a better way to get valid answers?  The list comes from a forms form properties dropdown values.  Is there a way to pull it in from there?

tekmera
Level 2
May 30, 2026

Hey ​@FrankatMSC - I think it depends on whether the values are static or dynamic - do you expect them to change over time? If they are static, I’d default to the simple approach - just type them into Fusion. If they are dynamic, loading them within the scenario makes sense. Hope that helps.

David Kershaw | Workfront & Fusion Architecture | Tekmera | https://tekmera.ai/work-with-us/adobe-practice
Level 1
May 30, 2026

I'd import the valid values into a lookup table and validate the issue property against that table. If a match is found, it's valid; otherwise, trigger a validation error. That's usually much easier to maintain than hardcoding values in rules.