2 Dynamic Choices

This chapter describes Dynamic Choices, as implemented in Oracle Real-Time Decisions (Oracle RTD), Version 2.2.1. It contains the following topics:

• Section 2.1, "Dynamic Choices Overview"

• Section 2.2, "Simple Example of Dynamic Choices"

• Section 2.3, "Multiple Category Dynamic Choices from a Single Data Source"

• Section 2.4, "Prerequisite External Data Source"

• Section 2.5, "Setting up Dynamic Choices in Oracle RTD Decision Studio"

• Section 2.6, "Dynamic Choice Reporting in the Decision Center"

2.1 Dynamic Choices Overview

In Oracle RTD, Choices represent the universe of alternatives, from which Oracle RTD can select its recommendations, such as the best offer in a cross selling application.

In previous releases of Oracle RTD, the only type of Choices available were Static Choices, where the Choice values to present to the requesting application or self-learning model were completely defined within Oracle RTD.

Static Choices are useful in cases where the number and values of the Choice options are known in advance, and are constant over a period of time.

In version Oracle RTD Version 2.2.1, Choices can now be either Static or Dynamic.

Dynamic Choices take their values from data retrieved from external Data Sources, typically database tables or views. This allows for the management of Choices to be done at the source system, such as Choices based on offers defined in an offer management system.

Each time a Dynamic Choice needs to be evaluated by Oracle RTD, the data is retrieved from the external Data Source or Sources. Therefore, the Choices to be presented to an application may vary over time, but always reflect the up-to-date state of the application data. They are not restricted to predefined, static values, changes to which would require a redeployment of the Oracle RTD Inline Service.

Note: While this section focuses on Dynamic Choices, in Oracle RTD Version 2.2.1, a Choice Group can contain a combination of Static and Dynamic Choices. A Decision, as in previous releases, can be associated with one or more Choice Groups, no matter what types of Choice they contain.

2.2 Simple Example of Dynamic Choices

As a simple example, take the case of an Insurance_Proposals table, as shown in Figure 2-1. This table contains rows for different insurance products, as identified by the common value InsuranceProducts in the ChoiceGroupId column. The column that categorizes or groups the Dynamic Choices is an important required key identifier for setting up Dynamic Choices.

Each row in the group shows a different type of insurance product being offered, such as AutoInsurance, and DisabilityInsurance. Each row represents a Dynamic Choice.

One column serves to identify the particular Dynamic Choice within the group. In this example, the ChoiceID column is the Dynamic Choice identifier column.

Other columns in the table, such as ProfitMargin, can be used by Oracle RTD in the evaluation process. These columns can also be sent back to the application as part of the Dynamic Choice recommendation, as a value for a defined Choice attribute.

Figure 2-1 Insurance Products in the Insurance_Proposals Table

In short, the setup process is that, in Oracle RTD, you set up a Choice Group for Dynamic Choices, and associate this Choice Group with the required external Data Source or Sources. The Dynamic Choices are then available to be recommended by Oracle RTD.

After sufficient recommendations have been made and models have been updated for the corresponding Choice Group, you can analyze the performance of the various Dynamic Choices through the Oracle RTD Decision Center, as shown in Figure 2-2.

Figure 2-2 Decision Center Analysis of Dynamically Chosen Insurance Products

2.2.1 Basic Dynamic Choice Design Implications

The basic design process for Dynamic Choices is similar to that for Static Choices. You must first set up a Choice Group, then define the required elements and parameters for Dynamic Choices in the Choice Group. For more detailed information on how to perform the setups, see Section 2.5, "Setting up Dynamic Choices in Oracle RTD Decision Studio."

Using the Insurance_Proposals example, this section acts as an overview of the design process. It also introduces key terms used in the design process, as follows:

• The set of all the Dynamic Choices is identified as all the rows that have a common value in a "grouping" or categorizing column. In the Insurance_Proposals example, the categorizing column (or set identifier) is the ChoiceGroupId column.

• Each row in the database set represents a single Dynamic Choice. In the Insurance_Proposals example, the Dynamic Choice itself is identified by the unique value in the ChoiceId column.

• When you define the Choice Group for Dynamic Choices in Oracle RTD, you must link the Group to the set of rows that contain the Dynamic Choices.

• When you define the Dynamic Choices in the Choice Group in Oracle RTD, you must link each Dynamic Choice in the Group to the corresponding single Dynamic Choice row in the Data Source.

