How to setup Test Profiles with user.segment for the rules' Business Condition in Test Drive (Doc ID 1439104.1)

Last updated on FEBRUARY 28, 2017

Applies to:

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

Goal

Test profiles can be used in test drive (a tool in the workbench) to simulate the values that are passed from Infocenter as parameters when the user asks a question for search.  During normal end user interaction these parameters are passed from Infocenter to the runtime as part of a search request and they describe the user.  The parameters influence the search results returned to the user. One of the most common parameters passed from Infocenter is the user.segment. User.segment is set by InfoCenter and is often related to the usergroups that the user belongs to.  Based on the user.segment value the rules in the dictionary (established when setting up the use of the user.segment variable) will control which content results the user is returned. While testing in test drive the way to set these values for a testing session is to use test profiles. Test profiles can also be used to set other values that can be passed as part of the search request from Infocenter or the CRM interface, like which application the request is coming from.  You can set any combination of parameters in a test profile to test the dictionary rule behavior in test drive.

The Goal for testdrive and profiles is to simulate the typical users that are found in infocenter for testing their results.  This can be a complicated process as not all users follow the same patterns and you will often see differences between infocenter and testdrive.  There are some helpful ways to debug this.  This debugging is part of the process of creating good profiles and matching them to infocenter users.  Please see these KMs to learn more about this debugging process.

Showing debug faceting or searchscore in InfoCenter or Iconnect User Interface (Doc ID 1393423.1)

My Content is Missing- Tips for Debugging when Results aren't Returning Expected Answers (Doc ID 1040309.1)

Solution

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