The Workspace Alert component can be used with the Conditional Sub-Queries component, and is linked to the Conditional Sub-Queries primary table (see Dashboard Studio Conditional Sub-Queries Component).
The Conditional Sub-Queries component is configured to handle the threshold and monitor for exception conditions. Using the Conditional Sub-Queries component, threshold filters can be configured with more flexibility; for example, where business rules are more complex and multiple thresholds require handling at one time.
To use the Workspace Alert component with the Conditional Sub-Queries component, select Used Conditional Sub-Queries (CSQ) in EPM Workspace Alert Properties.
When Used Conditional Sub-Queries is selected, you do not have to enter values for Column, Operator, and Threshold Limit; however, threshold values must be configured for the Conditional Sub-Queries, and the primary query must be selected from Alert Details Query.
When using conditional sub-queries, you provide table, query, and exception string data. The _sysException column and filter are not added to the table, however, since the Workspace Alert component relies on the Conditional Sub-Queries limits to look for exception data. The specified Conditional Sub-Queries table is monitored after the process is run, and any exceptions or alerts are reported.
Note:
For the Workspace Alert component to work with the Conditional Sub-Queries component, EPM Workspace Alert Properties must have a higher priority than Conditional Sub-Query Properties. During the onPostProcess() event, the Workspace Alert component onPostProcess() method must be called before the Conditional Sub-Queries component onPostProcess() event. If the Conditional Sub-Queries component onPostProcess() method is called first, it causes complications and incorrect behavior when handling alert messages.