2.3 Multiple Category Dynamic Choices from a Single Data Source

In the simplest Dynamic Choice case, all the rows of the database table belong to the same category, that is, have the same value in a categorizing column.

You can provide different Dynamic Choices from either the same database table or a variety of data sources. The following example, as illustrated in Figure 2-3, shows the case where the Insurance_Proposals table is extended to provide Choices for both Insurance Products and Insurance Services.

Figure 2-3 Insurance Products and Insurance Services in the Insurance_Proposals Table

For this situation, you set up two Choice Groups in Oracle RTD, making both sets of data available for recommendations in the application.

After sufficient recommendations have been made and models have been updated for the corresponding Choice Group, you can analyze the performance of either or both of the Insurance Products and Insurance Services Dynamic Choices.

For example, the Choice Groups could have been set up as two groups in a group hierarchy, and available for analysis in the Oracle RTD Decision Center as shown in Figure 2-4.

Figure 2-4 Choice Groups in the Decision Center

Analyzing the Insurance Products provides the same results as shown in Figure 2-2. Figure 2-5 shows an equivalent analysis report for Insurance Services.

Figure 2-5 Decision Center Analysis of Dynamically Chosen Insurance Services

2.3.1 Considerations for Different Dynamic Choice Categories in the Same Data Source

For each real-world category, you must set up a separate Choice Group, usually, but not necessarily, in a Choice Group hierarchy.

The design considerations for and components of each Choice Group are the same as described in Section 2.2.1, "Basic Dynamic Choice Design Implications."

For general information on how to set up Choice Groups, see Section 2.5, "Setting up Dynamic Choices in Oracle RTD Decision Studio."

For specific information on how to set up different Choice Groups from the same Data Source, see Section 2.5.7, "Creating a Multi-Category Choice Group."

2.4 Prerequisite External Data Source

The data required for Dynamic Choices exists in an external Data Source.

For the sake of simplicity, the following description assumes that the external Data Source is a database table or view in the calling application.

To be useful for Dynamic Choices, the data must include:

• One column to be used for categorizing and extracting the data.

  For a single Dynamic Choice, the rows to be extracted will all have the same value in the categorizing column, and this column is used to control the extraction.

  For example:

  • The database table Special_Events has a column Event_Type.

  • There are three distinct values of Event_Type across all the rows, namely Promotion, Product_Launch, and Mailshot.

  In this example, Event_Type is the categorizing column, and for a single Dynamic Choice, Oracle RTD will extract all the rows of one event type, such as all the Promotion rows.

• One column that uniquely identifies the rows extracted for a particular Dynamic Choice.

  The column does not need to have unique values across all the rows, just within the extracted data set.

  Any column that provides a unique identifier within the extracted data is sufficient. Oracle recommends that the column values include some textual component. These values appear as headers for some Oracle RTD Decision Center reports, and an identifier that is meaningful in the real world sense is more useful than a strictly numeric identifier.

Figure 2-6 is an example of a database table Web Offers, that could be used as the external data source for a Dynamic Choice data source. This table is not released with Oracle RTD.

Figure 2-6 Example of an External DatabaseTable

The table illustrates the following features:

• The categorizing column is Category, and the common value in all the Category columns is DynamicOffersCG.

• You could select either Name or ID as the Dynamic Choice identifier column for the DynamicOffersCG category.

2.5 Setting up Dynamic Choices in Oracle RTD Decision Studio

This section consists of the following topics:

• Section 2.5.1, "Creating the Dynamic Choice Data Source"

• Section 2.5.2, "Creating the Single Dynamic Choice Entity"

• Section 2.5.3, "Creating the Dynamic Choice Set Entity"

• Section 2.5.4, "Creating the Dynamic Choice Data Retrieval Function"

• Section 2.5.5, "Considerations for Choice Group Design"

• Section 2.5.6, "Creating a Single Category Choice Group"

• Section 2.5.7, "Creating a Multi-Category Choice Group"

Figure 2-7 shows an overview of setting up a simple, single category Choice Group for Dynamic Choices. The elements in the diagram are referred to in the more detailed process descriptions that appear later in this section.

Figure 2-7 Overview of Setup Process for Single Category Dynamic Choices

Note: The diagrams and Oracle RTD Decision Studio screenshots illustrating the setup process, which appear later in this section, are based on the DC_Demo Inline Service that is released with Oracle RTD Version 2.2.1.

2.5.1 Creating the Dynamic Choice Data Source

To create the Dynamic Choice Data Source:

1. Create a new Data Source that maps to the table described in Section 2.4, "Prerequisite External Data Source," using the Import button to point to the external data source.

2. In the Output column area, check Allow multiple rows, and select all the columns that you require for a Dynamic Choice.

   In the Input column area, select the column that contains the common value that categorizes and groups the Dynamic Choice rows.

Note: You do not have to select the Dynamic Choice identifier column from among the Output columns at this stage.

Figure 2-8 shows how the Data Source Web Offers DS is set up from the table SDDS.WEBOFFERS, with Category as the Input identifier, and a number of other columns that represent attributes of the Dynamic Choice itself.

Figure 2-8 Defining the Web Offers DS Data Source

2.5.2 Creating the Single Dynamic Choice Entity

The Dynamic Choice data exists in the Data Source. You must create a Single Dynamic Choice Entity in Oracle RTD that consists of all the information associated with a particular category, but not the category itself.

In terms of the Data Source that you created, the Entity attributes for the Single Dynamic Choice Entity are the Output attributes of the Data Source.

To create the Single Dynamic Choice Entity:

1. Create an Entity for the Dynamic Choice data, using the Import functionality to bring in all the Output columns from the Data Source described in Section 2.4, "Prerequisite External Data Source."

2. When selecting the Data Source, be sure to uncheck the Build data mappings for the selected data source option found in the Select window that appears when you import.

Figure 2-9 shows the Definition tab for the setup of the Single Dynamic Choice Entity Web Offers. The attributes are the Output columns of the Data Source Web Offers DS.

Figure 2-9 Defining the Web Offers Entity

2.5.3 Creating the Dynamic Choice Set Entity

In addition to the Single Dynamic Choice Entity, you must create a Dynamic Choice Set Entity, that includes the following Attributes:

• A Key Attribute, which is the input, categorizing column of the Data Source that contains the Dynamic Choice data

• An array Attribute that stores the Single Dynamic Choice Entity data

  This array Attribute must be of the same Entity type as the Entity that you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity." This array is the container for all the Attributes of the data to be extracted from the Data Source required for the Dynamic Choice except for the categorizing Attribute.

To create the Dynamic Choice Set Entity:

1. Create an Entity in Oracle RTD.

2. For the key Attribute, click Add Key, and select the Dynamic Choice categorizing Attribute from the Data Source.

3. Create an Attribute whose type is the name of the Entity created in Section 2.5.2, "Creating the Single Dynamic Choice Entity."

4. Mark this entity-type Attribute as an Array.

   Figure 2-10 shows the Definition tab for the setup of the Dynamic Choice Set Entity Web Offers List. The Key Attribute is the Input column Category of the Data Source Web Offers DS, and the second Attribute is an array Attribute of type Web Offers.

   Figure 2-10 Defining the Dynamic Choice Set Entity Web Offers List

   
   

5. Click the Mapping tab, and map each Attribute within the entity-type Attribute to the appropriate column in the original Data Source.

6. In the Data Source Input Values region, for the Input Value of the Data Source, select the Dynamic Choice categorizing Attribute that you created in step 2.

   Figure 2-11 shows the Mapping tab for the setup of the Dynamic Choice Set Entity Web Offers List. Each of the Attributes within the array Attribute is mapped to the corresponding column in the Web Offers DS Data Source. In the Data Source Input Values region, the Attribute selected for the Input Value is the key Attribute Category.

   Figure 2-11 Mapping the Web Offers Attributes in the Web Offers List Entity

   
   

7. Click the Cache tab.

8. Select the check box to Enable caching for this entity type.

   
   

   Note: It is important to enable caching on the Dynamic Choice Set Entity. Enabling caching will keep the Oracle RTD Decision Server from repeatedly pulling the Dynamic Choices from the data source with each new session.

   
   

2.5.4 Creating the Dynamic Choice Data Retrieval Function

To extract the Dynamic Choice data from the database, you must create a Function that will perform the data retrieval. This function will be called by the Choice Group that you will create in the steps that follow. The properties of the Function are as follows:

• The Function returns a value.

• The return value is of type Array.

• The Data Type of the array elements is the Single Dynamic Choice entity that you created previously

• The Function has a Parameter that is the same as the Data Source Input Value of the Dynamic Choice Set Entity that you created previously.

