Oracle® Real-Time Decisions Release Notes Versions 3.0 and 3.0.0.1 Part Number E13857-09 |
|
|
View PDF |
This chapter provides release notes for Oracle RTD Decision Center. It contains the following topic:
This issue applies to Version 3.0 and Version 3.0.0.1.
When an Oracle RTD model is defined with partitions, then at run-time, when each new partitioning attribute value is presented to the learning process, Oracle RTD automatically creates a new partition in the model.
When any partitioning attribute in a model has one or more explicitly defined values in its Value Domain in the Inline Service, this causes the following problems in Decision Center reports that can filter on the partitioning attributes of that model:
The partitioning attribute does not appear among the filtering parameters in the report header, so users cannot select a particular attribute value to filter on
Multiple rows appear for other input attributes, instead of one per attribute
Note:
This problem does not arise if values are not explicitly defined for a partitioning attribute in the Inline Service model. In this case, Decision Center reports display the partitioning attribute field in the report header, enabling users to select a value from the field's drop-down list.The image that follows shows an example of this issue, as applied to the Inline Service CrossSellwithpartition, and to a subsequent Decision Center report. In the Inline Service, the partitioning attribute Session/Channel for the Offer Acceptance model has two explicitly defined attribute values, "Call" and "Web", in its Value Domain.
Assuming both of the attribute values, "Call" and "Web", have been passed to the model learning process, the effects of the explicit attribute definition are shown on an Analysis Drivers report in the Decision Center, as follows:
The filter parameter fields in the report header should include the field "Channel", but that field is not present in the report header
In the report body, two rows appear for each of the customer attributes Age, Amount of Pending Transactions, AvailableCreditAsPercentOfCreditLine, and CallReason
The workaround for this issue is not to fill in the Value Domain field for any partitioning attribute in the Inline Service.
This issue applies to Version 3.0 and Version 3.0.0.1
For Choice Group Performance Count reports, rollup does not apply to the dynamic choice folder names, whose format is <dynamic_choice_1>...<dynamic_choice_2>.