Bookshelf Home | Contents | Index | PDF |
Oracle Customer Hub (UCM) Master Data Management Reference > Configuring Oracle Customer Hub (UCM) Privacy Management > Customization Methods > Examples of Customizing the Sample Knowledge BaseThis 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 ChannelYou 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
Changing the Address for Privacy PreferencesYou 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)
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)
Implementing a New Company Policy to Be Compliant with OFACYou 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 ExpirationYou 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 TableYou 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 BaseFINCORP 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. |
Oracle Customer Hub (UCM) Master Data Management Reference | Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |