Whether this is a great, or extensible, or lazy, or short-sighted solution is likely quite debatable. However, I use this method for nearly every variable evaluation, and have never had a terrible issue with it.
Let’s set up a situation — say you’re doing a search for a set of values in a SQL table. The results need to be mapped to another variable, but if there are no results (null), the mapping component fails. We need to verify that a value exists prior to leading the data to the mapping component.
I’ve seen many, many different ways of doing this.
I’m personally very guilty of having overused the Equals Rule in my early days.
Then one day, someone showed me the Text Exists component, and that’s almost all I’ve used ever since. Need to check a SQL return? No problem. Test a Guid part of a complex data type in an SMP component result? Also no problem.
Not to say that there won’t be situations in which this will be problematic, of course. I’m just saying I haven’t come across any.
I use Text Exists for nearly every Visibility model for form elements. I use it prior to doing any data copies with the Copy Data Element to New Location component. I use it every time I need to check to see if a database entry exists for a proposed insert or edit to prevent duplicates. Here’s an example of that last one:
When validating a complex data type, make sure you validate a part that is “null not allowed” (like a primary key, name, or a Guid) to discourage false negatives.
That’s it! I hope it helps make your Workflow development a little easier.
Featured Components
Copy Data Element To New Location
atmaworkflow 