Decision attributes

The required Decision Name must be unique across the repository and is the handle whereby a decision is called. Decision Names may contain alphanumeric characters, hyphens, and underscores, but no spaces, single quotes or double quotes.

The required Decision SQL statement must be a valid SQL SELECT or INVOKE statement, or a valid SQL fragment. A SQL fragment is a SELECT statement that has only a SELECT clause, or only a WHERE clause.

The Decision SQL is executed when the Decision is called. If it is a SELECT statement:

•If the query retrieves 1 row, the Yes Action script is executed once. If that script contains placeholders ( :1, :2 ... ), then these are substituted by values from the SELECT output list for the retrieved row.

•If the query retrieves more than 1 row, the Yes Action script is executed once for each row. If the script contains placeholders ( :1, :2 ...), each time these are substituted by values supplied by the row that is currently processed.

•If the query does not retrieve any rows, the No Action script is executed once.

If it is an INVOKE statement, the INVOKE statement is executed, and then the Yes Action script is executed. If the Yes Action contains placeholders (:1, :2 ...), then these are substituted by result values returned by the invocation.

If the Decision SQL consists of a SELECT clause only, the expressions in the output list are evaluated and passed to the Yes Action, where they substitute placeholders ( :1, :2 ...):

SELECT   'data-report(''' || 

         RulesEngine.GetProperty('tempdir') || 

         '\ClipBoard_' || :"CurrentInfoBox" || '.xml'')'

In this case, a WHERE clause may be added even if a FROM clause is not present:

SELECT   'data-report(''' || 

         RulesEngine.GetProperty('tempdir') || 

         '\ClipBoard_' || :"CurrentInfoBox" || '.xml'')'

WHERE        NOT :"CurrentInfoBox" IS NULL

If the Decision SQL consists of a WHERE clause only, the Yes Action script is executed once if the WHERE condition evaluates to true. The No Action script is executed once if the WHERE condition evaluates to false.

WHERE :f_datatype = 'CHECK'

The WHERE keyword may be omitted in this case:

:f_datatype = 'CHECK'

If the Decision SQL is empty, the Yes Action script is executed once.

For examples of Decision SQL values and how they collaborate with Yes Action scripts, see the Yes Action section below.

The required Yes Action is a script containing one or more actions in the USoft action syntax. Multiple statements are separated by whitespace or by semi-colons(;), typically by a newline.

The Yes Action script is executed when the Decision is called and the Decision SQL produces 1 or more rows. The Yes Action is executed once for each row.

Example 1

If the contents in the clipboard look like a valid import, an attribute value is extracted and passed to a second decision called CP_PASTE_2:

(Decision SQL:)

SELECT        USXSL.Value( TO_CLOB( Clipboard.GetText() ) , 'MultiImport/@type' )

WHERE        TO_CLOB( Clipboard.GetText() ) LIKE '%<MultiImport type%'

(Yes Action:)

ActionDecision( CP_PASTE_2, :1 )

Example 2

In this GUI example, 2 global variables are set and a window is opened if a datatype is one of a list of specific datatypes (Yes Action). Otherwise, an error message is produced (No Action).

(Decision SQL:)

SELECT   'global_query_name:'  || :query.name

,        'global_query_confn:' || :query.constraint_file 

FROM     dual

WHERE    :datatype in ('DECIMAL', 'INT', 'INTEGER', 'NUMBER', 'NUMERIC', 'SMALLINT', 'TINYINT')

(Yes Action:)

ResourceFileUpdate( :1 )

ResourceFileUpdate( :2 )

WindowCreate(Constraint Violation Report)

(No Action:)

MessageLanguage(USoft Benchmark Message, BM_NOT_A_CONFIG, WARNING)

The No Action is a script containing one or more actions in the USoft action syntax. Multiple statements are separated by whitespace or semi-colons(;), typically by a newline.

The No Action script is executed once when the Decision is called and the Decision SQL produces 0 rows.

For an example, see the Yes Action section above.