Info Only Fields with Default Values on Search Page Are Not Included in Search Query (Doc ID 2016875.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

Oracle WebCenter Content - Version 11.1.1.8.0 and later
Information in this document applies to any platform.

Symptoms

If you have a rule that sets some fields to Info Only with default values, and you go to the Profile Search page that uses that rule, those fields and their values are not included in the search query.

If the rules are set to be Edit or Hidden fields (with default values) rather than Info Only, the fields and their values are then included in the search query.

To reproduce the issue:

  1. Create a rule that sets a field to be Info Only with a default value.

    Example:

    dDocType set to Info Only with <$dprDefaultValue="Binary"$>

  2. Create a profile that uses this Rule.

  3. Turn on this tracing at Full Verbose:

    system, requestaudit, systemdatabase, search*

  4. Go to the Profile Search page, and verify that the field is set to Info Only with a default value.  Run the search.

  5. Check the server output for the search query.  You will see that it doesn't include the field or the default value.

  6. Change the field to be Hidden and rerun the search from the Profile Search page.

  7. Check the server output for the search query.  You will see that it now does include the field or the default value.

 

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