How to Use Context Variables to work from the InfoCenter search page to trigger rules?

(Doc ID 1040113.1)

Last updated on MAY 21, 2018

Applies to:

Oracle Knowledge - Version 8.0.x and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Symptoms

Each Context Variable you add is a “Preference”. Using context variables you can access business data through Dictionary Rules, which enables you to set Business Conditions within Rules based on user, session, and other context information.   The providers determine where the variable can be used.  If you want to use it in testdrive as part of a quality monitory profile, the Session provider must be set.  If you want to use it in the runtime as a variable on the request, then the Request Parameter provider must be set.

Prior to 8.5.1 there were two out of the box context variables that are commonly used for analytics: the User.Segment and Query.Source context variables which are all passed to the runtime for analytics from the InfoCenter search page.  In 8.5.1 and after these context varables are not part of the OOB implementation.  The query_src is still passed to analtyics but the user.segement was replaced by the reporting usergroup.

Note in the last two releases there are a couple bugs that need to be considered.  In 8.5.x the request parameter provider has to be used before the session provider.  And in 8.6 the 'user.segement' syntax is not working, only a single key name is working like 'segment' or 'usersegment'.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms