iConsole Review Queue Guide › Customizations › Customizable Stored Procedures and Functions › GET_TYPE_P_PRED_STUB_1

GET_TYPE_P_PRED_STUB_1

Purpose

See the previous description.

Type P data is the prime target for the main selection that drives the building of the queue. An example of Type P predicate could be to define that the prime target for selection is events that have triggered policy.

If this procedure is customized then it has to return an SQL sub query, that projects the eventuid and eventtimestamp pairs of events that are to be considered Type P data.

Default implementation

Select only those events that have triggered policy.

SQL Server custom implementation

In SQL Server, the custom function must always be named WGN_RQ_GET_TYPE_P_PRED_CUSTOM_n_1 where 'n' is the RQ Process number for which this function applies. If the name of the custom function(s) deviates from that stipulated above then the RQ process to populate the Review Queue will merely ignore it and subsequently it will fail to implement the intended custom behavior.

Oracle custom implementation

In Oracle, the custom function is contained within the stored package WGN_RQ_CUST and must always be named WGN_RQ_CUST.GET_TYPE_P_PRED. Additionally, the process number is passed to this function such that multiple implementations can be coded on a per process basis by using a PL/SQL CASE construct. The custom package body is contained within the supplied file WGN_RQ_BODY.sql and can be modified accordingly.