Redirecting to default login.. Qualia Marketplace Integration
  1. Home
  2. Integrations
  3. Qualia Marketplace Integration
Searching...

Qualia Marketplace Integration

Contents

Overview

The Qualia Marketplace to Resware integration allows Qualia Core (“Core”) customers to place orders with Resware customers and other search providers that have implemented the Resware-to-Resware API, expanding the available customer base for these companies. This document demonstrates how to set up Resware to receive and fulfill search orders from Core customers. 

Read the one-sheeter overview.

Begin here: Contact Resware CSM.

Next: Complete the steps in this job aid.

Then: Test the integration. For assistance, contact Resware’s support team at support@resware.qualia.com.

Version History

VersionDateIDDescription
9.101/1/202248809Integration available

Webinar Demo

Enable the Office Option

Admin/General Setup/Offices

  • Edit the office using this integration.
  • Select the Web Services tab and enable the Resware to Resware Order Submission office option if it is not already enabled.

Create a Marketplace Client Partner

When an order is received from Marketplace for an unmapped client, “Marketplace” will be set as the client on the file. Using this generic Marketplace client will ensure that the Resware file is created for either new customers or customers that have not yet been mapped. Any files created with the Marketplace client should be modified by an admin to reflect the actual client, whose name will be in the notes on the file, and the customer should be mapped in Marketplace’s Resware admin panel to ensure that future orders from this customer reflect the actual client name. Please contact the Marketplace team to map additional clients.

The Marketplace partner will also be used to set up the Resware to Resware partner mapping and will need to be on each file where notes, documents, and search data will be sent to Marketplace. 

Admin/Partners

  • Click New.
  • Enter the Company Name as Marketplace. 
  • Set the Partner Type to Client and the partner type that will be associated with the Marketplace partner on each file (i.e. Integration Partner)
    • The client partner type is necessary because this partner will be used as the client on the file if the customer sending the order via Marketplace is not mapped.
    • The integration partner type is necessary so the partner can be set up in Resware to Resware.  This partner and partner type combination will need to be added to every file so data can be sent back to Marketplace.
  • Click Client Products and add the products that can be ordered through Marketplace.
  • Click XML Config and select Enable XML Transmission of Notes and Documents and Don’t Also Send Notes and Documents via Email. 
  • Make note of the System ID and provide it to the Marketplace team.
  • Click Save.

Create a Partner Employee

Admin/Partners

  • Highlight the Marketplace client partner created above and click New in the partner employee area.
  • Enter a First Name. 
  • Enter an Email Address. 
    • NOTE: This can be a “dummy” email address.
  • Check Primary Contact, which will set this employee as the primary contact by default when the partner is added to the file.
  • Check Enabled in the Website Access area, which allows the web/API services to be utilized.
  • Check Override Username and set the Username to Marketplace.
  • Click Generate to populate a Password. This will ensure company-specific password requirements are met. Make note of the password for use in the validation step. 
    • NOTE Contact support@resware.qualia.com if these credentials are changed so that they can be updated to ensure that the integration continues to function as expected.
  • Check Enabled in the Website Access area, which allows the web services to be utilized.
  • Enable the following services in Website Roles
    • Web Services: Access All Files for ResWare-to-ResWare Services (required to receive notes from Core)
    • Web Services: Add Documents
    • Web Services: Add Notes
    • Web Services: Order Placement
    • Web Services: Cancel Files 
  • In the Office Access area, check Access for the office that will be receiving orders from Marketplace.
  • Click Save.

Password Validation

Website

After a password is set or reset for a partner employee, the employee is required to enter a new password the next time they access the website. To ensure this integration is set up correctly, log into the company’s Resware website with the username and password created in the previous step, and create a new password  Make note of this password to use later in the Marketplace setup section.

NOTE: It may be beneficial to set the expiration date of this password on the partner employee setup for an extended period  Check with company-specific password security protocols to verify this will be acceptable or have a reminder in place to update this password as needed to ensure this integration’s service will not be interrupted.

Add XML on Products

The Resware XML package must be added to each product that will use this integration.

Admin/Action Lists/Product Types

  • Click Add and select the Resware XML package. 
  • Click OK.
  • Click Save, Close. 

Add an Action to Automate Sending Search Data and Documents