• The logic of the Function instantiates a new occurrence of the Dynamic Choice Set Entity, and uses the Parameter to retrieve the Dynamic Choice data into the array.

To create the Dynamic Choice Data Retrieval Function:

1. Create the Function, and select the Return value check box.

2. Select the Array option, to ensure that the return value is of type Array.

3. For the Data Type, select the name of the entity that you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity."

4. In the Parameters area, add the Name and Type of the Key attribute that you created in step 2 of Section 2.5.3, "Creating the Dynamic Choice Set Entity."

5. In the Logic field, enter code similar to the following, adapting it as required for the names of your entities and attributes:

   WebOffersList list = new WebOffersList();
   list.setCategory(category);
   return list.getWebOffers();
   

   where:

   • WebOffersList is the object name, with internal spaces deleted, for the Entity created in Section 2.5.3, "Creating the Dynamic Choice Set Entity."

   • list.setCategory references the Entity key that you created in Section 2.5.3, "Creating the Dynamic Choice Set Entity," step 2.

   • getWebOffers() refers to the Entity created in Section 2.5.2, "Creating the Single Dynamic Choice Entity," that is mapped inside the Dynamic Choice Set Entity.

     Figure 2-12 shows the definition of the GetWebOffers Function.

     Figure 2-12 Defining the GetWebOffers Function

     
     

2.5.5 Considerations for Choice Group Design

Dynamic Choices enable application data administrators to control the choices that Oracle RTD recommends to the application. Unlike Static Choices, Dynamic Choices may be added, edited, and deleted in the application tables without requiring any changes in the interfacing Oracle RTD Inline Service.

If there is a requirement to have both type of Choice in a single Inline Service, Oracle recommends that Static Choices and Dynamic Choices are clearly separated in the designing of the Choice Groups. This section concentrates on the design of Choice Groups for Dynamic Choices.

The main real world conditions that affect the design of Choice Groups for Dynamic Choices are:

• Single Dynamic Choice Category in a database table

• Multiple Dynamic Choice Categories in a database table

Single Choice Group

Where there is a single Dynamic Choice category in a database table (such as Promotion in a Special_Events table), then the recommended design strategy is:

1. Design a single Choice Group.

2. Enter and select the required parameters in each of the following tabs for the Choice Group: Group Attributes tab, Choice Attributes tab, Dynamic Choices tab.

In Oracle RTD Decision Studio, this Choice Group has no subgroups.

Choice Group Hierarchy

For multiple categories in a database table (such as Insurance Products and Insurance Services in an Insurance_Proposals table), design a Choice Group hierarchy. Typically, all that is required is a two-level hierarchy, as follows:

1. For the top-level Choice Group, enter and select the required parameters in the Choice Attributes tab, but not the Group Attributes tab, nor the Dynamic Choices tab.

2. For each separate Dynamic Choice category, specify one lower-level Choice Group. In each of the lower-level Choice Groups, enter and select the required parameters in the Group Attributes tab and the Dynamic Choices tab, but not in the Choice Attributes tab.

Note: You only need to fill in Dynamic Choices tab parameters in the lowest-level Choice Groups of a multi-level Choice Group hierarchy.

In Oracle RTD Decision Studio, the lower-level Choice Groups have no subgroups.

2.5.6 Creating a Single Category Choice Group

To use Dynamic Choices, you must create one or more Choice Groups. Where the Dynamic Choices refer to data that belongs to one type or category, create a single category Choice Group.

Note: In Oracle RTD Decision Studio, when you create a Choice Group for Dynamic Choices, the individual Dynamic Choices do not appear in any of the RTD Decision Studio windows. In Oracle RTD Decision Center reports, you can see all the Dynamic Choices which satisfy the following conditions: They have been returned by Decisions called by the front-end applications. They have had RTD models updated for those Choices.

In Oracle RTD Decision Studio, the Choice Group is configured to be able to extract the Choices dynamically at runtime through options that you set up in the following tabs:

• Group Attributes tab

• Choice Attributes tab

• Dynamic Choices tab

These are the main tabs where you configure Dynamic Choices.

Note: You can also use the Choice Eligibility tab, to filter the Dynamic Choice data as it is extracted from the Data Source. Eligibility rules created for a Dynamic Choice are shared across all Choices retrieved for the same Dynamic Choice Group.

