arrow-left Back to Announcements
DATE:
AUTHOR:
The Cotality Title Order Management team

Order Management Production Release – January 21, 2026

DATE:
AUTHOR: The Cotality Title Order Management team

The Order Management Production release scheduled for January 21, 2026, includes several key updates. Below are the details of what's included in this release and how it supports our ongoing efforts to improve system performance and user experience.

Production deployment will begin at 10:00 PM CDT and is expected to conclude by 4:00 AM CDT.

During this deployment window, you may experience intermittent connectivity issues. If so, please wait 5-10 minutes and then try again.

Don't forget to subscribe to receive notifications when new release notes are posted.

Platform Enhancements

  • Add Funder to the UpdateUsers XML and Consider Auto Create Settings When an UpdateUsers XML is Received (17181): We have updated our UpdateUsers XML handling to include the Funder role and to respect Auto Create settings when an UpdateUsers XML is received. This ensures the Funder is captured accurately, and that Users are automatically created or updated according to the configured Auto Create rules—reducing manual setup and improving data consistency.

  • Add Funder Role to Title Order Entry Screen (OM-16466): To enhance role-based communication and order details, we have added a new Funder role to the Title Order Entry page in both OM UI and EPC. This allows users to capture and manage Funder information directly within the order workflow.

  • What's New:

  • — Funder Field in Client Information Section:

  • —— A new field labeled "Funder:" has been added under Closer in the Client Information section.

  • —— Supports multi-function behavior:

  • ——— Free-form text entry for email addresses.

  • ——— Dropdown list of Client's Users with the Role Type Funder.

  • ——— Displays the selected User's Name when chosen from the dropdown.

  • — EPC Enhancements:

  • —— The funder field is pre-populated with data from the originData payload when available.

  • —— Field remains editable for updates or corrections.

  • —— Email address included in Order Options to DG (funderEmail)

  • — Where to Find It:

  • —— OM UI: Title Order Entry screen under Client Information section.

  • —— EPC: Title Order Entry page with editable Funder field populated from originData.

  • — Benefits:

  • —— Improves visibility and communication by capturing Funder details upfront.

  • —— Reduces manual follow-up by including the Funder email in downstream processes.

  • —— Enhances flexibility with both free-form entry and user selection options.

  • Update Agents Popup and Status Panel for Client-Added Agent Users (16851): To simplify status handling and improve clarity when a Client adds a new Agent User, we've updated the Agents Popup and Order Status Panel to display a single, clear status.

  • What's New:

  • — Status Updates:

  • —— When a Client adds a new Agent User, the system now displays "New Agent User Added".

  • Where to Find It:

  • — Order Details Page → Agents Popup for updated status.

  • — Order Status Panel for streamlined status display.

  • Benefits:

  • — Eliminates redundant statuses for Client-added agents.

  • — Improves clarity for both Clients and Providers.

  • — Provides consistent messaging across UI components.

  • Update OAuth Functionality to Support JWK and Certificate Formats (OM-17083): To improve flexibility in token validation, we have enhanced OAuth functionality to dynamically support two public key formats: JWK (JSON Web Key) for external integrations and X.509 Certificate for internal integrations. This update ensures seamless authentication across different environments and reduces configuration overhead.

  • What's New:

  • — Dynamic Public Key Format Support:

  • —— Automatically detects whether the incoming public key is in JWK or Certificate format.

  • —— Routes to the appropriate validation logic without manual intervention.

  • — New Feature Toggle:

  • —— Added OAuthFeatureFlag in the ApplicationSetting table to enable or disable OAuth functionality.

  • — Where to Find It:

  • —— Configuration for enabling/disabling OAuth is available in the ApplicationSetting table.

  • —— Public key validation occurs during token verification for both internal and external endpoints.

  • — Benefits:

  • —— External Integrations: Supports JWK format for secure token validation.

  • —— Internal Integrations: Continuous support for X.509 Certificate format without disruption.

  • —— Improved Flexibility: Dynamic detection eliminates manual configuration.

  • —— Enhanced Transparency: Logging provides traceability for audits.

NOTE: In INT environment, you can update ApplicationSetting to switch between internal and external endpoints for testing. In higher environments, only external endpoint testing is required.

  • Misc Adjustments to Update Agents Popup and Status Panel (17084): To improve clarity and usability in the Order Details view, we have made several updates to the Agents Popup and Order Status Panel when a Provider adds a new Agent User.

  • What's New:

  • — Status Panel Updates:

  • —— Updated status text from "New Agent User Request" to "New Agent User Requested."

  • —— Updated icons for this status:

  • ——— The green checkmark now appears first.

  • ——— Red X replaces the previous red circle with a line through it.

  • — Agents Popup Enhancements:

  • —— Added Agent Email Address and Phone Number between Agent Name and Status for better visibility.

  • — UI Adjustments:

  • —— Removed the Resend Order button from the Client's toolbar on the Order Details page.

  • —— Updated Agents button icon to be blue with a transparent background on Client view.

  • Where to Find It:

  • — Order Details Page → Agents Popup for email and phone details.

  • — Order Status Panel for updated status and icons.

  • — Toolbar for removal of the Resend Order button.

  • Benefits:

  • — Improves clarity of agent-related status updates.

  • — Provides quick access to agent contact details.

  • — Enhances UI consistency and reduces unnecessary actions for Clients.

  • Add Decline Confirmation Page for Email Providers (17185): To enhance user experience and maintain consistency with order management workflows, we have introduced a new Decline Confirmation Page for Providers accessing an order via the email invitation link.

  • What's New:

  • — Decline Link Expiry:

  • —— The decline link in the email now expires after 24 hours, matching the Order URL expiry time.

  • — New Decline Confirmation Page:

  • —— Page Heading: Decline Order

  • —— Confirmation Text: "Are you sure you want to decline this order? This action cannot be undone, and you will no longer have access to this order."

  • —— Comments Box: Allows the provider to supply an explanation as to why an order is being declined.

  • —— Action Button:

  • ——— Continue → Sets order status to Declined

  • ——— Displays confirmation message: "Thank you. This order has been declined, and we have notified the Lender."

  • Increase Length of County Name in Title Order Entry Page to 100 Characters (OM-17275): We extended the County field in both EPC and Order Management (OM) user interfaces to support up to 100 characters. The full county name will now be displayed completely on the Order Detail page, improving visibility and accuracy for longer names.

  • Impact:

  • — This change accommodates the new Connecticut planning regions, which have longer names than traditional county names, ensuring accurate display and reducing truncation issues.

  • Increase Length of County Name Field in NewOrder XML Inbound and Outbound to 100 Characters (OM-17276): We increased the length of the County element to accommodate up to 100 characters in both inbound and outbound NewOrder XML. Previously, this field was limited to 30 characters in the OrderProperties table.

  • Impact:

  • — This change ensures compatibility with longer county names, including the new Connecticut planning regions, and improves data accuracy across integrations.

  • Update NewOrder XML to Include DU Case File ID, LPA Key, Eligibility Code, and Title Waiver Elements (16477): Updated the NewOrder XML schema to support Title Waiver functionality. The following changes have been implemented:

  • New XML Elements Added:

  • — DUCaseFileID

  • — LPAKey

  • — EligibilityCode

  • — TitleWaiverAcceptance

NOTE: Clients who would like to participate in the Title Waiver program should contact their CSM to have this functionality enabled on their accounts.

  • Add Fields to Designate When Mutual TLS is Required on Outbound Messages (OM-17397): To meet security requirements for certain lenders, we've enhanced outbound communication capabilities to support Mutual TLS (mTLS) for client integrations. This ensures secure, certificate-based authentication for sensitive data exchanges.

  • New Configuration Fields:

  • — Added fields in Client Admin to indicate when mTLS is required for outbound messages to a client system

  • mTLS Support for Outbound Communication:

  • — When enabled, outbound messages from CCOM to the lender system will:

  • —— Use Mutual TLS handshake for authentication

  • —— Validate both client and server certificates for secure communication

  • Benefits:

  • — Enhanced Security: Meets lender requirements for certificate-based authentication

  • — Flexibility: Allows per-client configuration without impacting other integrations

Issue Resolutions

  • Duplicate Email Notifications Sent to Title Providers (16847, 16845): We resolved an issue where Title Providers were receiving duplicate Title Order and Title Order Note email notifications. This fix ensures that only a single notification is sent for each event.

  • LenderReferenceID Not Appended to Commitment XMLs (17065): We resolved an issue where the LenderReferenceID was not appended to the Commitment XML when sending it back to the lender. This fix ensures that the XML now includes the correct reference ID as expected.

  • Incorrect EPC Mapping (17202): This fix addresses an error in the default mapping for the EPC setup, where the fields "For Credit To" and "Further Credit To" were incorrectly swapped between the title and escrow company. The mapping has been corrected so the "For Credit To" and "Further Credit To" data fields correctly populate EPC.

  • Fix: Loan Amount Value Displayed Incorrectly on Order Detail page (17320): We have resolved an issue where the Loan Amount value was not displayed correctly in the Order Details page. Previously, decimal values were being rounded up to the nearest dollar in the UI instead of showing the exact amount provided by the Client.

Please do not hesitate to contact your Client Success Manager with any questions. You can also reach out to the Cotality CX Team at ordersupport@closing.com or 866-256-7464.

Powered by LaunchNotes