Siebel Master Data Applications Reference for Industry Applications > Privacy Management Solution >
Sample Privacy Rules
The top-level modules are grouped by privacy events and the type of rules in the module (core rules as compared to specific business rules). In addition, modules are separated by order of evaluation because only top-level modules can have priorities.
The following are the major modules:
Account Type Change Event module
Purpose: This module contains rules that apply when a fincorp account type is changed from Consumer to Business or the other way.
Consumer Address Change Event module
This module contains rules that apply when a fincorp account contact of a consumer type of fincorp account moves to a new state. Certain sub-modules are applicable only when this causes a change to the privacy state code for the fincorp account.
Contact Inactivated Event module
Purpose: This module contains rules that apply when a fincorp account contact is inactivated from a fincorp account. The sample rules specific to Contact Inactivated Event are included in the sub-module "Customer Rules". The other sub-modules are actually a copy of the core modules including "Input interpretation", "Initialization", "Core Privacy Rules", "Generate Output" and "Reevaluate privacy". This is because "Contact Inactivated Event" is for both active and inactive contacts; whereas the other events are for active contacts only. They can not share the same core modules.
Core Privacy Rules module
Purpose: This module contains the core rules that generally apply to all the evaluation requests.
- CUST. Customer rules. This module contains customer-specific core rules. The sample rule provided is for the consumer type of customers, which forces the channel partner sharing preference elections to be identical to the non-affiliate sharing preference elections for consumers outside of California who have a channel partner type of Brand X or Brand Y.
- US.FS. Evaluate core privacy rules. This module contains core rules that generally apply to all US Financial Services customers for any evaluation request.
- US.FS.1. Determine privacy state code. This module contains statements that set the privacy state code values for a business or consumer account and determine whether it has changed from a previous value.
- US.FS.2. Determine precedence of privacy options and sources. This module contains statements that use the privacy option with source hierarchy to determine the roll up of privacy preferences to the financial account level.
- US.FS.3. Handle privacy notices and letters. This module contains statements that determine whether a contact receives an annual notice and what cover letter and notice must be sent to the customer, except in the case where the contact has moved.
Generate Output module
Purpose: This module contains the rules that must evaluate after the main body of business rules and be used to set values on the privacy record to be output to UCM. The sample rules provided set value to a concept only when the concept value need to be changed after the evaluation of the main business rules.
Purpose: This module contains business rules including definitions and tables of default values:
- CUST. Customer rules. This module contains initial business rules and table instances that are customer-specific. This module includes table instances of cover letter types and privacy notice types based on privacy state code and owner type (communication message type) and the cover letter types based on state address change and owner type.
- Expired Pending Period. This module contains a business rule to determine that a pending period has expired.
- Initial values. This module contains initial business rules and table instances that are not country or industry-specific. Includes the table instance establishing the hierarchy of privacy option with sources (Opt In Request < Opt In Default < Pend < Opt Out Default < Opt Out Request).
- US. Country rules. This module contains initial business rules and table instances that apply to US companies (for example, a rule establishing the most restrictive state for each contact). This module includes a table instance ranking the restrictiveness of US states. This module contains some examples and please consults with your company's consumer privacy best practices and tailors these samples rules accordingly.
- US.FS.1. Default privacy option tables. This sub-module includes tables of default privacy options for each privacy flag based on state code.
Input Interpretation module
Purpose: This module contains rules that interpret input data and determine key privacy related facts:
- Annual notice requirement
- Contact Delete
- Determine garage address state
- Determine primary fincorp account contact
- Privacy State Code
New Financial Account_New Contact Event module
Purpose: This module contains the rules that apply when a new fincorp account or a fincorp account contact is added.
- Determine New financial account or New financial account contact. This module contains the rules that decide on the event object type: whether it is for a new fincorp account or for a new fincorp account contact.
- New contact. This module contains the rules that apply for a new fincorp account contact case. Business and Consumer types of fincorp account have different privacy regulations further specified in two separate submodules.
- New financial account. This module contains the rules that apply for a new fincorp account case.
Pending Period Expired Event module
Purpose: This module contains rules that apply when the pending period for the Consumer type fincorp account expires (such as setting the default privacy options for each privacy preference based on the privacy state code).
Reevaluate Privacy module
Purpose: This module contains the statements that interpret and recognize the input privacy options with sources on fincorp account contact privacy level. By executing rules in this module, all customer requested flag values are preserved and not just limited to OUT Requested.