Rules Engine parameters

Previous Next

Do not confuse with Rules Engine properties. Do not confuse with Deployment Configuration parameters.

To set Rules Engine parameters, choose Define, Rules Engine Parameters from the USoft Definer menu.

By setting and getting Rules Engine properties, you can override a number of these settings dynamically.

Rules Engine parameter

Default

Description

ALLOW_PLUGINS

True

Specifies if this application allows plugins to be added to the application.

ALLOW_SET_MANIPULATIONS

auto

Specifies whether SQL manipulations are handled set-oriented (True) or not (False).

Possible values are 'auto', 'True' and 'False'. The 'auto' value (the default) is the equivalent of True for runbatch.exe and False in other contexts (Client/Server, Rules Service).

For details on how set-oriented handling is different from record-by-record handling, in the Rules Engine Guide, please consult the " Rules Engine Optimisation Techniques " topic or search for "set-oriented". The Rules Engine Guide is published as part of the USoft Definer documentation. To access it, press CTRL + F1 in USoft Definer.

COMBINE_QUERIES

True

Specifies if the Rules Engine should combine the statement used to retrieve and lock the records to be updated with the statement used to determine the new values

DEFAULT_DATE_FORMAT

DD-MON-YY

Specifies the default IO format to be used when converting a date into a string.

DEFER_RESTR_REL_CHECKS

True

Specifies the moment when restrictive relational checks are performed.

In a relationship, the Update Rule and Delete Rule attributes can be set to 'Restricted' to indicate that it is not allowed to update or delete a parent record for which corresponding child records exist. If the DEFER_RESTR_REL_CHECKS parameter is set to True (the default), these restrictive checks are performed at commit time. Otherwise, the checks are performed at record-store time.

LOCK_PARENT_ON_SEQNO

False

Specifies whether parent records must be locked when child records are being entered. This type of locking prevents identical generated values in a child column that is part of a key spanning multiple columns.

QUERY_ORDER_TURNING_POINT

100

Specifies the the maximum number of rows that can be returned by a component table in order to be the first table fetched.

RDBMS_CONNECT

auto

Specifies whether or not a USoft application should try to reconnect to the database after a connection failure.

Possible values are 'auto' (the default) and 'reconnect'.

If this parameter is set to 'auto', the USoft application will try to reconnect.

If this parameter is set to 'no reconnect', the USoft application will not attempt to reconnect to the database. This can be a desirable setting for security reasons.

READ_ONLY_ODBC

False

Applies only to Rules Service contexts.

Specifies if the Rules Service when accessed via ODBC is restricted to querying (or: returning) application data, as opposed to being allowed to manipulate application data.

This parameter has an effect in settings where an application (such as MS Excel) calls a Rules Service that accesses the USoft ODBC data provider, as opposed to accessing a USoft data source through a non-ODBC channel. In such a setting, if READ_ONLY_ODBC = True, the Rules Service is restricted to querying (or: returning) application data, as opposed to being allowed to manipulate application data.

Using this parameter is a shortcut way of implementing authorisation rules. The alternative is to grant a Table Right with Access Right = SELECT for each combination of role and application table.

ROLE_MERGE

False

Specifies whether access to functionality must be merged for application users who have multiple roles.

STARTUP_EVENT

False

Specifies if the Rules Engine should initiate a startup event by inserting a record in table T_EVENT at startup.

TEMP_TABLE_AT_OWNER

False

Specifies if temporary tables are to be created in the owner's schema.

TRANSACTION_CHAIN_DEPTH

500

Specifies the maximum number of chained transactions.

UNIQUE_KEY_CHECK

True

Specifies whether the Rules Engine must perform unique key checks in the case of non-manual data entry, for example sql-script() functions.

If this parameter is set to True, error feedback will be faster.

If it is set to False, performance will be slightly better in the case of non-manual data entry, for example sql-script() functions. In this case, unique key checks are still performed by the RDBMS so that data integrity is ensured. For data entered manually, unique key checks continue to be performed by the Rules Engine.

Set this parameter to False only in time-critical situations where overall performance

UPDATE_SUPERTYPE_ON_INS

False

Specifies whether inserting a subtype for an existing supertype must be considered as an UPDATE on the whole constellation.

If this parameter is set to False, when a subtype is inserted for which the supertype already exists, an error will be raised because the key is not unique.

If this parameter is set to True, inserting a subtype for an existing supertype will be considered as an UPDATE on the whole constellation. In this update the subtype indicator column(s) will be set as well.

Note that in this case only those transitional constraints that have been specified as Fire On Update will be fired.

UREQUIRE_INPUT_XSL

(null)

Specifies the filepath and filename of the XSLT transformation (if any) that must be applied to business rule input from URequire before it is imported into USoft Teamwork.

VERIFY_VIEW_WHERECLAUSE

True

Specifies if manipulations on logical views should be checked to see if they match the view’s WHERE clause or not.

 

See also

Rules Engine properties

Deployment Configurations: parameters