/
RGI Client CRM Synchronization

RGI Client CRM Synchronization

High Level Design

Synchronizing the RGI client information with the CRM follows this approach.

Error rendering macro 'excerpt-include' : No link could be created for 'HSIF:RGI Data to Salesforce Detailed Solution Proposal'.

RGI Data File

SSHA provides a file with all the eligible clients on listed on the file. To determine any changes the current file must be compared to the previous day's file. Any additional records should be added to the

ItemTypeSourceDestinationComment
Applicant CodeStringRC_Applicant_CodeRGI_Applicant_Code__cNew household id for a family after Yardi migration

Household ID

numberHousehold Ref#

RGI_Houshold_Id__c

For the Household ID for the member

System ID

numberMember ID
SSHA_id__c


Applicant IDnumberMember_refRGI_Member_Id__c

Given Name

String 50First Name

first_name__c


Last Name

String 50Last Name

last_name__c


Gender

String 6Gender

gender__c

M, F, U

Date of Birth

DateDate Of Birth

date_of_birth__c


Application ID

numberApplication ID


Not needed

Application Status

String 6Application Current Status Codergi_status__c

Legacy status

Email Address

String 255Member eMail address

email__c


Telephone Contact (Home)

String 20Home Phone

phone




Home Phone Ext

Phone_Ext__c


Telephone Contact (Mobile)

String 20Mobile Phone

Mobile_phone__c




Mobile Phone ExtMobile_Phone_Ext__c

Telephone Contact (Work)

String 20Bus Phone

Other_phone__c




Bus Phone ExtOther_Phone_Ext__c

Postal Address

  Street Number

String 15Member Mailing Address Street Number

BillingStreet

Combine Unit, street number and street name

  Street Name

String 80Member Mailing Address Text

BillingStreet


  Unit Number

String 10Member Mailing Address Unit Number

BillingStreet


  City

String 30Member Mailing Address City

BillingCity


  Province Code

String 6Member Mailing Address Province

BillingState


  Postal Code

String 6Member Mailing Address Postal Code

BillingPostalCode


applicationCreateDate
Date
Application Create Date
OW_start_date__c
Keep OW's prefix, will be re-mapped with RGI in SF.
accountSource
String
"Housing/Shelter"
Hard code for RGI indicator

JSON example:

{
"allOrNone" : false,
"compositeRequest" : [
{
     "method" : "POST",
      "url" : "/services/data/v45.0/sobjects/Legacy_System_Record__e",
      "referenceId" : "265573",
       "body" : {
              "JSON_Message__c" : "{
                       "BillingStreet":"",
                       "BillingCity":"TORONTO",
                       "BillingState":"ON",
                       "BillingPostalCode":"M8V ",
                       "ApplicationId":"422368",
                       "RecordTypeId":"0126A000000yrPjQAI",
                       "AccountSource":"Housing/Shelter",
                       "first_name__c":"",
                       "last_name__c":"",
                       "date_of_birth__c":"1948-",
                       "Mobile_phone__c":"",
                       "RGI_Houshold_Id__c":"911613768",
                       "SSHA_id__c":"265573",
                       "RGI_Member_Id__c":"911613768",
                       "OW_start_date__c":"2017-06-30",
                       "rgi_status__c":"ELG"
                }",
              "Object_Name__c" : "Account"
       }
}...
]
}

TAWL - Yardi/Rent Cafe Status Mapping:

TAWL Application StatusesRent Café StatusNotes
(Bring notes for all the canceled Rent Café statuses; Yardi will mass update into Secondary Status field later)
CX1Cancelled - ArrearsCanceled
For ex.
Notes type - 'Cancelled Reason'; Note: 'Cancelled | Arrears'

Yardi will update 'Arrears' into Secondary Status field
CX5Cancelled - Chronological- COHB
CX4Cancelled - Indigenous- COHB
CX3Cancelled - Modified- COHB
CXGCancelled - SPP Portable Housing Benefit
CX2Cancelled - SPP-COHB
CXRCancelled-3 Refusals
CXBCancelled-Administration
CXECancelled-Applicant not Eligible
CXCCancelled-Applicant Request
CXACancelled-Deceased
CXDCancelled-Documents Required
CXUCancelled-Duplicate Application
CXHCancelled-Homeless
CXXCancelled-Housed By Provider
CXFCancelled-Housed Humewood Partnership
CXPCancelled-Housed R/S (Next Steps)
CXQCancelled-Housed R/S (Tent City)
CXICancelled-Information Not Complete
CXTCancelled-Internal Transfer
CXMCancelled-Mail Returned
CXNCancelled-No Response
CXYCancelled-Not able to move
CXOCancelled-Other
CXJCancelled-Reapplied in Error
CXSCancelled-Split
CXVCancelled-Unsatisfactory History
CXZCancelled-Zero Members
ELG*Eligible (Not on hold and no offers)Eligible

*Eligible (On hold for SPP Reconciliation)Inactive

*Eligible (On hold for COHB)Canceled

*Eligible (On Offer, Verbal Acceptance offer, and Accepted offer but not yet leased files) On Offerwith Verbal Acceptance as Offer Secondary Status
HOUHousedHoused
CIFInactive - Housed Humewood PartnershipHousedNotes type - 'Data from TAWL'; Note: 'Temp Housed'
CIGInactive - SPP Portable Housing BenefitHousedNotes type - 'Data from TAWL'; Note: 'Temp Housed'
CIAInactive - ArrearsCanceled
CI5Inactive - Chronological- COHBFor ex.
Notes type - 'Cancelled Reason'; Note: 'Inactive | Chronological- COHB'

Yardi will update 'Chronological- COHB' into Secondary Status field
CI4Inactive - Indigenous- COHB
CI3Inactive - Modified- COHB
CIWInactive - Refused to Withdraw
CI2Inactive - SPP-COHB
CIRInactive-3 Refusals
CIDInactive-Documents Required
CIHInactive-Homeless
CIIInactive-Information Not Complete
CIMInactive-Mail Returned
CINInactive-No Response
CIYInactive-Not able to move*Convert cases prior to Jan 2020 to 'Eligible' and the rest to 'Canceled'
CIOInactive-Other
CISInactive-Split
CIEInactive - Not EligibleIneligble
PENPendingApplied

TAWL Copy and Processed Tables

On a daily basis, SSHA receives a copy of the TAWL clients and loads it into the MemberExtraction_tawl table. This table can be considered as the current version of the member information. The MemberExtraction_sf table contains the member information that has been uploaded to the CRM, this table can be considered the previous version

Initially the MemberExtraction_sf table is empty and the MemberExtraction_tawl table contains all the active RGI members. As the HSI RGI synch process runs,  the differences between the MemberExtraction_tawl and the MemberExtraction_sf are sent to the CRM.

HSI has read access to the MemberExtraction_tawl table and read, insert, delete and update access to the MemberExtraction_sf table.

The MemberExtraction_tawl table does not appear to have any primary keys or indexes and does have some duplicates.

Views

SSHA has provided these views to support this process:

sf_delete, sf_insert, sf_update

Database Connectivity

jdbc:jtds:sqlserver://torms201.corp.toronto.ca:1433/

Database is HSI_RO