3.1 Use Cases for Configuring Tables
You can use the following scenarios to understand the services. Before modifying the JSON, you must configure the tables with appropriate values.
Note:
This section applies only to the following API Services:- Create Event
- Create Event and Promote to Case
- Create Event and Extend to Existing Case
Adding an Entity and Adding Persistence to an Entity use cases explain how to add a new entity in FCC_RT_EVENT_ENTITY_TABLES.
Adding an Entity, Adding Persistence to an Entity, and Adding PTC for Entity use cases explain how to use the Create Event service.
Adding an Entity, Adding Persistence to an Entity, Adding PTC for Entity, and Adding an Event Type to Correlation Map use cases explain how to create Event and Attach to Existing Case.
Adding an Event Type to Correlation Map use case explains how to map an event type to correlation rule.
Adding an Entity
To add an entity, follow these steps:
- Add a new entry in the FCC_RT_EVENT_ENTITY_TABLES table, as shown in the
following table:
Table 3-7 FCC_RT_EVENT_ENTITY_TABLES
N_ENTITY_TYPE_ID V_ENTITY_TYPE V_EVENTED_TABLE_NAME V_ENTITY_TABLE_NAME V_ENTITY_LOOK_UP_TABLE_NAME IS_LOOK_UP_PER_REQD IS_ENTI_PER_REQD IS_EVENT_PER_REQD Column Name V_LOOKUP_SEQUENCE_NAME 102 ECM_CUSTOMER FCC_CUST_EVNT FCC_CUST FCC_CUSTOMER_ LOOKUP Y Y Y _ Oracle recommends setting the flag to Y for the IS_LOOK_UP_PER_REQD and IS_EVENT_PER_REQD columns. The V_ENTITY_TABLE_NAME table names must be the same as mentioned in the backend ECM data model.
- Add the evented details in the FCC_RT_EVENT_ENTITY_TABLES_COL table for the
newly added entity, as shown in the following table:
Table 3-8 FCC_RT_EVENT_ENTITY_TABLES_CO
N_ENTITY_TYPE_ID V_TABLE_NAME V_COL_BUSINESS_NAME V_COL_NAME V_DATA_TYPE V_COL_TYPE V_IS_SURROG_KEY 102 FCC_CUST_EVNT custId CUST_INTRL_ID CHAR _ _ Here, the entry in the V_TABLE_NAME column must be the same as either the V_EVENTED_TABLE_NAME,V_ENTITY_TABLE_NAME, or V_ENTITY_LOOK_UP_TABLE_NAME column of the FCC_RT_EVENT_ENTITY_TABLES table.
Adding Persistence to an Entity
For the FCC_RT_EVENT_ENTITY_TABLES table, the following scenarios are possible:
- If the IS_LOOK_UP_PER_REQD, IS_ENTI_PER_REQD, and IS_EVENT_PER_REQD columns are
set to Y, then the corresponding Entity and Event tables will be populated after
lookup as shown in the following table.
Table 3-9 Adding Persistence to an Entity 1
N_ENTITY_TYPE_ID V_ENTITY_TYPE V_EVENTED_TABLE_NAME V_ENTITY_TABLE_NAME V_ENTITY_LOOK_UP_TABLE_NAME IS_LOOK_UP_PER_REQD IS_ENTI_PER_REQD IS_EVENT_PER_REQD Column Name V_LOOKUP_SEQUENCE_NAME 102 ECM_CUSTOMER FCC_CUST_EVNT FCC_CUST FCC_CUSTOMER_ LOOKUP Y Y Y _ - If the IS_LOOK_UP_PER_REQD and IS_EVENT_PER_REQD columns are set to Y, then the
corresponding Event tables will be populated after lookup. If the
IS_ENTI_PER_REQD column is set to N, then the UI may not display the correct
data as shown in the following table.
Table 3-10 Adding Persistence to an Entity 2
N_ENTITY_TYPE_ID V_ENTITY_TYPE V_EVENTED_TABLE_NAME V_ENTITY_TABLE_NAME V_ENTITY_LOOK_UP_TABLE_NAME IS_LOOK_UP_PER_REQD IS_ENTI_PER_REQD IS_EVENT_PER_REQD Column Name V_LOOKUP_SEQUENCE_NAME 102 ECM_CUSTOMER FCC_CUST_EVNT FCC_CUST FCC_CUSTOMER_ LOOKUP Y N Y _
Adding PTC for Entity
To add PTC for an entity, add a new entry in the FCC_RT_EVENTTYPE_PTC table.
Before adding the entries in the FCC_RT_EVENTTYPE_PTC table, populate the FCC_RT_EVENT_ENTITY_TABLES and FCC_RT_EVENT_ENTITY_TABLES_COL tables.
Table 3-11 Adding PTC for Entity
V_CASE_TYPE | N_SEQUENCE | V_T2T_CODE |
---|---|---|
AML_DD | 1 | t2t_KDD_CASE_ACCOUNTS |
AML_DD | 2 | t2t_KDD_CASE_CUSTOMERS |
AML_DD | 3 | t2t_KDD_CASE_INSTN_MASTER |
AML_DD | 4 | t2t_KDD_CASE_CLIENT_BANK |
AML_DD | 5 | t2t_KDD_CASE_EXTERNAL_ENTITY |
Adding an Event Type to Correlation Map
Table 3-12 Adding an Event Type to Correlation Map
N_CORRELATION_RULE_SKEY | V_EVENT_TYPE |
---|---|
12 | AML_SURV |