Figure 2-13 shows an example of the main elements required to set up a single category Choice Group, Dynamic Offers.

The Group Attribute setup indicates that all the data to be retrieved for the Dynamic Choices will be of one category only, and you must specify the exact category here.

The Choice Attribute setup describes the individual attributes that will be retrieved.

The Group and Choice Attributes are then referenced in the Dynamic Choices tab for this single category Choice Group.

Figure 2-13 Defining the Choice Group Dynamic Offers

2.5.6.1 Group Attributes Tab

In the Group Attributes tab, you specify an array Attribute of the same Entity type as that which you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity." This Attribute is referred to as the Dynamic Choice Array Entity in Figure 2-7, which shows an overview of the single category Dynamic Choice setup process.

At this level, you also specify the Function that retrieves the Dynamic Choice data. You must choose a value for the Function parameter. This enables the function to retrieve just the Dynamic Choice data relevant for one particular real world type or category.

To create a Choice Group and specify the Group Attributes:

1. Create a Choice Group.

2. Click the Group Attributes tab.

3. Create a new entity-type Group Attribute (the Dynamic Choice Array entity), whose type is the name of the entity that you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity."

4. Specify that this Attribute is an Array.

5. Click the right-hand end of the Value box to expose the ellipsis (...) button, then click the ellipsis button to open the Value window.

6. In the Value window, select the option Value for array as a whole.

7. For Value Source, select Function or rule call, then select the Function that you created in Section 2.5.4, "Creating the Dynamic Choice Data Retrieval Function."

8. In the Parameters area, choose the Value of the parameter that will retrieve the corresponding rows in the Data Source whose Input Attribute contains that value.

   
   

   Note: This string Value is the exact value in the database that categorizes all the Dynamic Choice rows for a Choice Group. For example, for a Choice Group set up for the Insurance_Proposals table as described in Section 2.2, "Simple Example of Dynamic Choices," the Value is InsuranceProducts.

   
   

   Figure 2-14 shows the Group Attributes tab for the Choice Group Dynamic Offers. The Function to call is GetWebOffers. The Value in the Parameters area is the string DynamicOffersCG.

Figure 2-14 Defining the Group Attributes for the Choice Group Dynamic Offers

2.5.6.2 Choice Attributes Tab

In the Choice Attributes tab, you must:

• Specify an entity-type Attribute of the same type as the Entity that you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity."

  This Attribute is referred to as the Dynamic Choice Row entity in Figure 2-7, which shows an overview of the single category Dynamic Choice setup process.

• For each of the component attributes within this Dynamic Choice Row Entity, create a separate Choice Attribute, which you must then map to the corresponding attribute within the Dynamic Choice Row entity that you just created.

To specify the Choice Attributes of the Choice Group:

1. Click the Choice Attributes tab.

2. Create a new entity-type Attribute (the Dynamic Choice Row entity), whose type is the name of the entity that you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity."

3. Ensure that the Array check box is not selected.

4. For each attribute of the new Dynamic Choice Row entity, create a corresponding Choice Attribute.

5. For each Choice Attribute created in the previous step, map its Value to the corresponding attribute within the Dynamic Choice Row entity that you created in step 2.

   Figure 2-15 shows the Choice Attributes tab for the Choice Group Dynamic Offers. The Choice Attributes are the following:

   • One Dynamic Choice Row Entity Web Offer Entity

   • Several other Attributes, each of whose Values derives from the corresponding Attribute of the Dynamic Choice Row Entity Web Offer Entity

Figure 2-15 Defining the Choice Attributes for the Choice Group Dynamic Offers

2.5.6.3 Dynamic Choices Tab

In the Dynamic Choices tab, you provide the following information:

• You explicitly select this Choice Group to be for Dynamic Choices.

• You specify the Group and Choice Attributes that you set up in the corresponding Group Attributes and Choice Attributes tabs.

• You select the Attribute that identifies each Dynamic Choice.

• You describe how you wish the Dynamic Choices to appear in Oracle RTD Decision Center reports. Because the number of Dynamic Choices could be considerable, you can choose to break up a potentially long list of Dynamic Choices into smaller units or "folders", and you indicate how you want the data grouped in the folders.

To specify the Dynamic Choice parameters:

1. Click the Dynamic Choices tab.

2. Select the check box option to Use Dynamic Choices for this Choice Group.

