Oracle Customer Hub (UCM) Master Data Management Reference > Configuring Oracle Customer Hub (UCM) Privacy Management > About Privacy Management Workflow Processes >

About UCM Privacy Process Workflow

This workflow process is invoked by run-time events through the business component user property Named Method and can be configured to support additional events. This workflow handles the following events:

• Financial account type changes. The workflow is triggered, by way of run-time events, when a financial account type changes. For example, a car loan has changed from a consumer car loan to a business car loan because the car is now used as a company vehicle. Some privacy regulations mandate different compliance requirements for consumers than for businesses. The sample rules provide examples for both business financial accounts, whose opt-in data sharing is less restrictive, and consumer financial accounts where data sharing is more restrictive.
• New financial account contact has been added. The workflow is triggered, by way of run-time events, typically during a financial account new booking process. In this process, a new financial account with contact information is submitted to Oracle Customer Hub (UCM) from an external system, such as a financial loan-origination system. The workflow calls the rules engine to set the initial privacy preference values for each contact and for the financial account to which the contact belongs. The workflow is also triggered if a new financial contact is added. The sample privacy rules written in Siebel Business Rules Developer determine the contact's privacy preferences based on the entry in contact's Primary Garage Address State field. The default privacy preference values stored in the privacy rule must be changed, with the changes based on the privacy regulations and the company's data sharing practice.
• Privacy setting for a financial account contact has been updated. The workflow is triggered, by way of run-time events, when a financial account contact's privacy setting is changed.
• Financial account contact status has been set to Inactive. The workflow is triggered, by way of run-time events, when a contact changes its status from Active to Inactive. When a contact's status changes, its privacy sharing rights might change, too. The sample privacy rules provide the logic to set the updated, privacy-preference values for the inactive contact, as well as reevaluate the privacy status of the financial account with which the inactive contact is associated.
• Financial account contact garage address has been changed. The workflow is triggered, by way of run-time events, when a contact on a financial account changes his or her address. The current U.S. privacy regulation allows states to pass their own privacy regulation and therefore different privacy rules and business logic might be applied depending on the state where the financial account belongs. For example, California Financial Information Privacy Act (also known as CA SB1) requires that financial institutions provide California-based residents with a special disclosure and allow a 45-day initial waiting period before sharing of data occurs. This initial waiting period might be different for other states. The sample Haley Privacy Knowledge Base provides examples of such logic.