This chapter provides release notes for Oracle RTD Decision Studio. It contains the following topics:
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.
When importing a Table in Decision Studio, an Integer column may incorrectly be mapped as a Double column. This is due to a bug in the Oracle JDBC driver version 11.2.0.3. In order to fix this, replace the JDBC driver that your application server uses with version 11.2.0.4.
Caching on the set entity using a table data source works fine. But replacing the table data source with a procedural data source gives errors. A workaround may be to use a table data source on top of a view.
Importing a stored procedure from an Oracle database with a column of timestamp data type results in an error. To work around this, use a date data type.
The following choice model methods defined in ChoiceModelInterface do not work and should not be used:
public float getChoiceModelQuality(String choiceId)
public int getChoiceModelCount(ModelCount modelCount, String choiceId)
public float getChoiceModelLift(ModelLift modelLift, String choiceId)
public float getChoiceModelError(ModelError modelError, String choiceId)
When calling logInfo() from a function in your inline service, the log message may not appear in the log window in RTD Studio, but it does appear in the server logs. To work around this, look at the tail of the log file.
There are known issues, which may result in compilation and runtime errors, with enabling entity caching where a number of design factors coincide:
You have a multi-level entity hierarchy, and a child entity is an array attribute of a parent entity.
The data source for the child entity has no Input column defined.
You want to enable caching on the child entity.
If possible, simplify the structure of the child entity, specifically the attributes that are mapped to the sources. If this is not possible, contact Oracle Support with details of your particular design configuration.