3. For the Group attribute containing the list of Entities for choices, select the Dynamic Choice Array attribute that you created in Section 2.5.6.1, "Group Attributes Tab."

4. For the Choice attribute to assign the entity data, select the Dynamic Choice Row attribute that you created in Section 2.5.6.2, "Choice Attributes Tab."

5. For the Entity attribute that contains the choices id, select the Attribute that serves as the unique identifier for each of the extracted Dynamic Choice rows.

6. For the Distribution mode for choices over choice group folders, select Spill or Even.

   
   

   Note: For more information about this parameter, and the parameter in the following step, see Section 2.6.2, "Distribution of Choices Across Decision Center Folders."

   
   

7. Select the Maximum number of choices within one choice group folder on decision center.

Figure 2-16 Defining the Dynamic Choice Parameters for the Choice Group

2.5.7 Creating a Multi-Category Choice Group

To use Dynamic Choices, you must create one or more Choice Groups. Where you want to be able to select different groups of data from the same data source, create a multi-category Choice Group. This section describes the standard way to set up a multi-category Choice Group.

Note: In Oracle RTD Decision Studio, when you create a Choice Group for Dynamic Choices, the individual Dynamic Choices do not appear. In Oracle RTD Decision Center reports, you can see all the Dynamic Choices that have been returned by Decisions to calling applications.

In RTD Decision Studio, a Choice Group is configured to be able to extract the Choices dynamically at run time through options that you set up in the following tabs:

• Group Attributes tab

• Choice Attributes tab

• Dynamic Choices tab

These are the main tabs where you configure Dynamic Choices.

Note: You can also use the Choice Eligibility tab, to filter the Dynamic Choice data as it is extracted from the data source. Eligibility rules created for a Dynamic Choice are shared across all Choices retrieved for the same Dynamic Choice Group.

To allow for multiple Dynamic Choice categories, you must create a hierarchy of Choice Groups, and set up the Choice Group elements at different levels.

Figure 2-17 shows an example of the main elements required to set up a two-category Choice Group, Incentive Choices.

The Choice Group Incentive Choices is the parent Choice Group, with two child Choice Groups, Discounts and Gifts.

You specify the Choice Attributes at the top level, in the parent Choice Group. These Choice Attributes are then inherited by the two child Choice Groups.

Note: In the parent Choice Group, or in any higher level Groups of a multi-level Choice Group hierarchy, you do not enter or select any values in the Dynamic Choices tab. Dynamic Choice parameters are only specified in the lowest level Group of any Choice Group hierarchy.

Each child Choice Group enables a different category set of data to be retrieved, through the Group Attributes setup. The Group and Choice Attributes are then referenced in the Dynamic Choices tab for both of the child Choice Groups.

To compare this process with the equivalent single category Choice Group setup, see Figure 2-7.

Figure 2-17 Example of Defining a Choice Group Hierarchy

2.5.7.1 Choice Attributes Tab in the Parent Choice Group

In the Choice Attributes tab, you specify an entity-type Choice Attribute of the same type as that which you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity."

This Choice Attribute is also known as the Dynamic Choice Row Entity, as in the equivalent single category Dynamic Choice setup process shown in Figure 2-7.

For each of the attributes within this Dynamic Choice Row entity, create a separate Choice Attribute, which you must map to the corresponding attribute in the Dynamic Choice Row entity that you just created.

To create the Parent Choice Group and Choice Attributes:

1. Create the parent Choice Group.

2. Click the Choice Attributes tab.

3. Create a new entity-type Choice Attribute, whose type is the name of the entity that you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity."

4. Ensure that you do not specify that this is an Array.

5. For each of the attributes of the new entity-type Choice Attribute, create a corresponding Choice Attribute.

6. For each of the attributes created in the previous step, map its Value to the corresponding attribute within the Choice Attribute that you created in step 3.

2.5.7.2 Group Attributes Tab in the Child Choice Groups

For each child Choice Group, in the Group Attributes tab, you specify an entity-type array Attribute of the same type as that which you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity."

This Group Attribute is also known as the Dynamic Choice Array Entity, as in the equivalent single category Dynamic Choice setup process shown in Figure 2-7.

At this level, you also specify the function that retrieves the Dynamic Choice data. You must choose a value for the Function parameter. This enables the Function to retrieve just the Dynamic Choice data relevant for one particular real world type or category.

