Ens.Enterprise.Portal.MsgFilter.Assistant

The Message Bank Header table must be sorted by time and not ID, but we we can convert time ranges to ID ranges for each NodeId.

Name of Filter to use for searches.

Inherited description: Subscript under temporary session data to use for storing the search history for the viewer. The storage is activated by setting the ^Ens.Debug("UtilEnsMessages","sql") debug node to a positive number.

Flag to indicate whether the only restrictions on the query are time-related

Method to release the references held by the query.

Method to initialise the retrieval of the data and create the query to retrieve information for a specific Message Header.

Method which implements the custom fetch code which iterates over the TimeCreated index of the Message Header to retrieve candidate headers before checking the SessionStart condition on the message.

Callback to create the Filter class for this Assistant. The paging logic is implemented in this method based on the nextPageStartTime and nextPageEndTime properties of the supplied proxyObject, as the ID values are not sequential.

Callback to create a Zen proxyObject from a supplied Filter. Sequence manager searches are always excluded.

Initial method which parses the Filter into SQL terms and post-SQL terms. In the specific case where no terms have actually been specified, the custom BasicEnumerate query is used to create a result set. If the user does specify any terms, then this method constructs an inner result set based on the SQL terms and calls the execute method of this inner result set.

Helper method to return a valid ResultSet for the supplied Filter object. The result set construction itself is wrapped by the Enumerate query.

Method to finalize the generated SQL query. Any modifications to JOIN order or the FROM clause should be implemented in this callback. The pSelect, pFrom, pWhere and pOrder arguments represent the SELECT, FROM, WHERE and ORDER BY clauses of the query thus far. The pSelectTerms and pFromTerms arguments are arrays that contain further values and tables which have yet to be added to the respective clauses. The contents of these arrays in combination with the state of the current Assistant can be used to determine what (if any) modifications should be made to the query as constructed by the parser. In the specific case of a single SearchTable condition, the Message Bank code makes use of the %STARTTABLE keyword to ensure that we use the SearchTable condition first.