7 Oracle RTD Decision Studio Issues

This chapter provides release notes for Oracle RTD Decision Studio. It contains the following topics:

• Section 7.1, "Deploying an Inline Service from Decision Studio Causes a Null Pointer Exception in the WebLogic Log"

• Section 7.2, "Explicitly Defining Partitioning Attribute Values Causes Subsequent Decision Center Report Errors"

• Section 7.3, "Mapping Array Attributes in a Multi-Level Entity Hierarchy"

• Section 7.4, "Terminate Active Sessions in Cluster Works Only on Decision Server Receiving Deployment Request"

• Section 7.5, "Can Only Use String Datatype for Type Restrictions using List Of Values"

7.1 Deploying an Inline Service from Decision Studio Causes a Null Pointer Exception in the WebLogic Log

This issue applies to Version 3.0 and Version 3.0.0.1.

When Oracle RTD is running on WebLogic, when you deploy an Inline Service from Decision Studio, a null pointer exception appears in the WebLogic log. This error is harmless and can be ignored.

7.2 Explicitly Defining Partitioning Attribute Values Causes Subsequent Decision Center Report Errors

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.

Partitioned models can be defined with values explicitly named in the Value Domain field of a partitioning attribute, or that field can be left blank. If you specify explicit values for any model partitioning attribute in the Value Domain field, this causes problems for some Decision Center reports. For more information, see Section 8.1, "Multiple Rows Appearing for Some Reports Based on Partitioned Model Data."

The workaround for this issue is not to fill in the Value Domain field for any partitioning attribute.

7.3 Mapping Array Attributes in a Multi-Level Entity Hierarchy

This issue applies to Version 3.0 and Version 3.0.0.1.

A "parent-child" entity hierarchy is typically defined with the child entity as an attribute of the parent entity. When the child entity is an Array attribute, be careful to map the child Array attribute to its data source in the direct parent entity only. Assume, for example, a Customer with many Accounts, each of which has many Contracts. In Decision Studio, the Customer entity's Mapping tab may display the complete hierarchy as follows: - The Customer entity contains the Account entity as an Array attribute - The Account attribute contains the Contract entity as an Array attribute The Account entity's Mapping tab contains the Contract entity as an Array attribute.With this example, only map the Contract attribute in the Account entity's Mapping tab. Do not map the Contract attribute in the Customer entity's Mapping tab.

7.4 Terminate Active Sessions in Cluster Works Only on Decision Server Receiving Deployment Request

This issue applies to Version 3.0 and Version 3.0.0.1.

Deploying an Inline Service to a cluster with the "Terminate active sessions" option selected will terminate sessions on only the Decision Server that receives the Inline Service deployment request.

7.5 Can Only Use String Datatype for Type Restrictions using List Of Values

This issue applies to Version 3.0 and Version 3.0.0.1.

In Decision Studio, when creating a Type Restriction containing List Of Values, select only String for Data Type. Selecting other Data Types will result in compilation errors.

.