Restricting Visual Query conditions

By default, all the Visual Query operators are available for all the record types that support them in your system. To prevent the creation of queries that take too long to produce results, you can configure Visual Query to restrict the operators that are valid in conditions.

If you follow this procedure in a deployment that provides high availability, you must complete each step on every Liberty server in your environment before you move to the next step.
  1. Set the rules that you would like to make to your Visual Query conditions:
    1. Using an XML editor, open the visual-query-configuration.xml file.
      You can find this file in the following location: toolkit\configuration\fragments\opal-services\WEB-INF\classes.
    2. Using the supplied examples, add the rules that you would like to implement.
      Note: Ensure that you add the restrictions paying attention to the ordering as later rules will override earlier rules if applicable.
    3. Save your changes.
  2. Update the DiscoServerSettingsCommon.properties file to use your configuration rules.
    1. Using a text editor, open the DiscoServerSettingsCommon.properties file.
      You can find this file in the following location: toolkit\configuration\fragments\opal-services\WEB-INF\classes.
    2. Set the VisualQueryConfigurationResource
      For example: VisualQueryConfigurationResource=visual-query-configuration.xml
    3. Save your changes.
Redeploy i2 Analyze to update the application with your changes.
  1. In a command prompt, navigate to the toolkit\scripts directory.
  2. Stop Liberty:
    setup -t stopLiberty
  3. Update the i2 Analyze application:
    setup -t deployLiberty
  4. Start Liberty:
    setup -t startLiberty

Run a selection of Visual Queries that use conditions. Continue to change the configuration until you are satisfied with the Visual Query condition.