Admin/Action Lists/Email Templates 

  • Click New and enter a Template Name like Send Search Documents to Marketplace.
  • Select Automatically send (no user interaction) in the Send Action drop-down menu.
  • Check Attach by Document Type.
  • Click Select Doc Types and select the documents to send, such as Search Package.
  • Check Attach Most Recently Created Document Only to ensure that only the latest version of the document types on a file is being sent.
  • Check Transmit via XML.
  • Click Save.
  • Click on Select to open the Send To panel and select the Client partner type.
  • Click Save.

Admin/Action Lists/Action Groups  

  • Highlight the group where the search order fulfillment actions exist. 
  • Click Edit Actions.
  • Click New Global Action and enter a Name like Send Completed Search Data to Marketplace.
  • Click Add in the Completing Requires Documents area and select the document(s) needed for the email template created above.
    • NOTE: Adding documents as required to the action will prevent the action from being completed unless the required documents are on the file.
  • Click Add.
  • Click Add in the Completing Email Templates area and select the email template created above.
  • Click Add.
  • Click Save.   

  • Check Dynamic.
    • NOTE: An affect must be added to the action in the workflow to create this action. 
  • Select a Coordinator for the start and complete of the action.
  • Other options, such as Auto-start when Added to File or making the action partner specific, may be utilized depending on what is needed to make the flow of the action group work for each customer.
  • Click Save.
  • Highlight the action that was just added, and click Edit Affects. 
  • In the Complete Task Marked Done Affects section, click Add.
  • Select the following in 5 – Marking Done Sends XML:
    • Select Resware: Send Search Data from the XML drop-down menu.
    • Select the Client partner type from the Send To: drop-down menu. 
  • Click Save.

Add Action Event for Completed, Canceled, and Revised Orders

Admin/Action Lists/Action Events

  • Click Add.
  • Create an action event for completed orders (this example uses
    Marketplace Completed Order Event).
  • Click Add.
  • Create an action event for canceled orders (this example uses 
    Marketplace Cancel Order Event). 
  • Click Save.
  • Click Add again. 
  • Create an action event for revised orders (this example uses Marketplace: Order Revision Requested). 
  • Click Save. 

Add an Action for Completed Orders

Admin/Action Lists/Action Groups

  • Select the Action Group that will be used to process orders from Core. Click Edit Actions.Click Add Action.Select the action that will be used for notification when an order is completed. If one does not exist, it must be created.Click Edit Affects.In the Complete Task Marked Done section, click Add.
  • In the 5 – Marking Done Sends XML section, select:
    • XML: ResWare: Send Action Event
    • Send To: Integration Partner
    • Action Event: Marketplace Completed Order Event
  • Click Save.

Add an Action for Canceled Orders

Admin/Action Lists/Action Groups

  • Select the Action Group that will be used to process canceled orders from Core. 
  • Click Edit Actions.
  • Click Add Action.
  • Select the action that will be used for notification for when an order is canceled. If one does not exist, it must be created.  
  • Click Save. 
  • Click Edit Triggers.
  • Click Add.
  • Set the External Trigger to XML Received Action Event, then select the action event created above that will be used to notify a user when the file is canceled. 
  • In 1 – Marking Done Creates Action, select the group and action to use to notify a user when an order is canceled. 

Add an Action for Revision Requests

When a Core customer receives a search order, they can either accept or reject the order. In instances where an order needs to be revised, a status of “Revision Needed” is sent from Marketplace to Resware.

Since a revision could be requested after the Resware file’s status is set to “Closed,” it is recommended that the action used to notify a user if a revision is requested be set to displayed regardless of the file’s status.

Admin/Action Lists/Action Groups

  • Select the Action Group that will be used to process revision requests from Core. 
  • Click Edit Actions.
  • Click Add Action.
  • Select the action that will be used for revised orders.
  • Click Save.
  • Click Edit Triggers.
  • Click Add.
  • Set the External Trigger to XML Received Action Event Completed, then select the action event created above that will be used to notify a user when a revision is requested. 
  • In 1 – Marking Done Creates Action, select the group and action being used to notify a user when an order revision is being requested. 
  • Click Save. 

NOTE: For information about working with actions, please refer to this job aid. 

**Please see further below in job aid for how the Revision Requested Action works on the Qualia Core side and within Resware. **

Resware to Resware Partner Mapping

  • Click Add. 
  • Click Search and select the Marketplace client previously created. 
  • Enter the Username and Password provided by support@qualia.com during the onboarding phase.
    • NOTE Contact support@resware.qualia.com if these credentials are changed so that they can be updated to ensure that the integration continues to function as expected.

Search data

  • Select Search Data from the Service Type drop-down menu. 
  • Enter the following URL: https://resware-mediator.qualia.io/ReswareWebServices/ReceiveSearchDataService.svc 
  • Select v2 as the Service Version.
  • Click Add in the Lien Type Mapping area.
  • Select a Lien Type, and assign the respective Remote ID from the list below. Core has the following lien types available; regardless of how the lien types are named in Resware, they must be mapped to one of the five lien types in Core.
    • Mortgage = 100
    • Deed of Trust = 101
    • Release of Mortgage = 102
    • Assignment = 150
    • Subordination = 160
  • Click Save.
  • Repeat the above steps for each lien type. 
  • Alternatively, click Add All and then edit each lien type to set the remote ID.

NOTE: To send the full language from Resware to Core for a lien type, use a lien type that does not exist in Core (e.g.
RemoteLienTypeID = 500).

  • Click Add in the Requirement Type Mapping area. 
  • Select a Requirement Type, and enter 200 for the Remote ID.
    • NOTE: Core has one type for all requirements (ID = 200); all requirement types from Resware will be added to the same Commitment Requirements field in Core. Requirements that are mapped to a Core requirement type will be sent as encumbrances, and the required data fields are populated based on the information from Resware. The language in Resware is not sent to Marketplace; Core’s default language is used.
  • Click Save.
  • Repeat the above steps for each requirement type.
  • Alternatively, click Add All and then edit each requirement type to set the remote ID.  
  • Click Add in the Easement Type Mapping area.
  • Select an Easement Type, and enter 250 for the Remote ID.
    • NOTE: Core has only one type for all easements and restrictions (ID = 250); all easement and restriction types will be added to the same Commitment Exceptions field in Core. The language in Resware is sent to Core for all easements.
  • Click Save.   
  • Repeat the above steps for each easement type. 
  • Alternatively, click Add All and then edit each easement type to set the remote ID.
  • Click Add in the Restriction Type Mapping area. 
  • Select a Restriction Type, and enter 250 for the Remote ID.
    • NOTE: Core has only one type for all easements and restrictions (ID = 250); all restriction types will be added to the same Commitment Exceptions field in Core. The language in Resware is sent to Core for all restrictions.
  • Click Save.
  • Repeat the above steps for each restriction type. 
  • Alternatively, click Add All and then edit each restriction type to set the remote ID.

Note/Document

  • Click Add in the Document Type Mapping area.
  • Select a Document Type.
    • NOTE: It is not necessary to change the Remote ID; documents sent to Core do not need to be mapped to a Core ID. All documents that are sent will be attached in the Title Search Document section in Core.
  • Click Save.
  • Repeat the above steps for each document type.
  • Alternatively, click Add All and then remove the document types that will not be sent to Core.

Action events

  • Select Action Mapping from the Service Type drop-down menu.
  • Enter the following URL: https://resware-mediator.qualia.io/ReswareWebServices/ReceiveActionEventService.svc   
  • Click Add in the Action Event Mapping area.
  • Select the Action Event that will be used to send search order requests back to Core.
  • Enter “order_completed” in the Code field. 
  • Click Save.
  • Click Add again.
  • Select the Action Event that will be used when an order revision is requested from Core.
  • Enter “order_revision_requested” in the Code field.
  • Click Save.
  • Click Add again.
  • Select the Action Event that will be used to process canceled orders from Core.
  • Enter “order_cancelled” in the Code field. 
  • Click Save.

Qualia Marketplace Admin Setup

Once the Resware setup has been completed, the following information will need to be set up in Marketplace, under the Resware tab. Additionally, certain fields will need to be provided directly to the Core admin before the integration can be used.  

Resware product mapping

  • Select the Resware tab on the Manage Order page in Marketplace. 
  • Click Add Product Mapping. 
  • Select a Qualia-Side Product from the dropdown.
    • Select Purchase. 
    • Enter the equivalent Resware-Side Transaction Type ID for a purchase.
    • Enter the equivalent Resware-Side Product ID for a purchase.
    • Click Add Mapping. 
  • Select a Qualia-Side Product from the dropdown.
    • Select Refinance. 
    • Enter the equivalent Resware-Side Transaction Type ID for a refinance.
    • Enter the equivalent Resware-Side Product ID for a refinance.
    • Click Add Mapping. 

Resware client mapping

  • In the same Resware tab as the previous step, click Add Customer Mapping. 
  • Select a Qualia-Side Customer from the dropdown. 
  • Enter the System ID (previously noted from the Resware client partner setup) in the Resware-Side Customer ID field.
  • Click Add Mapping. 
  • Repeat for every client that will place an order through Marketplace. 

