New features and changes in version 9.1.1

Ability to add or modify treatment rules with the Rule Wizard

You can use the Rule Wizard to add or modify multiple treatment rules at once. This new wizard steps you through the process of adding or modifying treatments rules. From the wizard, you can select offers and segments to be included in the rules you generate. You can also associate zones with each segment. You can also check the Syntax to validate any expressions for the rules through the wizard.

Predefined events available when event patterns are added

When you add an event pattern on the Interactive Channel, you can choose from predefined events when you define the events that must occur to fulfill your event pattern. The predefined events are offerAccepted, offerContacted, offerRejected, offerAcceptedInCategory, offerContactedInCategory, and offerRejectedInCategory.

If you add offerAccepted, offerContacted, or offerRejected, you are prompted to select an offer that triggers the macro. If you add offerAcceptedInCategory, offerContactedInCategory, or offerRejectedInCategory, you are prompted to set attribute values of the offers that triggered the macros. You can add each of these macros multiple times with different offers or offer attributes and values for each event pattern.

Exporting interactive channels

In Interact, you can export a previous interactive channel deployment version. When you export a deployment version, you can send this export to HCL® technical support to troubleshoot any problems with your deployment.

New Interact JavaScript API

Event Pattern report added

The Interact Event Pattern report shows you event pattern activity across interactive channels and their categories. You can use this report to analyze how personalized offers were presented to visitors through event patterns. You can also analyze how many event patterns are triggered to visitors in the interactive channels you report on.

The Event Pattern report uses the data that is contained in staging tables, which are populated by stored procedures. The stored procedures perform a delta refresh operation.

ETL report aggregation configuration

The Interact ETL has extra configuration options for report aggregation. These configuration options are used to aggregate the ETL data to provide pattern state activity that can be analyzed with the Event Pattern report.

The following configuration options are available for the ETL report aggregation process.

• Enable: Enable or disable the report integration with ETL.
• retryAttemptsIfAggregationRunning: The number of times the ETL attempts to check whether the report aggregation is completed if the lock flag is set.
• sleepBeforeRetryDurationInMinutes: Sleep time in minutes between consecutive attempts.
• aggregationRunningCheckSql: This property lets you define a custom SQL, which can be run to see whether the report aggregation lock flag is set.
• aggregationRunningCheck: Enable or disable the check if the report aggregation is running before the ETL run is performed. T

These configurations can be set in Interact | ETL | patternStateETL.

Configuration options for built-in learning

Interact now has extra built-in learning configuration options. You can set Version to 2 to set thread and record parameter to improve performance. These parameters perform the aggregation and deletion when these parameter limits are reached. autoAdjustPercentage can be used to set the percentage of data the run of aggregation tries to process based on the metrics of the previous run. excludeAbnormalAttribute can be used to determines whether to mark those attributes as invalid. If set to IncludeAttribute, abnormal attributes are included not marked as invalid. If set to ExcludeAttribute, abnormal attributes are excluded and marked as invalid. numberOfThreads, maxLogTimeSpanInMin, and maxRecords were added as parameters for the built-in learning configuration.

These configurations can be set in Interact | offerserving | Built-in Learning Config.

Configuration to catch the response events that do not have contacts

You can use the actionOnOrphan configuration to determine what to do with response events that do not have corresponding contact events. If set to NoAction, the response event is processed as if the corresponding contact event was posted. If set to Warning, the response event is processed as if the corresponding contact event was posted, but a warning message is written into interact.log. If set to Skip, the response even is not processed, and an error message is written into interact.log. The setting that you choose here is effective regardless if response history logging is enabled.

This configuration can be set in Interact | services | responseHist.

IBM ExperienceOne Knowledge Center

You can view common tasks, troubleshooting, and support documentation the same way you have in prior releases by using the Help menu in each product, including Help > Product documentation or Help > Help for this page. To get documentation on all other IBM products, use the IBM Knowledge Center at http://www.ibm.com/support/knowledgecenter/.