Siebel Master Data Applications Reference for Industry Applications > Configuring and Administering Siebel Universal Customer Master Privacy Management > Process of Configuring Siebel Universal Customer Master Privacy Management >

Preliminary Requirements Before Configuring Siebel Universal Customer Master Privacy Management

This task is a step in Process of Configuring Siebel Universal Customer Master Privacy Management.

Before configuring Siebel Universal Customer Master (UCM) Privacy Management, make sure the following preliminary software requirements are met:

• UCM SIA installed
• Siebel Business Rules Developer installed (part of the Siebel Tools installation)

The Siebel Business Rules Developer is required for design time of privacy rules but is not required in run time.

About UCM Rule Engine Helper

The Universal Customer Master (UCM) Rule Engine Helper is a prebuilt helper business service for master data application to help preparing input for the rule engine and processing output from the rule engine.

To review specific details on business services, including user properties, methods, and method arguments, use Siebel Tools. For information on using Siebel Tools, see Using Siebel Tools on the Siebel Bookshelf.

About Siebel Universal Customer Master Privacy Workflow Processes

Siebel Universal Customer Master (UCM) Privacy Management consists of the following preconfigured UCM Privacy workflow processes. For background information on workflow processes, see Siebel Business Process Framework: Workflow Guide on the Siebel Bookshelf.

The following workflows and the corresponding sample privacy rules are provided to administer privacy changes associated with Contacts on a Financial Account. Similar workflows and privacy rules can be created in UCM and Siebel Business Rules Developer corresponding to privacy changes associated with prospects, consumers, companies, organizations, or households. Run-time events are used to trigger these workflows.

The UCM Privacy Workflow processes are:

• UCM Privacy Process
• UCM Privacy Process—Pending Expired
• UCM Privacy Process—Reevaluate Privacy Batch

UCM Privacy Process

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. This 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 those for businesses. The sample rules provide examples where business financial accounts, by default, opt-in data sharing compared with consumer financial accounts, by default, have more restrictive data sharing.
• New financial account contact has been added. This workflow is triggered, by way of run-time events, typically during a financial account new booking process where a new financial account with contact information is submitted to UCM from an external system such as a financial loan origination system. This 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. This workflow is also triggered if a new financial contact is added. The sample privacy rules written in Siebel Business Rules Developer determine the contact privacy preferences based on each contact's primary garage address state. You must change the default privacy preference values stored in the privacy rule based on privacy regulations and the company's data sharing practice.
• Financial account contact privacy setting has been updated. This 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. This 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 may change, too. The sample privacy rules provide the logic to set updated privacy preference values for the inactive contact, as well as re-evaluate the privacy status of the financial account to which the inactive contact associates.
• Financial account contact garage address has been changed. This 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 may 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 occurs. This initial waiting period may be different for other states. The sample Haley Privacy Knowledge Base provides examples of such logic.

UCM Privacy Process—Pending Expired

Different states in the U.S. can mandate different initial waiting periods during which a Contact may elect to opt-in or opt-out sharing of his or her personal information. This workflow process can be invoked using a workflow process batch manager server component. For background information on how to run workflow process batch manager server component, see Siebel System Administration Guide. It can be run in background with search specification to pick up all the financial accounts where the pending period have expired. The length of the pending period is specified as rules and is set in UCM when the financial account is created or updated. The pending period is preconfigured to 50 days.

UCM Privacy Process—Reevaluate Privacy Batch

This workflow process can be invoked using a workflow process manager server component. For background information on how to run workflow process manager server component, see Siebel System Administration Guide. It is a self-looping workflow process to avoid workflow batch process manager's query overhead. This workflow is triggered when there is a change to the privacy global settings, for example, some states' law changes the default privacy settings for telemarketing sharing. The sample rules provide some basic logic to re-evaluate market sharing for the financial account and the contact.