Add New Data Element/Single Value Mapping = Answer to Editor "Woes"

The following is a user support request:

The problem I am having is in passing parameters to a SharePoint query via the generated SharePoint list module.SearchItems. For static queries (constant value), I can use "not equal to", ">", "<", etc. conditions but for dynamic queries based on other model variables (Process Variables), I can only map to the equals condition.

I'd like to use process variables but be able to say "where task.PercentComplete > 50 AND task.AssignedTo = ProcessVarAssignee". As far as I can tell, I can't use the > condition in a data mapping and there seems to be no other option for interacting with the SharePoint generated component.

A way to get around some editor issues is by using a Add New Data Element/Single Value Mapping component combo. My fix for the user was as follows:

OK, I've found a "workaround" s.t. you can set the conditions... the data mapper currently only allows you to map simple types, and not enumerations (most likely intended)

1. Use an Add New Data Element comp... hook it up to a Number datatype, and lets call the variable MyNum
2. Use another Add New Data Element comp... hook it up to your Generated.CreateSPTasks.SR_TasksQuery datatype, and lets call the variable 'abc' (boring, I know). For the Value, check your "Use % complete" checkbox and set your "% complete" condition to GreaterThan
3. Use a Single Value Mapping comp... hook it up to your Generated.CreateSPTasks.SR_TasksQuery datatype. Map it into an existing variable 'abc'. For the mapping, drag our process var MyNum over to the "X Complete" value field.
4. Call your generated Sharepoint Search comp, hooked up to your query process variable. Your query should now be a Greater Than condition, as well as hooked up to a process variable for value.