Accepted Solution

SQL Queries for User Input

Great Tech Team Deep Dive this morning, thanks.

I would like to know more about the schema that we can query for creating pull-downs in the User Input section.

For example, to get a list of aggregate names for a given controller we can use:



    storage.aggregate AS aggr, storage.array AS array


    aggr.array_id = AND (array.ip = '${controllerName}' OR = '${controllerName}')

But it would help to know more about the schema so we can create more precise SQL statements.



Re: SQL Queries for User Input

Hi Tom,

On the top left menu bar, select "Help" and then "Reference Manual".

An on-the-fly, automatically generated reference manual would  be created, where you can navigate the various parts.

On the top left you can find "cache tables" entity, which would detail all the tables in the cache and their structure.

Would be worth noting that the reference manual is generated "Here and now". So if you created workflows, finders and

even new cache tables - They would appear there and would be nicely documented if you took the time to do so :-)

Hope that helps,

Yaron Haimsohn

WFA team

Re: SQL Queries for User Input

Thanks, that helps a lot. The SQL Examples are very helpful, although it looks like you can only have one item in the select clause when using the SQL for user input queries.


Re: SQL Queries for User Input

Hi Tom,

For other examples, you can check out the Example WFA workflows.  Many of them have different user input queries... as well as staggered inputs (select Array, then Aggr, then volume then qtree, etc).

Currently with WFA 1.1.1, you can only have one select at a time.... or an SQL "concat" that joins multiple elements... but would then need to be split out with a function when used in the workflow.  In WFA 2.0, it will be possible to identify the "Main" element... and then additional supporting inputs that can help guide a WFA "Operator" to the best resource based on what WFA can see of the environment.

Hope this helps,