OneCONNECT Hub v3.5

Deployed 12/10/2025

Introduced a process to remove oversized OC order messages from the queue to prevent delays. Previously, messages larger than 5–10 MB could slow down or block subsequent messages, risking missed order deadlines. The new process identifies large orders, pulls them from the queue, and schedules them for after-hours delivery. Strata engineers will be notified via Daily Order Checks, and clients will be informed of any delayed orders requiring immediate attention.
Revised Ampersand order confirmations in OneCONNECT now behave consistently with new orders. When sales users click “Confirm,” a message is automatically sent to Ampersand and registered in SpotCable. Previously, revised orders required manual confirmation in SpotCable even after clicking “Confirm” in OC.

OneCONNECT Hub v3.4

Deployed 7/30/2025

Provides the ability for the OneCONNECT database to process Ampersand orders built with Comscore Dentsu-Merkel proprietary data into the UI as expected with any other orders using Comscore data.
Database fix to resolve a bug in the OneCONNECT funnel filter functionality where orders with a blank AE field were incorrectly included when filtering by specific AEs. Will be visible to users once OneSUITE v 8.1.0 is in production.
Resolves an issue where in the database the officeid from Ampersand orders is null (edge case). Result was those order would not be visible in the OneCONNECT Inbox or an Object Reference Error was thrown. Orders will now open as expected.

OneCONNECT Hub v3.3

Deployed 11/11/2024

Work done in OneCONNECT database to change how orders are populated into the Inbox in particular, especially upon user click of All Records. Previously, regardless of filters already applied, in the background all records would be called when determining the orders to display. Then they would be filtered again. New behavior will start with the filtered list and call from there saving time in the process.
Work was also done to adjust the behavior when "All Records" is checked to make it behave more like the complementary call in OneTIM. This change will not be visible to users until OneSUITE v 7.9.0 has been released and deployed. Specific user documentation will be included with that release. Nothing is required to make this happen in the hub.

OneCONNECT Hub v3.2

Deployed 6/30/2024

Work done to improve OneCONNECT performance due to the increase of volume of orders now that the majority of Ampersand orders are processing through OneCONNECT. Work done is around archiving old hub data and orders based on and end date of four years ago or more. And optimizing the notifications job.

OneCONNECT Hub v3.1

Deployed 3/26/2024

Optimization of the PostFilter Method as it relates to order loading in OneCONNECT Inbox. Processing Ampersand orders through OC will lead to a huge increase in volume of orders. Represents Phase 1 of work to handle that additional volume without impacting performance.
Stratasphere Registry TradingpartnerContact (User syscode mapping) Properties will be correctly captured for Account Executive users who have left the company and come back.

OneCONNECT Hub v3.0

Deployed 7/18/23

Work to optimize OneCONNECT Order Notifications and Post Filter methods in order to improve performance in OneCONNECT due to the ever increasing volume of orders.

OneCONNECT Hub v2.9.1

Deployed 6/27/23

Work to migrate OneCONNECT hub from the old Strata STL data center to AWS.

OneCONNECT Hub v2.9

Deployed 4/19/23

Hub work to allow Ampersand orders and notifications to process through OneCONNECT.

OneSUITE v7.5.0 requires this version.
Ampersand redirecting syscodes to process through OneCONNECT instead of Gateway-to-TIM.

OneCONNECT Hub v2.8

Deployed 3/28/22

The Order Details screen will now display syscodes with the same CPE in one UI screen. OneSUITE v7.2 or higher is required.
Transactions between the buyer system and OneCONNECT will no longer fail due to the error "Order [X] does not have any outstanding makegoods." Previously, a makegood transaction (or similar activity) would complete, but the status failed to update. Additionally, more logging has been added to help with future troubleshooting.

OneCONNECT Hub v2.7

Deployed 1/19/22

The initial work to route Ampersand orders to OneCONNECT is now complete. OneSUITE v7.1.0 or higher is required. Please be advised that further development is required to complete this effort.
Unnecessary CRM fields have been removed from the database. These same fields were previously removed from the UI in OneSUITE v7.0.0.

OneCONNECT Hub v2.6.1

Deployed 10/25/21

Performance has now been improved when opening the OneCONNECT Inbox and applying filters. Also, OneCONNECT will launch more quickly when opened from OneTIM Order Details.

OneCONNECT Hub v2.6

Deployed 8/23/21

Orders built with Comscore data can now be processed. OneSUITE v7.0.0 or higher is required and has been released.

OneCONNECT Hub v2.5

Deployed 6/29/21

Name changes (e.g. married) will now be updated in the Registry sync job and correctly displayed in Eleven. Previously the sync job would revert back to the old name/email and a buyer had to select this name when sending orders.
New DARE Error codes have been added (per DARE specs 7.0 v21).
NCC labels have been updated to AMP. OneSUITE v7.0 or higher is required.
Orders that start in CRM D365 can now be linked to the OneTIM order number or the CRM Opportunity. OneCONNECT will maintain the connection between the order and the linked value. OneSUITE v7.0 or higher is required.
A new "Makegood Age" and "Modified Date" column have been added to the Inbox screen. OneSUITE v7.0 or higher is required.
The ability to partially import a revision when a buyer has made changes to past and/or current weeks has been added. OneSUITE v7.0 or higher is required.

OneCONNECT Hub v2.4.1

Deployed 4/25/21

Sending makegoods will now work correctly for orders with a pending revision and a null reference in the primary demo field (not visible in UI). Previously, these sent makegoods would fail, and an error notification email was provided: "There is an error sending this makegood. Please cancel and try again or contract FreeWheel Client Service using the Help link from the Main Menu." This issue was introduced in OC Hub v2.4.

OneCONNECT Hub v2.4

Deployed 4/19/21

The batch limit functionality will now include the MSO designation when creating batches. This issue was introduced in OC Hub v2.3 and caused some notifications to not be sent.
Special characters in AE email addresses will now be decoded to minimize duplicate users from being created in the database. Previously, orders with incorrectly mapped AEs could not be found in the UI.

OneCONNECT Hub v2.3

Deployed 2/23/21

The confirmation message sent to Eleven will now include total dollars and spots. This will ensure totals match between Eleven and OneCONNECT, and help FreeWheel triage discrepancies.
An Eleven Failure Message will now be sent to the buyer when the order's days or weeks do not match the flight dates. Eleven message: "Weeks/days sent do not match flight dates. Please contact Support with questions." Previously, this type of order (new or revision) caused incorrect data between SBMS, Eleven, and OneCONNECT.
Header comments in the DARE outbound makegood message will now include missed and added spots, as well as total spots and dollars. Also, Agency Line numbers will no longer be listed for makegood lines, as they lead to confusion. These updates simplify the message for Mediocean and will help with future trouble-shooting.

OneCONNECT Hub v2.2

Deployed 12/2/20

Create Makegood and Cancel Makegood outbound errors will now be listed in the Audit window and a detailed email notification will be sent to the AE/Assistant. To improve performance in the Order Details screen, the Date Filter functionality will now be handled in the OneCONNECT Hub and UI. OneSUITE v6.9.0 or higher is required.
The Hub will now check for active makegood transactions when processing a rejected makegood. This ensures crossing transactions correctly set the order State and Status in the UI.

OneCONNECT Hub Release Notes