HCL® Opportunity Detect 11.0.1 includes a new feature. This is listed underneath. It was added in version 11.0 and is carried forward to 11.0.1.

HCL® Opportunity Detect enables you to look for specified customer behaviors and patterns in your customer data. You define the transactions and patterns that Opportunity Detect looks for, and you specify the data that is written to the database or web servlet when those criteria are met.

The permissions assigned to users in Opportunity Detect determine what areas of the application they can access and the actions they can perform.

Opportunity Detect offers three data source connectors for processing transactions as soon as they are received.

To set up data sources for HCL® Opportunity Detect, you configure them in the user interface, including setting up connections to the databases that hold run detail, State History, and Outcome data.

You can create and run deployment configurations and view deployment and batch run history on the Workspaces page.

Opportunity Detect generates one outcome record for every set of transactions that meets the criteria specified in the trigger system.

The Queue data source connector allows Opportunity Detect to operate with a supported queue server.

You can use a Web Service Connector for incoming transaction data, for Outcome data, or for both.

Opportunity Detect provides a monitoring tool for deployments running on Streams.

The Opportunity Detect command line utility, RemoteControlCLI (CLI), allows you to automate the management of deployment configurations and batch runs. You can use the CLI to perform the same actions you can perform on the Deployment & Batch Run tab of a workspace.

Use the export/import utility to transfer Opportunity Detect workspace logic from one environment to another.

The conversion utility enables you to convert workspaces in Unica Detect format (that is, in versions earlier than 9.1.1) to Opportunity Detect format.

Some suggestions for resolving issues with Opportunity Detect are listed in this section, along with workarounds or solutions.

This section describes the Opportunity Detect and Interact Advanced Patterns configuration properties on the Configuration page.

HCL® Opportunity Detect enables you to look for specified customer behaviors and patterns in your customer data. You define the transactions and patterns that Opportunity Detect looks for, and you specify the data that is written to the database or web servlet when those criteria are met.

The permissions assigned to users in Opportunity Detect determine what areas of the application they can access and the actions they can perform.

You build trigger systems in workspaces. This procedure provides the basic steps for setting up workspaces. Details on adding and using components are provided elsewhere in this guide.

There are three ways to add components to workspaces: by creating a component from the Component Palette, by copying a component within a workspace, and by using a component reference to share a component across workspaces.

You can create and run deployment configurations and view deployment and batch run history on the Workspaces page.

Opportunity Detect generates one outcome record for every set of transactions that meets the criteria specified in the trigger system.

Components are the basic building blocks for trigger systems in Opportunity Detect.

You build expressions and configure incoming events and time spans when you work with several types of components. In addition, all component editors have a left panel where you configure or view basic attributes. Read this section to understand these commonly used component attributes.

The Expression Builder is used throughout Opportunity Detect to compare strings and numbers, perform math operations, and apply database functions.

In Opportunity Detect, you use regular expressions in two situations.

Expression components evaluate customer data and return a value that can be used by other components. You can create similar logic by using inline expressions within components, but creating an expression component for frequently used calculations allows you to re-use this logic.

Trigger systems in HCL® Opportunity Detect all have Simple components as their basic building block. Simple is the only component type that is triggered by incoming transactions in the transaction data feed, and not by an event produced by another component. This is why every trigger system requires at least one Simple component.

The purpose of an Action component is to send a notification that a specified behavior has occurred by writing data to a database or sending the data to a web service. Like all event components, an Action component fires and writes its outcome when it receives an incoming event from another event component.

Select components perform operations that are similar to the SQL SELECT database query with optional WHERE clauses. A Select component holds a set of records that you define, and on which you can perform further operations.

Container components store data that you define for a specified length of time. Container components depend on Container Manipulator components to feed them the data that they store.

You can use Pattern components to test whether one or more events for a given customer occur over a period of time. A Pattern component collects events that match its criteria and stores these events in the customer's state history. When the specified pattern of events is met, the pattern drops those events from state history and fires a positive event.

You use a Backward Inactivity component when you want to verify that some event did not occur within a specified period of time prior to an incoming event. You use a Forward Inactivity component to set a timer when it receives an incoming event, and optionally to specify another event that turns off the timer.

Trend components detect changes in activity measured over defined periods of time. Before you can create a trend component, your trigger system must include a Container or Select component that the trend can use as a data source.

An artificial transaction (ATX) is a system-generated event that you can use as an incoming event in an event component.

The integration between HCL® Interact and HCL Interact Advanced Patterns provides advanced pattern recognition capabilities for your Interact implementation.

An installation of Opportunity Detect or Interact Advanced Patterns is complete when you install, configure, and deploy the product.

When you plan your Opportunity Detect and Attribution Modeler installation, you must ensure that you have set up your system correctly, and that you have configured your environment to deal with any failures.

The Opportunity Detect runtime environment uses data sources to store user and interaction data.

You must run the HCL® Marketing Software installer to start the installation of Opportunity Detect. The HCL Marketing Software installer starts the Opportunity Detect installer during the installation process. Make sure that the HCL Marketing Software installer and the product installer are saved at the same location.

If you select manual database set up when you install Opportunity Detect, you must complete the tasks in this section after you run the HCL® Marketing Software and the Opportunity Detect installer.

To deploy Opportunity Detect, you must deploy Opportunity Detect Design Time using an EAR or WAR file.

After you deploy Opportunity Detect, perform the additional configuration tasks described in this chapter.

Opportunity Detect can be installed and deployed in a cluster.

Run the Opportunity Detect and Attribution Modeler uninstallers to uninstall Opportunity Detect. When you run the Opportunity Detect uninstaller, the files that were created during the installation process are removed. For example, files such as configuration files, installer registry information, and user data are removed from the computer.

The properties and values on the Configuration page are stored in the Marketing Platform system tables. You can use the configTool utility to import and export configuration settings to and from the system tables.

This section describes the Opportunity Detect and Interact Advanced Patterns configuration properties on the Configuration page.

An upgrade of Opportunity Detect is complete when you upgrade, configure, and deployupgrade and configure Opportunity Detect. The Opportunity Detect Upgrade Guide provides detailed information about upgrading, configuring, and deployingupgrading and configuring Opportunity Detect.

You can upgrade your current version of Opportunity Detect to bring it up-to-date with the latest features.

Perform these steps before you run the upgrade installer.

Automatic migration allows the installer to run the SQL scripts and insert the configuration properties that are required to upgrade your Marketing Platform system tables. If your company policy does not allow automated updates to your system table database, you must use manual migration, described elsewhere in this guide.

The Opportunity Detect upgrade installer can perform all of the data migration that is required for an upgrade automatically. However, if the policy of your organization does not allow automatic migration, you must complete the migration procedure to upgrade Opportunity Detect manually.

To deploy Opportunity Detect, you must deploy Opportunity Detect Design Time using an EAR or WAR file.

After you deploy Opportunity Detect, perform the additional configuration tasks described in this chapter.

Run the Opportunity Detect and Attribution Modeler uninstallers to uninstall Opportunity Detect. When you run the Opportunity Detect uninstaller, the files that were created during the installation process are removed. For example, files such as configuration files, installer registry information, and user data are removed from the computer.

The properties and values on the Configuration page are stored in the Marketing Platform system tables. You can use the configTool utility to import and export configuration settings to and from the system tables.

This section describes the Opportunity Detect and Interact Advanced Patterns configuration properties on the Configuration page.

HCL Marketing Software provides GDPR support for the following Marketing Software products: