Triggering/Non-triggering SQL Queries

This topic describes the SQL triggering and non-triggering functionality.

This feature is exclusive to:
  • Operations Hub Classic version, accessible under Query definition and Page designer.
  • Specifically designed for input plug-ins (excluding widgets).

When creating SQL queries in Operations Hub, you have the option to specify whether the SQL query should be triggered or not when a change occurs in its input value. You can also specify if the value is mandatory or optional to trigger a query. By default, the options are set to Triggering and Optional for all SQL queries. This is also the default behavior of Operations Hub page designer PAGE DATA tab > Query option > Auto submit on input change.

When you use the query in page designer, you can choose to modify the triggering/non-triggering settings. The page designer settings take precedence over the settings in query definition. Once the query is added to a page, any changes to the settings in query definition is not carried over to page designer.

Non-triggering

If the input parameter is set to Non Triggering, then at runtime any change to the input does not trigger the query.

Triggering

If the input parameter is set to Triggering, then at runtime any change to the input will trigger the query provided all the mandatory fields are set.

Optional

If the input parameter is set to Optional, then the input need not have any value for the query to trigger.

Mandatory

If the input parameter is set to Mandatory, then the input should contain a value for the query to trigger.