Oracle Customer Hub (UCM) Master Data Management Reference > Configuring Oracle Customer Hub (UCM) Privacy Management > Customization Methods >

Examples of Customizing the Sample Knowledge Base

This topic gives examples of customizing the sample knowledge base. You might use this feature differently, depending on your business model. Review the following examples to see if they apply to your implementation:

• Capturing Privacy Elections for a New Business Channel
• Changing the Address for Privacy Preferences
• Implementing a New Company Policy to Be Compliant with OFAC
• Modifying New State Default Privacy Options upon Pending Expiration
• Modifying the State Restrictiveness Ranking Table
• Using New Business Components in Oracle Customer Hub (UCM) to Reuse Modules or Rules in the Privacy Knowledge Base

Capturing Privacy Elections for a New Business Channel

You want to capture privacy elections for a new channel added to the business, for example, Insurance.

Adding a new privacy preference involves several changes to the business rules after the privacy preference is added in the Siebel table and Siebel Repository. Use the following task to capture privacy elections for a new business channel.

To capture privacy elections for a new business channel

1. Run the Siebel Object Importer to bring the change into the knowledge base conceptual role model.

   New concepts and relations are generated automatically.

2. Add the instances for the privacy preference to the privacy preference concept Insurance.
3. Add a new table with the default privacy preference values for insurance, copying the format of the existing Default Privacy Option Tables.
4. Add the business rules for this new privacy preference.

Changing the Address for Privacy Preferences

You want to evaluate the privacy preferences based on the addresses other than Garage Address, for example, Permanent Address. In such a case, you must change the rules in both the Siebel CRM configuration and HaleyAuthority.

NOTE:  If you do not require consistency in concept and entity naming, the required changes are minimal.

To change the address for privacy preferences (solution one)

1. In Oracle Customer Hub (UCM), add the LOV Permanent to the Address Type field for FINCOPR Account Contact Address.
2. Change the business component search specification, UCM FINCORP Account Contact Garage Address Source Data and History, from:

   [Address Type] = 'Garage' AND [UCM Type Code] = 'History' AND [Parent Type] = 'Financial Account Contact'
to:
   [Address Type] = 'Permanent' AND [UCM Type Code] = 'History' AND [Parent Type] = 'Financial Account Contact'

3. Modify the run-time event to look for changes in Permanent Address instead of Garage Address.
4. In HaleyAuthority, search for the word Address Type, replace Garage with Permanent in all the statements found, then deploy the changed modules.

Changing the Address for Privacy Preferences (Solution Two)

If you require consistency in the wording of concept rules and entity rules in Oracle Customer Hub (UCM) and HaleyAuthority, then perform the following procedure.

To change the address for privacy preferences (solution 2)

1. Make the changes specified in solution one.

   For more information, see To change the address for privacy preferences (solution one).

2. Create a new business component.
3. Modify the business object and integration object definitions.
4. Modify the rules administration configuration.
5. Run Siebel Object Importer to bring the new concept and relations into HaleyAuthority.
6. Build the new rules, using the existing rules for garage address.
7. Create a new module to hold the new rules.

Implementing a New Company Policy to Be Compliant with OFAC

You pass a new company policy to be compliant with the Office of Foreign Assets (OFAC) list, and privacy rules must be created around OFAC. The existing field exists in both the Siebel Repository and Haley Conceptual model, so do not run Siebel Object Importer again.

Add a new submodule under the corresponding event module, and then add the relevant business logic.

Modifying New State Default Privacy Options upon Pending Expiration

You want the default privacy options to be set for each customer. The default privacy options are based on the privacy state code for each preference.

Modify table entries in the Default Privacy Option Table in the U.S. FS.1 Default privacy option tables. The entries for additional state regulations can be added by inserting additional rows in this table.

Modifying the State Restrictiveness Ranking Table

You want to alter the ranking of states used to determine the privacy state code for the financial account.

Modify the priority of the states in the State Restrictiveness Ranking Table in U.S. country rules or add additional states with priorities. If Puerto Rico has the same rank as another entry, Puerto Rico has a rule that makes it take precedence in the module, U.S. country rules.

Using New Business Components in Oracle Customer Hub (UCM) to Reuse Modules or Rules in the Privacy Knowledge Base

FINCORP is a standard business component and corresponds to S_ASSET. You want to reuse the rules related to the FINCORP account, but you must use your industry-specific business component based on S_ASSET.

Make these modifications:

• Run Siebel Object Importer to bring the new business components into knowledge base conceptual role model.

  New concepts and relations are generated automatically.

• Change the rules that you want to reuse to use the concepts and relations that you just imported. Or, copy the original rules instead of changing them.
• Reparse the rules.