DR Configuration

Modules

The following modules are in use by the DRA application:

Module	Description
Property	Store base information for a property. Parent of a Loan.
Loan	Fannie loans that are actively referred to by DRA. When a DRA event file is imported, if it references a Fannie Loan number that is not in the Loan table, it is inserted from the import.FannieLoan table.
Process	Unique Foreclosure and Bankruptcy records received from attorneys are represented by a Process and corresponding Foreclosure or Bankruptcy row. Tasks (Events) associated with these processes are bound to the Foreclosure or Bankruptcy accordingly.
Task	Also referred to as Events, tasks represent Foreclosure events, Bankruptcy events, or Delay events. Foreclosure task are bound to a Foreclosure, Bankruptcy tasks are bound to a Bankruptcy, and Delays tasks are bound to a Loan.
Message	Used for global messages.
Organization	Used to store servicer and attorney organizational information.
Contact	Based table for Organization.
Template Tables	Dictate the behavior of instance table rows.
ProcessTemplate	Defines the behavior of a Process.
TaskTemplate	Defines the behavior of a Task.
MessageTemplate	Defines the behavior of a Message.

Import File Templates

Template	Description
Fannie Loan Sync	Imports Fannie Mae loan files on a monthly based into the import.FannieLoan table. Used by the DR Legacy Events import to insert rows into the Loan table. The data files for this import are provided by Fannie Mae via sFTP.
DR Legacy Events	Imports a legacy events file into QBO.

Subscriptions

The QBO ObjectSubscription module is used to tag QBO records with unique keys from other systems. Current in use include:

Use Case	Pattern
Single Sign On	The Fannie SSO platform passes a 5 digit corporateFamilyCode code as a claim. This is used by Person/LoginFannie to map a user to a Servicer Organization record.
Legacy Provider Codes	The ImportForm/DRLegacyEvents import statement maps legacy 'Provider codes' to an Organization based on the old provider codes, and are required.
Marketing Codes	The Fannie Mae marketing code (e.g. JPMOR) is used to uniquely identify a Servicing Organization, so we don't wind up with 17 version of JP Morgan. Marketing codes are imported via a daily vendor file.
Seller Servicer Codes	The 9 digit seller servicer codes are imported via a daily vendor file, and are mapped to the Organization with the appropriate Marketing Code. These 9 digit codes are referenced by the Fannie Mae Loan file that QBO ingests on a regular basis. This allows us to map Loan.ServicerID and Loan.AssignedOrganizationID to the appropriate Organization without creating 17 versions of JP Morgan.

The overall patterns include:

Module	Prefix	Subscription
Organization	defaultreporting.fnma.com-Provider-{ProviderCode}	Maps legacy P-codes to Organization records.
Organization	defaultreporting.fnma.com-Servicer-{MarketingCode}	Maps Marketing (or Corporate Family) codes to Organization records.
Organization	defaultreporting.fnma.com-Servicer-{SellerServicerID}	Maps Seller-Servicer codes to Organization records.
Organization	mornet.fnma.com-Attorney-{mornetPlusId}	Maps Fannie Mae Mornet codes to Organization records.
SystemRole	fmsso.fanniemae.com-Role-{Group}	Maps Fannie Mae SSO AD Groups to QBO Roles.
Foreclosure	defaultreporting.fnma.com-Foreclosure-{ProviderCode}-{Loan}-{Attorney File}	Uniquely identifies a Foreclosure record.
Bankruptcy	defaultreporting.fnma.com-Foreclosure-{ProviderCode}-{Loan}-{BK Case Number}	Uniquely identifies a Bankruptcy record.
ImportFormTemplate	defaultreporting.fnma.com-DelayCode-{DelayCode}	Uniquely identifies Delay tasks for importing.
ImportFormTemplate	defaultreporting.fnma.com-EventCode-{EventCode}	Uniquely identifies Event tasks for importing.

Publishing Configuration

To publish configuration data between environments, from any Search panel, select the items to be exported QBO will serialize data to XML,

Single Sign On (SSO)

QBO's SSO module enables single-sign-on via Fannie Mae's SSO platform. When a user is authenticated, the following happens:

• All claims are passed to a statement: Person/LoginFannieMae
• If the user does not exist in the Person table, a new Person is created
• If a SystemRole has a subscription to fmsso.fanniemae.com-Role-{Group claim}, the user is added to that role
• If an Organization has a subscription to the the mornet.fnma.com-Attorney-{mornetID claim}, the user is granted access to that organization

Importing Data

The following templates are used to import data:

Template	Description
DR Legacy Event	Imports legacy flat files, applying logic described below.

DR Legacy Events

todo: document!