First, you need to create the child Choice Groups under the previously created parent Choice Group, then enter the required elements in the Group Attributes tab.

To create the Child Choice Groups and Group Attributes:

1. Create the first child Choice Group.

2. Create extra child Choice Groups as required, one for each separate Dynamic Choice category.

   Within each child Choice Group, you must now set up the required elements and parameters in the Group Attributes tab and the Dynamic Choices tab.

   The steps following in this section describe the actions required in the Group Attributes tab for each child Choice Group. Section 2.5.7.3 describes the actions required in the Dynamic Choices tab for each child Choice Group.

3. Click the Group Attributes tab of the child Choice Group.

4. Create a new entity-type Group Attribute, whose type is the name of the Entity that you created in Section 2.5.2, "Creating the Single Dynamic Choice Entity."

5. Specify that this Attribute is an Array.

6. Click the right-hand end of the Value box to expose the ellipsis (...) button, then click the ellipsis button to open the Value window.

7. In the Value window, select the option Value for array as a whole.

8. For Value Source, select Function or rule call, then select the Function that you created in Section 2.5.4, "Creating the Dynamic Choice Data Retrieval Function."

9. In the Parameters area, choose the Value of the parameter that will retrieve the corresponding rows in the Data Source whose Input attribute contains that value.

2.5.7.3 Dynamic Choices Tab in the Child Choice Groups

For each child Choice Group, in the Dynamic Choices tab, you must provide the following information:

• You explicitly select this Choice Group to be a Choice Group for Dynamic Choices.

• You specify the Group and Choice Attributes that you set up in the corresponding Group Attributes and Choice Attributes tabs.

• You select the Attribute that identifies each Dynamic Choice.

• You describe how you wish the Dynamic Choices to appear in Oracle RTD Decision Center reports. Because the number of Dynamic Choices could be considerable, you can choose to break up a potentially long list of Dynamic Choices into smaller units or "folders", and you indicate how you want the data grouped in the folders.

To specify the Dynamic Choice parameters:

1. Click the Dynamic Choices tab.

2. Select the check box option to Use Dynamic Choices for this Choice Group.

3. For the Group attribute containing the list of Entities for choices, select the attribute that you created in Section 2.5.7.2, "Group Attributes Tab in the Child Choice Groups."

4. For the Choice attribute to assign the entity data select the attribute that you created in Section 2.5.7.1, "Choice Attributes Tab in the Parent Choice Group."

5. For the Entity attribute that contains the choices id, select the Attribute that serves as the unique identifier for each of the extracted Dynamic Choice rows.

6. For the Distribution mode for choices over choice group folders, select Spill or Even.

   
   

   Note: For more information about this parameter, and the parameter in the following step, see Section 2.6.2, "Distribution of Choices Across Decision Center Folders."

   
   

7. Select the Maximum number of choices within one choice group folder on decision center.

2.6 Dynamic Choice Reporting in the Decision Center

This section consists of the following topics:

• Section 2.6.1, "Dynamic Choice Reporting Overview"

• Section 2.6.2, "Distribution of Choices Across Decision Center Folders"

2.6.1 Dynamic Choice Reporting Overview

This section consists of the following topics:

• Section 2.6.1.1, "No Impact for Applications with Static Choices Only"

• Section 2.6.1.2, "Dynamic Choice Visibility"

• Section 2.6.1.4, "System-Created Range Folders"

• Section 2.6.1.3, "Dynamic Choice and Range Folder Appearance in the Decision Center"

• Section 2.6.1.5, "Range Folder for Presentation Only"

• Section 2.6.1.6, "Dynamic Choice Reporting"

2.6.1.1 No Impact for Applications with Static Choices Only

If your application has been configured to use only Static Choices, there is no impact on Decision Center reporting. The Choice Groups, subgroups, and Static Choices that you defined in Oracle RTD Decision Studio will appear in the same hierarchical layout in the Oracle RTD Decision Center Navigator, as shown in the example in Figure 2-18.

Figure 2-18 Example of Definition and Reporting with Static Choices Only

2.6.1.2 Dynamic Choice Visibility

Dynamic Choices, by their very nature, cannot be predefined in Oracle RTD Decision Studio. A Choice Group can be configured to hold dynamically-extracted external data, from which Dynamic Choices can be recommended. Figure 2-19 shows an example of a Choice Group set up to display Dynamic Choices for insurance services.

Figure 2-19 Example of Dynamic Choice Group Definition

