glog.savedquery Properties

glog.savedQuery.limit.byUseCase.ML.MoveToAnalytics

24A

Used to overwrite the saved query limit for Logistics Machine Learning action Load Data into Analytics.

glog.savedquery.overwriteExisting

6.3.4

This property determines if a new saved query with the same GID as an existing saved query will without throwing any error, replace the old query with the new one. A value of false will throw an error on save. A value of  true will overwrite and mimic existing behavior.

Default: false

glog.savedQuery.parseSqlForNamedBinds

To permit backward compatibility with existing saved queries, the system optionally parses saved query SQL for named bind variables. If a named variable is found, the saved query uses Oracle's custom API to associate the name with the proper variable. If not, the saved query uses the standard JDBC API, based on variable index. Note that you cannot mix modes in a saved query SQL: you cannot use both named variables (e.g. :gid) and indexed variables (e.g. ?).

Set this property to 'true' to enable SQL parsing on saved queries. Default is false to prevent performance degradation.

Note: SQL parsing impacts all Oracle Transportation Management functionality based on saved query checks. This includes agent conditions, IF agent actions, tender, status checks, action checks, action reasons and action security impersonation.

glog.savedquery.show_all_savedqueries

Determines if queries in which the Use in Finder option is not selected show up on the finder screen in the saved query drop-down list. When this property is set to 'false', any queries with that check box not selected will NOT be shown on the associated finder. In order to get queries that do not have their Use in Finder option selected to show up on a finder, set this property to 'true'.

This property, when set to 'true', will enable saved queries to be used when creating workbench layouts.

Default: false