Known issues

This section describes the known issues in the 9.1.2 version of Opportunity Detect.

The database password is not updated when you install Interact Advanced Patterns over Opportunity Detect Defect 177556 If you install Interact Advanced Patterns over Opportunity Detect, and you select the manual option, you must manually update the password attribute of the properties tag in the server.xml file. This file is located in the InteractService/wlp/usr/servers/InteractService directory under your Opportunity Detect installation.

You can use the securityUtility located under the InteractService/wlp/bin directory under your Opportunity Detect installation to encrypt the password. For example:

./securityUtility encode your_password

An error occurs when referenced Container components in the same workspace have the same name Defect 178235 When you are building triggers, it is a common practice to copy component references from multiple test workspaces into the same production workspace. If two Container components from two different workspaces have the same name, the Streams log shows the following error, and Outcomes are produced for only one of the Containers.

The table definition already exists: Container

To avoid this issue, give your Container components names that are unique across all workspaces.
When you use the Internet Explorer browser you can not add output functions on Select fields used in a Container component Defect 178313 When you use the Internet Explorer browser to work with a Container component that uses fields from a Select component, when you try to apply a function that changes the output data type, the page refreshes intermittently and you can not select a function on any field. The drop down select box is not available and there are no values in the field. The workaround is to use the Chrome browser, where this issue does not occur.
The Action component does not fire for some workspaces when the Outcome is mapped to a Web Service connector Defect 198305 When the Outcome data source is mapped to the Web Service connector, and if the trigger system contains only one Action component that is listening for a Forward Looking or negative Pattern component, no outcome message is sent. In this case, you need a second Action component that is listening for another type of component; then all outcome messages will be sent.
The XML file for the command line utility is not updated when the Run Time component is installed on a different machine from the Design Time component Defect 199632 When you do not install the Run Time component on the same machine as the Design Time component, the RemoteControlCLI.xml file is not updated with the host and port of the Streams Remote Control service. This file must be configured if you want to use the RemoteControlCLI utility.

To work around this issue, update the file manually to replace [RCS_SERVER] and [RCS_PORT] with the host and port of the Streams Remote Control Service.

The RemoteControlCLI.xml file is located in the clidirectory under your Opportunity Detect design time installation.