In Oracle RTD Decision Center, only those Dynamic Choices that have actually been recommended and added to model learning data appear in the Decision Center Navigator, and have Performance and Analysis reports.

The other factor that influences how the Dynamic Choices appear in the Decision Center is the parameter Maximum number of choices within one choice group folder on decision center, which you specify when you define the Dynamic Choice Group. If the number of choices exceeds this maximum, the choices appear under system-created range folders, otherwise they appear directly under the Choice Group name.

For more information on range folders, see Section 2.6.1.4, "System-Created Range Folders."

The example Decision Support Navigator menu in Figure 2-20 shows the following:

• Five Dynamic Choices were recommended and added to model learning data.

• The maximum number of choices per choice group is 3.

• Each Dynamic Choice appears under one of the two system-created folder names.

Figure 2-20 Example of Dynamic Choice Layout in Oracle RTD Decision Center

2.6.1.3 Dynamic Choice and Range Folder Appearance in the Decision Center

Each Dynamic Choice is indicated in the Decision Center Navigator by a circle icon, that also contains a check mark and an asterisk.

Unlike the standard folder, which represents a Choice Group defined in Oracle RTD Decision Studio, the icon representing the range folder contains a check mark and an asterisk.

2.6.1.4 System-Created Range Folders

The name of each system-created folder is made up of the names of the first and last Choices in the folder, with the string "..." separating the two Choices. System-created folders are also known as range folders.

Note: The Choices within a range folder can be a mixture of Static and Dynamic Choices. Both components of the range folder name can therefore be either a Static or a Dynamic Choice. In general, Oracle recommends that applications keep Static and Dynamic Choices in separate Choice Groups or separate Choice Group hierarchies.

If the total number of (Static choices + Dynamic Choices recommended and added to model learning data) exceeds the maximum defined for the Choice Group folder, the choices appear in system-created "groups" or subfolders, otherwise they appear directly under the Choice Group name.

2.6.1.5 Range Folder for Presentation Only

There is an important difference in how you use standard and range folders in the Decision Center.

Whereas you can click the name of a standard folder to open reports for Choices within the folder, range folders are for presentation only.

In other words, clicking the name of a range folder will not open any reports. To see reports for a Dynamic Choice, you must click the Dynamic Choice itself.

2.6.1.6 Dynamic Choice Reporting

When you click a Dynamic Choice in the Navigator, the two tabs that appear are the Performance and Analysis tabs.

Static Choice reporting includes a third option, namely Definition Reports. Because Dynamic Choices are not defined in Oracle RTD Decision Studio, there are no Definition Reports for Dynamic Choices.

The Performance and Analysis reports for Dynamic Choices show exactly the same kind of data and statistics as for Static Choices.

Note: Static Choices always appear in the Decision Center, Dynamic Choices only appear if they were recommended within the time interval of the report.

2.6.2 Distribution of Choices Across Decision Center Folders

When configuring a Choice Group for Dynamic Choices in Oracle RTD Decision Studio, there are two parameters that affect how choices appear in Oracle RTD Decision Center.

Both parameters are in the Dynamic Choices tab, and they are only enabled if the Choice Group is selected to be used for Dynamic Choices. The parameters are:

• Distribution mode for choices over choice group folders

• Maximum number of choices within one choice group folder on decision center

For simplicity, these parameters are referred to as Distribution mode and Maximum number of choices in this section.

The Maximum number of choices parameter determines how choices appear in the Decision Center directly under the Choice Group name or under a system-created range folder. For more information on range folders, see Section 2.6.1.4, "System-Created Range Folders."

Note: In Oracle RTD Decision Center reports, range folders are not dedicated to Static or Dynamic Choices, that is, both Static and Dynamic Choices may appear together in the same range folder.

The Maximum number of choices parameter limits the number of Choices, regardless of whether they are Static or Dynamic, in each range folder.

The Distribution mode parameter specifies how the range folders are populated:

• In Spill mode, each range folder is filled up to the maximum, and the final range folder typically has less values than the maximum.

• In Even mode, the aim is to distribute the Choices evenly across the range folders.

For example, if there is a total of 106 Static or Dynamic Choices to display in the Decision Center, and the maximum per range folder is 25:

• In Spill Mode, the distribution across the range folders is 25,25,25,25,6.

• In Even Mode, the distribution across the range folders is 22,21,21,21,21.