Example of LoadData Method Using Key Field and Value Field
Golden Gate Bank decides to implement its product rates using a different schema. Instead of one record for one product as shown in the following table, they would like to store the data using name-value pairs for each product. The advantage of this approach is that they can add new attributes without schema changes. The following table shows the data that is stored in the Financial Product Attribute business component.
Region | Product | Attribute Name | Attribute Value |
---|---|---|---|
West |
Checking |
Balance |
10000 |
West |
Checking |
Rate |
0.2 |
West |
Savings |
Balance |
29000 |
East |
Savings |
Rate |
2.1 |
The following table shows the arguments used to retrieve the data and store it in a format as defined by the ProductRate Vector sample diagram shown in About Business Rule Process Property Types type.
Input Argument Name | Value |
---|---|
Buscomp |
Financial Product Attribute |
IsCachedData |
Y |
Hierarchical Key 1 |
Region |
Hierarchical Key 2 |
Product |
Sort Spec |
Region, Product |
Key Field |
Attribute Name |
Value Field |
Attribute Value |