How it works:
ICE's Paragon system is a nationwide MLS portal. By integration with GrowthZone additions and updates of agents and offices are seamlessly sent to ICE. GrowthZone sends a file with additions and changes every 15 minutes to Paragon's FTP site.
Canada Customers: Notes about Canada customers at bottom of page
PROJECT KICKOFF
Overview:
The customer must have a signed contract with Paragon before integration can begin. Once completed, the Integration Specialist reaches out to Paragon and the customer to receive RETS Credentials that are used to both pull data, and for turning on/testing the integration. Testing is done only in Production, however a test file/build file is sent while in Staging . Delays can be caused by waiting for the contract, and for Paragon to build their environment.
Ticketing Process for RE Integrations (Review the below and we'll remove the red notation)
- When requesting the RETS Feed, the Integration Specialist will CC platformintegrations@growthzone.com email to create a Paragon- (Tenant Name) ticket for project visibility. That ticket will then be related to the main Migration ticket.
- All communication with the vendor, for the project, will be tracked in this related ticket. All project movement, communiation between GZ Teams, updates, date files, and meeting dates will still be placed in a private note in the main Migration ticket for the Onboarder and Migrations team.
- The purpose of the related Paragon- (Tenant Name) ticket is to allow visibility on the vendor communications for all RE Integrations staff. The related Paragon- (Tenant Name) ticket will remain In Progress until the full integration is turned on and completed. The RE Integration point of contact for the project will be the Assignee on the related Paragon- (Tenant Name).
Data Process: Integration Specialist requests RETS feed credentials from Black Knight. We will pull down the data from RETS to populate their tenant in GrowthZone.
-
Ensure that they have connected with Black Knight on the costs associated with turning on the integration as well as confirmed they have signed the contract needed.
-
Confirm whether or not they have a feed from BK to their lockbox.
-
Integration Specialist will request RETS feed credentials and the mapping for vendor codes for Office and Agent Types to display values (this will be used to create the mappings in the Real Estate Settings)
- Timing of Integration: File-based that runs every 15 minutes. 7a-12 midnight for changes.
Outlined process for other integrations that may be occurring simultaneously:
M1 (if applicable) - https://helpdesk.growthzone.com/staff/kb/articles/2395-nrds-implementation-instructions
Lockbox (if applicable) -
Sentrilock https://helpdesk.growthzone.com/staff/kb/articles/2392-sentrilock-implementation-instructions;
SUPRA https://helpdesk.growthzone.com/staff/kb/articles/2391-supra-implementation-instructions
STAGING| DATA REVIEW
- Once the data has been pulled from Paragon and all other integrations, the Integration Specialist will create a staging database.
- Verify the Import Feature Settings are on. Setup -> Import Features
- Verify in the Setup -> Real Estate Integrations -> MLS Tab that Paragon is selected as the MLS.
- Once all data sources are obtained, and the Staging Database is created, the Integration Specialist will move the ticket to In Review for the Onboarder to move to Migrations when ready.
Once the Staging data has been imported by Migrations, it should be reviewed by Onboarding in conjunction with Platform Integrations and the Customer to ensure that the data was being imported correctly.
It is best to do a quick check to ensure all the data was imported properly.
-
Go to Setup>Integrations>Real Estate Settings>MLS Mappings and ADD values for Status, Agent & Office Type, and User Classes
- Office and Agent Types should have been provided by Black Knight
- Statuses are the same for all customers
- Y=Active (Office ONLY)
- A=Affiliate
- B=Board ONLY
- C=Commercial
- F=Staff
- M=MLS and Board
- N=Nonmember/Inactive for Office
- S=MLS Only
- User Classes are the same for all customers
- 0=0
- 1=1
- 2=2
- 3=3
- 4=4
- 5=5
- 6=6
- 7=7
- 8=8
-
Primary User Board is not used very often and was added for Rockford when they were going to come on
GZ-19220: BlackKnight MLS - additional Office Field CLOSED
-
-
Go to an Office and an Agent with BK data
-
Click Edit in the MLS Information to review the data and make sure that all key fields are populated (status, type, security, etc.) per the vendor requirements.
-
Sometimes Conversions will miss a step in the process where the data is visible when viewing the Real Estate tab, but when you click on the Edit pencil to view the information the data isn’t populated. Conversions should be notified and they will fix the issue.
-
The goal for testing is to provide Black Knight with a complete build file with all the active Agents & Offices for the Association. Black Knight will then use this data to complete their build in their test site. This should be done once data has been reviewed and confirmed ready.
PROVIDING A BUILD FILE
-
Double check that the GrowthZone Real Estate API has been setup by Conversions
Go to Setup>Applications>API Key Permissions ***If this is not a visible option in Setup, then the API module needs to be added via tenant settings.
2. Add Real Estate Settings
-
Go to Setup>Integrations>Real Estate Settings
-
Select “Sync to MLS” and put yesterday’s date for MLS Go Live
-
Select “FTP over SSH” for Transfer Mode
-
Server = http://mlsuploads.paragonerels.com
-
Path = Test
-
User Name = growthzone
-
Password = ^r)8M~w.gS0{GbO]k^y{
-
SAVE
4. Ensure tenant settings were received in IIT| Staging https://realestate.growthzonepreview.com/
-
Go to Message Types>GZ Tenant Settings>Find tenant
5. Force Kafka: Go to Setup>GrowthZone Staff Only Tools>Kafka Utilities>Force Changed Contact Kafka
6. Files will need to downloaded from Staging IIT and should be emailed to Black Knight (Gary Gorman & Steve Price) for review
- Allow for 2-3 days for processing
- gary.gorman@bkfs.com
- Steve.price@bkfs.com
STAGING| TESTING - Round Two
Once Gary or Steve has confirmed that the build in their test environment has been completed on their side, then the customer will need to create a test Agent & Office record to validate the build was set up correctly.
8. Customer creates one or two TEST Office & Agent records
- Download the office/agent files from Staging IIT and email Black Knight (Gary & Steve) informing them the customer has created test records
-
Gary will load the data into their test site and confirm the load was successful
-
Send the customer an email with the BK test site url (login with their live BK credentials) so that they can review that the test records were created successfully
9. Customer modifies test records: Then have the customer go to GrowthZone Staging and do a few modifications to the test records.
-
Download the office/agent files from Staging IIT and email Black Knight (Gary & Steve) informing them the customer has made modifications to the test records
-
Gary will load the data into their test site and confirm the load was successful
-
Send the customer an email with the BK test site url (login with their live BK credentials) so that they can review that the modified records were updated correctly
-
IF the customer confirms everything looks good, testing can be done. If they want to continue to test, follow the same process until they are comfortable.
10. Once testing has been completed: email Steve Price requesting the live folder path for the customer (do not include the customer on the email as Steve prefers it that way). Steve.price@bkfs.com I am not sure if the Folder path will end up being the same or different from the testing one.
11. Turn off Sync - after testing is completed, turn off the sync by going to Setup>Integrations>Real Estate Settings>remove sync checkbox & save
***No Friday work. Roughly 2 Business days would be the max.
GO LIVE
Black Knight will only 'go live' Mon.-Thurs, coordinate between Association, GrowthZone, and Black Knight on confirming the date & time.
-
Gary will do the implementation and needs at least a 2-day notice to move the build to production.
-
Double check the API Key Permissions for GrowthZone Real Estate is assigned: Setup>Applications>API Key Permissions
-
Delete GrowthZone Real Estate Webhook: Setup>GrowthZone Staff Only Tools>Web Hooks>delete Web Hook used during conversions and DO NOT Add Real Estate Web hook
-
Go to Setup>Integrations>Real Estate Settings and add MLS Mappings for Agent & Office Type, User Class, and Statuses
-
Got to Setup>Integrations>Real Estate Settings and check the “Sync To MLS” box and set the MLS Go Live date & time. Remember to set the time for at least 2hrs from the time you are completing this to allow for all contacts to get to IIT. For example, if it is 8:00 AM set the go live time to 10:00 AM.
-
The Server, UserName, and Password are the same for all GrowthZone customers. Save.
Transfer Mode: FTP over SSH
Server: mlsuploads.paragonrels.com
User Name: growthzone
Password: ^r)8M~w.gS0{GbO]k^y{
Path: Use the folder path provided by Steve
-
Go to Setup>GrowthZone Staff Only Tools>Kafka Utilities>Force Changed Contact Kafka
Troubleshooting Tips & Tricks
- Emails populating as Null in Black Knight: Found that if an Office or Agent doesn't have an email that has been set as default, when pushing over to Black Knight/Paragon it will be set to NULL.
Canada Customers
- CREA_ID: This ID number should be added under the account number. Also should be added as a Black Knight custom field.