Core admin setup

  • Provide the following information directly to support@qualia.com.
    • The previously noted Marketplace client employee username and password.
    • The Office ID for the office that will use the integration.

Examples on a File

When a Core customer submits a search order request to an integrated Resware vendor, a file will automatically be created in Resware. The Resware vendor will then be able to send back search data, documents, and notes to fulfill the request. When the search data has been sent to Marketplace and the request has been fulfilled, the action to confirm that the order has been fulfilled must be completed.

NOTE: The search data must be sent before the …Completed… action event is sent; the …Completed… event is used to push the search data from Marketplace to Core.

Search data 

  • To process and return search data from Resware, go to the Search Data tab of the newly created file, and complete the following fields, as applicable:
    • Parcel ID
      • This will map to the “Parcel IDs” field in Core.
      • If there are multiple parcel IDs, separate them with a comma so that each respective parcel ID is populated in its own field. 
      • The order in which the parcel IDs are entered in Resware is the order in which they will display in Core. Example: 12345, 56789, 54321 will display as Parcel ID #1 12345, Parcel ID #2 56789, and Parcel ID #3 54321.
    • Commitment Effective Date 
      • This will map to the “Search Effective Date” in Core. 
    • Vesting 
      • This will map to the “Title Vesting” field in Core. 
    • Legal
      • This will map to the “Legal Description” field in Core. 
    • Interest
      • This will map to the “Estate Type” field in Core. 
      • NOTE: Entering a value in the “Leasehold” field in Resware will cause the value to be populated in Core with a hyphen, e.g. “Leasehold – Estate at Will.”  
    • Liens & Requirements
      • The liens will map to the “Outstanding Mortgage” section in Core. Liens will populate in Core in the same order they are entered in Resware. 
      • The requirements will map to the “Commitment Requirements” section in Core.
      • NOTE: Lien types must map to one of the five Core types previously identified. 
    • Easements & Restrictions
      • These will map to the “Commitment Exceptions” section in Core. 
  • Chain of Title 
    • These will map to the “Deeds” section in Core.  
  • Once all search data is entered in Resware, go to the XML tab, select Resware: Send Search Data – Marketplace, and click Send to manually send the search data to Marketplace, or complete the action that was set up to automatically send this information.
    • NOTE: If any changes are made to the search data and it is resent to Core, all search data values in Core will be overwritten with the data that is in the updated response.

Title search documents 

  • To process and return search documents from Resware manually, go to the Documents tab. 
  • Attach or create the documents to be included. 
  • Select the documents that should be sent, and click Send. 
  • On the Send Information panel, select the client and any other necessary contacts.
  • Click Send to transmit the documents to Core. 
  • Any documents that are sent will display in the Title Search Documents section in Core.
    • NOTE: Only document types that have been properly mapped in the Resware to Resware partner mapping will be sent. 
  • Documents can also be sent automatically by completing the action that was set up to send the documents to Core. 

Notes

  • To send a note from Resware to Core, go to the Notes tab. 
  • Click New.
  • Enter the note details on the Note panel. 
  • Click Save, Send to transmit the note to Core. 
  • On the Send Information panel, select the client and any other necessary contacts.
  • Click Send to transmit the note to Core. 

File close out 

  • Once all search data and applicable documents have been sent back to Core and the action created above to confirm that the order is fulfilled has been completed, the Core file will automatically update to a Submitted status. 

How Revision Requested Works:

When a Resware user sends Search Data information from Resware through the Qualia Marketplace integration, the Qualia Core user can request a revision on the Qualia Marketplace side. When they request a revision, this will fire off the Revision Requested Action Event within Resware so that users will know that a revision to the information sent to Qualia is being requested.

How the Revision is requested on the Qualia Marketplace side:

When Search Data is received on the Qualia Marketplace side, the Qualia Core user can either choose to Add Data and Pay or they can select Reject Order. If they select Reject Order, the user has several options to choose from- the top 4 options are used for Revision Requested:

When the Qualia Core user selects one of the four options to request a revision, the Qualia Core user will see Revision Requested in the top right-hand corner of their order:

Once Resware receives the request, a note will be entered on the XML tab stating: “Action Event received successfully on remote file XXXX (ID:xxxx) PartnerCompanyID xxx. ActionEventCode: order_revision_requested“:

And the Action Event order_revision_requested will be added to the Resware file on the Actions tab:

Updated on October 19, 2023

Need Support?

Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support

Submit a Support Request