OneSUITE Release Notes

Avatar
FreeWheel
Follow

OneSUITE v8.2

Released 8/7/2026

OneTIM

  1. Notifications will now be sent to assistants for orders in Reject or Rework Status as part of the Select AEs for Notifications functionality.  AEs can be selected by following this path - OneSUITE Home > Select AEs > Select AEs for Notifications (OneCONNECT, Rejected/Rework Order Status)
  2. OneTIM WebService (SaveOrder) call has been updated to allow LIFT App to save priority codes.
  3. Reset eRevisions Flag button has been added to OneTIM Order Details screen. Previously it was only visible in the OneTIM Order Status screen. Button will only be visible to users with proper permission which must be assigned via User Profile in Setup. Matches current functionality for Reset eRevisions flag in Order Status screen. 
  4. The GetCopyGroupsByClientId method is not implemented in the Setup Cache Host service by design. The attempt to call GetCopyGroupsByClientId in the Setup Cache Host service always fails and then the logic retrieves the data from the Setup web service. This ticket is to suppress the errors logged in this scenario so they don't bloat the OMT log files.
  5. Updated the logic that saves LegacyTrafficSystem ExportIDs to handle when basedon traffic systems are not included when calling the POST methods for Advertisers, Agencies & RepFirms.
  6. Contact information can now be updated through SOAP and Web APIs. Previously, contact updates in OneSUITE could only be made through CRM.  Note: Updates made via the APIs are not currently captured in the Audit Trail. Support for Audit Trail tracking is planned for OneSUITE v8.3.0.

OneSUITE Rates

  1. Fixed a bug in OneSUITE Rates where rate card matching did not account for start or end date alignment with the buy line. Updated logic now selects a rate card line when its date range falls within the buy line range and covers more than half of it. As a result, the correct calculated rate is returned instead of the default $999.99.
  2. Fixed a bug where users could not update Start or End dates on a Draft or Activated Rate Card using the calendar icon. Workaround was to enter dates manually. 

 

OneSUITE v8.1.1

Released 11/11/2025

OneSUITE Rates

  1. Rate card values will now only apply to lines with scheduled units. Previously, OneSUITE Rates attempted to apply rates to all lines, which impacted performance and could prevent large orders from opening. With the “Hide 0 Unit Lines” option enabled, zero-unit lines are now skipped during rate application.
  2. A new “Load Rate Card” button has been added to the Rate Card list screen. To open a rate card, highlight it and click “Load.” This replaces the previous method of double-clicking the rate card name, which was inconsistent and confusing. A “Loading” message now appears and remains visible until the rate card is fully opened.
  3. Fixed an issue where large rate cards sometimes continued loading in a loop after import. Large rate cards now load as expected.

  4. Improves performance of the GetRates WebService calls to improve performance and allow large rate cards to open without issue. 

     

OneSUITE v8.1

Released 8/12/2025

OneTIM

  1. Work undertaken based upon the collaboration between CA & FW engineering teams to improve performance in OneTIM. Detailed solutions are captured at the individual ticket level.
  2. Comscore-Dentsu Merkel Audience Currency Support:
    • Audience Currency Support: Orders using Comscore-Dentsu Merkel proprietary demo data can now be processed in OneSUITE like other Comscore demo-based orders.
    • Demo Code Display: VIEW, OneCONNECT, and OneTIM will display the 5-digit demo code as received from buyer systems.
    • Estimate Adjustments: Impressions and Ratings can be modified to update estimates as needed.
    • OneCONNECT Workflow: Orders from Source Ampersand using proprietary demos are supported through the full workflow to OneTIM.
    • Integration Limitation: Orders submitted directly from Eleven or DARE require additional development for processing.
  3. A new option has been added under the "Hide Schedules" filter in the OneTIM Order Status funnel filter. This enhancement allows users to filter orders based on how recently they were updated, specified in hours (up to a maximum of 2160 hours or 90 days).  This feature is especially useful for bot-driven order management, enabling bots to focus on recently updated orders for improved efficiency.
  4. When a user is authenticating as ComcastLIFT app, GetOrdersByClient can now be successfully called. Engineering request, NOT user facing.
  5. Updated WebAPI POST methods to save Export ID to all entities that have IDs - Advertiser, Agency, Rep Firm. Critical to Phase II of Salesforce integrations. Engineering request, NOT user facing.
  6. Removes the logic to assign a default Agency <none> to and Advertiser in CRM in preparation for Salesforce integration. Engineering request, NOT user facing.
  7. Resolved a bug in the OneTIM WebService SaveOrder call where contracted monthly totals were not being saved. Now if contracted monthly totals are passed when creating an order using the WebService, those totals will be captured on orders in the UI. Engineering request, NOT user facing.
  8. OneTIM Configuration Setting updated so Order Comments BOT button shows/hides comments from users whose Display Name contains the BOT Identifier.
  9. The OneTIM Order Status page now includes a text box for entering a single order number, enabling direct navigation to that order in Order Details. This streamlines access and improves performance by bypassing the need to search through all displayed orders.
  10. Updating the Knowledge Base link requires admins to manually make the change. Update the Knowledge Base link in the Setup -> Configuration -> Applications page to point to https://freewheel.zendesk.com and then verify it's been updated via Test button and/or Hamburger Menu Help selection.  Clicking the Help button in OneSUITE will connect users directly to Zendesk where they can enter support tickets or search the Knowledge Base.

Zone One Source

  1. The Insertability End Date in ZOS is now editable, ensuring smoother processing for orders including networks with defined end dates crossing flight dates. New functionality highlights order lines crossing the end date in Order Details, requiring users to switch to an insertable network before saving or exporting.  This only applies only to OneSUITE schedules; VIEW orders remain unaffected. However, when impacted orders are imported from VIEW, end date warnings will display again requiring users to switch to an insertable network before saving or exporting.  IMPORTANT: This feature is only valid for networks ended across all syscodes. End dates for networks that are syscode specific must still be handled through scripts. 

OneCONNECT

  1. Resolved a bug in the OneCONNECT funnel filter functionality where orders with a blank AE field were incorrectly included when filtering by specific AEs.
  2. Resolved issues in Makegood Reports sent from OneCONNECT that resulted in errors when sent to Ampersand’s buyer system.
    • Big Ten Network now consistently appears as "BTN" in both Missed and Makegood sections, regardless of regional network on which spots air. No manual or user intervention required. (Will work like it already does for Eleven & DARE orders.)
    • Character limits added: Comments (500) and Program Name (250) to align with Ampersand’s system requirements. No manual or user intervention required. 

OneSUITE Rates

  1. Rate card list will now automatically refresh upon save to changes to any rate card. Previously, it was possible saved changes did not always automatically refresh the rate card list. As a result it was possible to unintentionally overwrite an active rate card. 

 

OneSUITE v8.0

Released 4/1/2025

OneTIM

  1. Research required to fix the BTN and character limit issues in the OneCONNECT Makegood Report for Ampersand. Fixes will be implemented in OneSUITE v 8.1.0.
  2. Updating the Traffic ID field in OneTIM Order Details is now permissions-based. To grant permission, enable "Edit Traffic ID" in the Order Details tab in the user's Profile. Previously, anyone could update the field, potentially causing downstream sync issues.

  3. OneCONNECT Notifications will now be delivered based on the new functionality in version 7.9.0, allowing users to choose notifications based on AE selection. Assistants will continue to receive notifications based on AE assignment in OneSUITE Setup, as per the original OC Notifications functionality. 

OneSUITE Rates

  1. Rate cards of any size will import successfully with minimal processing time.
  2. Rates to can now be applied to order lines by matching on exact daypart day or exact daypart time.

  3. Rate card details management workflow has been updated as follows:

    • When copying lines, the copied lines will now be numbered correctly and selected. 
    • Mass editing no longer requires unsaved changes to be saved prior to mass editing newly copied lines, any unchanged lines, or reselected lines from a previous unsaved mass edit.
    • Refreshing the page will now delete any unsaved changes.
  4. When saving an edited rate card, blank rates will be saved as $0 rates.
  5. Indexes will now be required when adding a new line to an active indexed rate card.
  6. Edits to a rate card with $0 rates will now save successfully.

OneSUITE v7.9.0

Released 12/9/2024

OneCONNECT

  1. Multiple assistants will be able to receive notifications for a single AE.  Previously OneCONNECT notifications were only sent to an Account Executive and their one assigned assistant.  The OneCONNECT Notification Subscription has been updated to allow an assistant to see Notifications for any AEs they choose by selecting those AEs in the Select AEs tab on the OneSUITE Home screen. Specific direction regrading Setup is available in the knowledge base article Setting Up OneCONNECT Notifications - AE Selection. 
  2. The All Records check box has been moved to the Funnel Filter section.  Previously, this was located on the top toolbar in Inbox screen. This was done to improve performance in OneCONNECT,  By also moving this to the Funnel Filter, this will also replicate the same behavior in the OneTIM Order Status screen where the All Records check box is also located in the Funnel Filter.  Also, there are new ways to filter the data being searched to limit what is returned is the most relevant list of orders:
    • Active Orders
    • Ended Orders
    • Flight Dates 
  3. If a Billing Schedule is manually updated to reflect something different from what is in the Client's record in Setup, that value now remain when Order Revisions are imported from OneCONNECT. Previously, a revision would revert Billing Schedule back to the client's default value. 
  4. Revisions in OneCONNECT with a Cash/Trade value will no longer update when the revision is imported.  Previously, some revisions changed to that value were not supported in the XG traffic system.

OneTIM

  1. Extended OneSUITE.WebAPI support by providing methods to query the database by Advertisers, Agencies, Account Executives, Team and Active Users. 
  2. The SQL timeout for the TIM Table Cleanup job is now configurable so it can be increased as needed.
  3. OneTIM can now connect to CRM webservice with HTTPS.
  4. When processing a large amount of orders for auto-apply traffic snapshot, it was possible the status on some orders could change between the time the list of orders was identified for auto-apply and the implementation of the process. Moving forward, auto apply will check to be sure the status hasn't changed right before applying. That will ensure it only updates the status of orders that have a valid auto-apply status (contract confirmed, revision confirmed, and traffic updates accepted).

OneSUITE Rates

  1. Large rates cards can now be imported successfully.
  2. Spot duration factors can now be given a default values of 0%.
  3. Rate card import profiles are now saved with the rate card and visible in the UI. 
  4. Rate cards spreadsheets with the "Index" will not import successfully. 
  5. Duplicate lines can no longer be added to a rate card using the "Add Line" button. 
  6. When the default rate is $0, $0 now displays as the rate instead of $999. 
  7. Mass editing dates on rate card lines now be saved successfully. 
  8. Rate card line matching is now handled correctly when the matching criteria is "E". 
  9. Large rates cards can now be successfully exported. 
  10. Duplicate rate card lines can now be deleted. 
  11. Rate cards converted from RCM to OS Rates can now be activated when all the required data has been entered. 
  12. Blank rates are no longer allowed to be added to an Active rate card. 
  13. Spot duration defaults are now pulled from the import profile and displayed in the rate card grid. 

Setup

  1. Profile Permissions that are no longer used were removed. 

OneSUITE v7.8.2

Released 8/19/2024

OneCONNECT

  1. The "No orders are currently available that have been assigned to you..." pop-up message has been disabled. Previously, it was being displayed when it should not have been.


OneSUITE v7.8.1

Released 7/19/2024

Setup

  1. Advertisers and Agencies with thousands of records will now load correctly in the UI. A fix implemented in v7.8 was not compatible with these tables that included thousands of records.  Additional work will need to be done in a future release to allow these tables with thousands of records to load correctly.


OneSUITE v7.8.0

Released 6/3/2024
Application Compatibility: VIEW 4.0.3 & higher (refer to v7.3.1 below for relevant VIEW v4.x information)

OneTIM

  1. System will no longer allow save when there is an empty string or whitespace (empty) daypart. An error message will be displayed telling the user to correct the error before the order can be saved. Previously on occasion orders somehow were saved with those values and orders would get stuck.
  2. Extended OneTIM WebService with an Undelete Order method.
  3. Extended OneSUITE Web API with GetChangedAgencies method.
  4. Extended OneSUITE Web API with GetChangedAdvertisers method.
  5. Implementation of the newly requested client specific Rules Engine rules.
  6. Extended OneTIM WebService with GetRevisedOrderIDs method.
  7. Enhancement to existing Partial Order Load feature that offers additional functionality. For either of these features to be active, Partial Order Load must be active. Set up is handled at the system level via Setup - Configuration - Order Details - Number of lines that will cause an order to partially load. Once this feature is enabled, orders that have more lines that designated in Setup will load a single week by default, but the user can easily load any number of weeks by using the newly added Date Picker in the Lines tab for orders meeting the criteria of being partially loaded. If an order has less lines than entered into this field, the order will load all lines and none of the Partial Order Load functionality will be enabled. Regardless of size, orders not yet exported to traffic will load in OneTIM Order Details in their entirety. Will ensure orders are exported to traffic in their entirety. Once orders have been exported, they are subject to the parameters determined in system level settings upon loading and when opened, will load one week at a time. Knowledge Base article _Order Details - Partial Order Load_ provides explicit detail around end user functionality.
  8. Rates can now be managed directly in OneSuite via the new Rates module (OS Rates). OS Rates has the same core functionality as RCM but with an improved user interface and enhanced rates management capabilities. For more details, please refer to the OS Rates user manual.

Setup

  1. In OneSUITE Setup when Industry Type value is saved as "None", it now displays correctly as . Previously on occasion that value would be displayed with illegible characters.
  2. Advertiser List will generate in pdf or excel form from either Setup or Order Status as expected. Previously an error was thrown when the list was too large.
  3. When a user attempts to Export an order and traffic information is missing, if that user updates the Missing Traffic IDs when the Audit is checked in Setup there will be a system user shown as the user who made the change. Previously the first blank "NetworkUserName" user in the database was the default user populated. And those users could be Inactive users. This system user is set on the corresponding Web server within IIS as the SetupService's App Pool Identity.

OneCONNECT

  1. Users with the profile permission to do so can now edit Public favorites in OneCONNECT.
  2. If a user is trying to open orders belonging to an AE to whom they are not assigned, explicit error message will be displayed. Previously it was a Null error and user had no indication as to why the order wouldn't open.
  3. A JSON error will no longer be thrown for users newly logging in to OneSUITE and clicking Compare to OneTIM. Workaround to open a new browser and try again.
  4. If there is an issue with a OneCONNECT order that causes a notification to not be sent, skip that order and continue processing notifications for all other orders. Previously the entire job would stop and no notifications would be sent until the error was discovered.

 

OneSUITE v7.7.2

Released 3/25/24
Application Compatibility: VIEW 4.0.3 & higher (refer to v7.3.1 below for relevant VIEW v4.x information)

OneCONNECT

  1. Ampersand advertisers will no longer be required to have a Default AE who is a real user assigned in OneSUITE Setup for OneCONNECT orders to process correctly. Previously AE assignment and mapping were handled differently for Ampersand orders.


OneSUITE v7.7.1

Released 3/4/24
Application Compatibility: VIEW 4.0.3 & higher (refer to v7.3.1 below for relevant VIEW v4.x information)

OneTIM

  1. When Service Level Feature is active, SCX files will import into OneTIM regardless of whether the Client is able to be selected upon Import. Previously there was a missing NULL check which meant if the client wasn't identifiable when the import was attempted an object reference error was thrown when the user attempted to open the order. 

Setup

  1. When a user attempts to Export an order with traffic information missing and that user updates the missing Traffic IDs from Order Details rather than in Setup, the user shown in the Audit in Setup as having made the change will be the system user (e.g. Supervisor). That system user is set on the corresponding Web Server within IIS as the SetupService's App Pool Identity, as already set for many other processes. Previously it would show the first user in the database that had a blank "NetworkUserName" column. Those users could also be possibly be inactive.  Changes made to Client's Export ID (or any other field) in Setup will show the name of the user who made the change.

 

OneSUITE v7.7.0

Released 1/29/24
Application Compatibility: VIEW 4.0.3 & higher (refer to v7.3.1 below for relevant VIEW v4.x information)

OneTIM

  1. OneTIM Automated Provisioning - New OneSUITE WEB API has been extended to  be used to automatically populate fields in Setup to; Add New User, Add Profile Permission based on Designated Role, Remove Profile Permissions/Role from Users, and Disable Users. This will allow for Automated Provisioning to be enabled.
  2. OneTIM Rules Engine Audit - OneTIM Order Details Comments tab will provide a user facing Audit trail of when the Rules Engine has been applied to an order, and which rule was applied.
  3. Missing Survey warning will now correctly reflect whether those surveys are Comscore or Nielsen in every reference in the message. Previously Nielsen and Comscore were both referenced in some Comscore messages.
  4. Mkt Net Car HH UEs will correctly populate in VIEW when survey is changed to Comscore. Previously it was blank.
  5. Comments in the Create Makegood Lines dialog will be editable as expected. A 7.6.0 JQuery update broke the functionality. Workaround is to add line level comments in the Lines tab.
  6. Advertiser List will generate in pdf or excel form from either Setup or Order Status as expected. Previously an error was thrown when the list was too large.

OneCONNECT

  1. Makegood transactions for AMP Advertisers with "/" or other special characters in their AMP Advertiser Name will no longer fail.
  2. OneCONNECT Inbox funnel filter will correctly capture orders for multiple AEs and any other values chosen. Favorites can be saved and accessed as expected. Previously when selecting some combinations of multiple AEs, filters didn't work.

Setup

  1. OneTIM Customer Threshold - Service Level field is now active in OneSUITE. This system level feature must be activated by checking "Enable Service Level" in OneSUITE Setup - Order Details - System Defaults. When enabled a Service Level column will be available in OneTIM Order Status. Service Level value will be displayed in OneTIM order header. Data will be captured from CRM. 

 

OneSUITE v7.6.1

Released 11/10/23
Application Compatibility: VIEW 4.0.3 & higher (refer to v7.3.1 below for relevant VIEW v4.x information)

OneTIM

  1. Order Description for OneCONNECT orders with Source AMP has been updated. To be compliant with BOTS, AMP Office Name has to be in the third position in the Description. Original requirements put it in the sixth position.
  2. Orders meeting the criteria laid out for the nine current Altice Rules Engine rules from TIM Classic will automatically follow their proscribed workflows in OneSUITE in the same manner to allow them to conduct business as usual. Specific details around each rule can be found on this Knowledge Base article Altice Rules Engine in OneSUITE.
  3. A new WebAPI has been created to integrate with an external CRM platform (i.e., Salesforce) included with added authentication functionality. See 7.6.1 OneSuite WebAPI document.  Details can be found in OneSUITE 7.6.1 Technical Documentation.
  4. Makegood transactions for AMP Advertisers with "/" or other special characters in their AMP Advertiser Name will no longer fail.
  5. Updates will now stick when selecting workflow Statuses for triggering Auto Apply Traffic Changes. 


OneSUITE v7.6.0

Released 9/27/23
Application Compatibility: VIEW 4.0.3 & higher (refer to v7.3.1 below for relevant VIEW v4.x information)


OneTIM

  1. Fixes all the Bugs found in OAuth allowing this new security feature to be implemented with the deployment of OneSUITE v7.6.
  2. There is now a system level setting providing the ability to select which orders statuses meet the criteria for Auto-Apply Traffic changes. A new column labeled Auto-Apply Traffic Changes was added to Workflows under OneTIM Configuration in OneSUITE Setup. Available statuses are already listed on the right hand side of the chart. Adding a checkmark in the AATS column means when orders meet the existing Auto-Apply criteria and are in that status, flags will be cleared. Explicit direction provided in Knowledge Base article entitled Auto-Apply Traffic Changes in OneTIM .
  3. OAuth implementation has been re-worked so that both Windows and Anonymous Authentication can always successfully return a user's login. Permanent fix for the performance under load issues.
  4. An issue has been reported where the OneSUITE Home page got stuck on loading. FW was unable to recreate precisely however, the error seems to have been caused by the splitter on one page. The splitter functionality allowed the two sections on the "My Notifications & Alerts" tab of the Home page to be resized. Removing the splitter means section sizes will be static. Expectation is this will have minimal to no end user impact.
  5. Made the following updates to Auto-Apply Traffic Changes
    • Created a setting to allow admins to select which orders statuses should be eligible for Auto-Apply. Explicit direction provided in Knowledge Base article entitled Auto-Apply Traffic Changes in OneTIM .
    • Traffic changes will now be automatically applied even if there is no valid AE email address attached to an eligible order. Previously those orders were locked as there was no place to send the captured changes.
    • Max poller job run time has been increased to allow orders that may be locked for changes to not impact the flow of changes to other orders.
    • Fixed a GetUserPermissions error.
    • Fixed a gap when changing the schedule status on an exported order, the Pending Changes flag disappeared in UI but was not cleared on the order itself. This also resolved both the funnel and the flag display issues.
    • Failed flags will clear as expected when manual snapshots are applied.
  6. An option to Deselect N/A Lines has been added to the Preempt Units dialog within the preempt module. Some users do not want the N/A result of the inventory check to automatically exclude lines from being processed using the preempt module. Previously every line had to be unchecked individually. This new option allows all lines to be unchecked at once.
  7. This change is to allow applying Traffic Snapshot and log the line info when a makegood line doesn't have makegood relationship created. Previously an Object Reference Error was thrown on makegood lines that had Parent Line # blank and Tr Par # populated.
  8. Prep work for eventual Service Level Phase I feature that will be completed in v 7.7. For this initial work, a Customer Threshold column has been added to Advertiser records in Setup. As no values will be passed from CRM yet, the values in that field will be Null when v 7.6 is deployed. When v 7.7 is deployed, field name will be changed to Service Level. And the value as sent by CRM will be captured.  

Zone One Source

  1. ZOS can now support Comscore AIUE files as provided by Ampersand. 

OneSUITE v7.5.1

Released 7/6/23
Application Compatibility: VIEW 4.0.3 & higher (refer to v7.3.1 below for relevant VIEW v4.x information)


OneTIM

  1. Fix to address performance issues found in testing with multiple concurrent users in v7.5.


OneSUITE v7.5.0

Released 5/1/23
Application Compatibility: VIEW 4.0.3 & higher (refer to v7.3.1 below for relevant VIEW v4.x information)


OneCONNECT

  1. New Ampersand orders will be routed through OneCONNECT rather than through Gateway to TIM.
  2. Process Ampersand order revisions through OneCONNECT.
  3. Makegoods transactions will now be processed from OneCONNECT to Ampersand. Send Makegood button in OneCONNECT makegood screen will now send Makegood Report to Ampersand at [makegoods@ampersand.tv|mailto:makegoods@ampersand.tv] via email.
  4. Allow revisions to Ampersand orders to flow through OneCONNECT.
  5. Market Name has been appended to the OneCONNECT create order and order revision Notification emails subject line.

OneTIM

  1. OneSUITE Help button functionality has been updated to be compatible with the new design in Salesforce around how user identity is verified when using the Help button to submit a support case or access the Knowledge Base. Users should not experience any difference in functionality.
  2. All orders for digital syscodes will now process correctly through Gateway to TIM. Previously syscodes with a population of 0 did not process and had to be handled outside of Gateway.
  3. Auto-Apply Traffic Snapshots will work as expected. Previously random Traffic Snapshots were not applied with the error "Not implemented".

Order Details

  1. Makegood relationship will be correctly created when the syscode is updated on a makegood line. Previously when syscode was updated, Object Reference Error was thrown when user opened Traffic Snapshot.
  2. Makegood relationship will be correctly created when the syscode is updated on a makegood line. Previously when syscode was updated, Object Reference Error was thrown when user opened Traffic Snapshot.
  3. CM Initial Clearance will now no longer automatically be captured when AE completes and inventory check and saves the order when there are no oversold lines and the AE IC is at 100%.
  4. Copying then editing lines on an order will now work as expected when the Flight Pattern on an order is set to 1 On/0 Off . Means in essence redundant as that pattern simply means all weeks are available for scheduling spots. Previously there was an error thrown and lines could not be edited.
  5. Importing OneCONNECT revisions to OneTIM will now work correctly when a buyer changes a key field on a line with preempts in OneTIM. Now changes will be captured correctly, the original lines will be zeroed.

Setup

  1. Changing the version in Setup - Applications - View Wrapper will now stick. Previously it was reverting upon Save.
  2. Connection config password for SOS is restricted to 15 characters


OneSUITE v7.4.0

Released 12/19/22
Application Compatibility: VIEW v3.3.6 & higher (refer to v7.3.1 below for relevant VIEW v4.x information)
 

eRevisions

  1. Extra spaces at the end of a Traffic Export ID will now be ignored when a related order is exported to traffic.
  2. A Traffic Snapshot can now be successfully applied after one or more weeks have been added to the beginning of a flight on a previously exported order. Previously, an "Object Reference not set to an instance of an object" was displayed.
  3. Traffic Snapshots will now be automatically applied when explicit criteria has been met. Notifications will be sent under most circumstances. Refer to the "Auto-Apply Traffic Snapshots in OneTIM" knowledge base article for more details.
Auto-Apply will be performed when:
  • New order is exported to traffic and ingested in the traffic system, flag will still be set at traffic upon acceptance of the order, however that flag will now be cleared automatically on any traffic systems set to Auto-Apply Changes
  • Any other time traffic makes changes to an order that trigger a change flag, that change flag will be automatically cleared

Auto-Apply will not be performed when:

  • Orders contain Advertisers, Agencies, and/or Rep Firms defined with Type = Enterprise in Setup
  • Applying change would cause an order to split
  • Traffic system on the order is not configured to Auto-Apply changes 

Two new settings have been added to enable this functionality:

  • "Enable Auto-Apply Traffic Snapshots" in Setup | Configuration | Order Details
  • "Auto Apply Changes" for each desired traffic system in Setup | Configuration | Traffic Systems

OneCONNECT

  1. Buyer revisions will now import to OneTIM correctly when the buyer has changed a daypart that has preempts in OneTIM. Previously, the following error message occurred when attempting to import: "Import is failed due to error..."

OneTIM

  1. A new Deal Parameters feature has been added. This functionality will allow orders that don't meet certain criteria to simply run as ordered (so they would not be eligible for makegoods, posting or under-delivery). The criteria is based on a flag sent from CRM to OneTIM and a rate card percent threshold. This can be enabled by checking the "Enable Deal Parameters" option in Setup | Configuration | Order Details. Additionally, a value for the "Order level Rate Card % to trigger conditions" must be entered to one decimal place (e.g. 49.9). Refer to the "OneTIM Deal Parameters Order Stewardship" knowledge base article for more details.
  2. The LUR flag will now be set correctly when an order is not LUR-compliant. Previously, the LUR flag would not display right after the order was either exported to traffic or the traffic snapshot was applied.

Order Details

  1. The maximum number of characters for the Order Description field has been increased from 50 to 100.
  2. Lines copied from a line with estimated () audience statistics in the Create Makegood dialog will now behave the same as in the Lines tab. Previously, the audience statistics were not updated for the copied lines when the network/daypart was changed.
  3. The Shared Inventory column will now include single day lines with overlapping dayparts. Previously, Shared Inventory for single day lines would only populate when there were multi-day lines with overlapping dayparts. 

OneSUITE v7.3.2

Released 10/18/22
Application Compatibility: VIEW v3.3.6 & higher
 

eRevisions

  1. When the "Export MG lines created against Traffic PEs as MGs" system setting is turned off, bundled makegoods created from lines preempted by traffic can now be created successfully. Previously, beginning in v7.3.0, these lines were set to export as makegoods (with a 0 parent line number) instead of new lines and the export failed.

OneSUITE v7.3.1

Released 9/19/22
Application Compatibility: VIEW v3.3.6 & higher
 

Order Details

  1. OneTIM Makegood Report will reflect all lines captured in a bundled makegood. Previously, it would capture all preempt lines but only the first makegood line would appear in the report.

Setup

  1. A new configuration setting has been added to support VIEW 4.x. This new web.config key provides the ability to switch from the 32-bit to the 64-bit STG. Refer to the "VIEW Wrapper 64-Bit Installation" knowledge base article for further details. IMPORTANT: These configuration settings must be updated when upgrading to VIEW v4.0.3.

Custom

  1. The new D365 Inventory Created Source along with the AE order save functionality will now work as expected and the Opportunity ID will be populated in the Sales tab in the Order Details screen. 

OneSUITE v7.3.0

Released 8/22/22
Application Compatibility: VIEW v3.3.6 & higher
 

eRevisions

  1. Applying traffic changes to an order with 2 traffic lines mapped to a single OneTIM line number with a comment will now work correctly. Previously an object reference error was displayed. 

OneCONNECT

  1. All syscodes included in a single CPE (Client/Product/Estimate) for the same agency can now be viewed and processed in a single OneCONNECT Order Details screen. Refer to the "OneCONNECT Batch View & Makegoods" knowledge base article for further details.
  2. The file naming convention for PDF and Excel versions of the Order Details report has been updated to Advertiser(name)_Agency(name)_Estimate_Market_External Order #_Version #.
  3. The following Import to OneTIM failure message has been updated to be more clear, "Buyer's revision is trying to remove lines that cannot be removed from the order in OneTIM. Please contact FreeWheel Client Service so we can help you identify the lines in question." Previously, only a "Import is failed" message was displayed.

OneTIM

  1. A new GetOrderStatus method will now return the order’s status based on the Order ID. Previously, users would have to search for it in the GetOrder/GetOrders calls.  

Order Details

  1. When the Description field contains more than 50 characters, users will now be able to reduce the number of characters after attempting to save the order. Previously, the "Saving" message would hang and the user was unable to edit the field and save the order.
  2. Creating, then saving a new Order Header without line details will now work correctly. Previously, new lines were unable to be created, causing the order to be read-only.
  3. Read-only access will now be correctly applied to users not assigned to a market(s). Previously, attempting to edit an order would cause the following error message: "Object reference not set to instance of object".
  4. When using Google Chrome, a Maximum Call Stack Error will no longer be displayed when loading the AE dialog window with the zoom set higher than 100%.
  5. Lines that share inventory can now be checked in Order Details. Shared Inventory lines have matching syscodes and networks with overlapping dates and dayparts. Refer to the "Shared Inventory" knowledge base article for further details.
  6. The following preempt-related changes have been made (refer to the "Preempting Units in OneTIM" knowledge base article for further details):
    1. Reverting makegood line changes to their previous rate or number of units will now work correctly in Mass Edit. Previously, using the Mass Edit feature to revert a value caused the following error message: "This change cannot be made as it can cause the Makegood $ value to be greater than the Preempt $ value".
    2. Lines with no inventory issues can now be moved to the Preempt module. This allows a user to drop lines that meet inventory clearance, but do not meet business requirements. This feature is designed to be used with the Shared Inventory function.
    3. The Delete Lines button in the Preempt tab will now be correctly enabled only when one or more lines is selected. Previously, after selecting lines, then unselecting them, the Delete Lines button remained enabled. This issue was introduced in OneSUITE v7.1.0.
    4. The Inventory Priority Code will now be ignored on lines in the Preempt tab. Previously, changing the Inventory Priority Code on lines captured in the Lines and Preempt tabs allowed the order to save, but caused the following error message: "Lines Tab: Inactive PriorityCode: Order cannot be saved until an active PriorityCode is selected for Unique Line".
    5. The Show All Preempts checkbox will now be enabled despite a CH flag applied to the order. Previously, users were unable to view closed preempts as the CH flag caused the order to be in a read-only status.
    6. To prompt users to check inventory, a 'Check Inventory' reminder is now configured with the Enable Preempt Module setting. Orders that move from Proposal to the next workflow without an inventory check will receive one reminder message.
    7. The create makegood operation can now associate many preempts to many makegoods, or, many preempts to one makegood in the Order Details Preempt module.
    8. To limit the need toggle between the Preempt and Lines tabs, these new data fields have been added to the makegood dialog:
      • Nielsen/Comscore
      • Inventory
      • Rate Card

Reporting

  1. A new Pre-emption Report showing open and partially open preempts is now available. Refer to the "OneTIM Preemption Report" knowledge base article for further details.

Setup

  1. Rate card selections can now be correctly removed from the 'Selected Rate Card' field. Previously, the remove all button did not clear this field.   

Zone One Source

  1. Enterprise orders will now be excluded from the active order validation when deactivating syscodes, headends or networks.
  2. The network ID field will now support up to 10 digits in the database and UI to accommodate network IDs exclusive to networks rated by  Comscore (and not Nielsen).
  3. Zone One Source tab will now display correct application version.

Custom

  1. A new Created Source "D365 Inventory" value has been added. When inventory has been checked in CRM D365 and saved to OneTIM, the AE Initial Clearance % for both spots and dollars will now be displayed and locked in the "AE IC% ($ - Units)" field in the Order Header. Additionally, AE IC% $ and AE IC% Units columns will now be available in the column chooser in Order Status.

OneSUITE v7.2.0

Released 4/18/22
Application Compatibility: VIEW v3.3.6
 

Order Details

  1. The Traffic Changes Report button will now only be visible in Traffic Snapshot screen. Previously, it was also visible in the Sales Snapshot.

Custom

  1. New fields for Currency, Billed On, and Shared ID have been added to support a Unified Order process. This functionality can be enabled by checking the "Enable Unified Orders" option in Setup | Configuration | Order Details. This feature is dependent on future development work by the UOPT. Please refer to the "Unified Orders - New Fields" knowledge base article for further details.

OneSUITE v7.1.1

Released 3/21/22
Application Compatibility: VIEW v3.3.6

OneTIM

  1. The OneTIM WS will now allow multiple orders to be pulled in a single call using the new GetOrders call and passing the order numbers to be loaded. Previously, the call could only pull one order at a time.
  2. To improve line selection for the Makegood Report, two new fields have been added to the grid on the Preempt tab:
  • Contract Line Number - this read only field displays which Contract Line the Preempt Line is associated with. For Preempts made from a Makegood Line, this value will show which original line needs to be made good.
  • Show Contract Line - this editable field is only used when creating the Makegood Report. If this box is checked on a Preempt Line, the Contract Line associated with the Preempt Line will be displayed on the Makegood Report instead of displaying the Preempt Line. This option should be used when a Makegood Line that has not yet been sent to the client is preempted.
Refer to the "Preempt Units in OneTIM" Knowledge Base article for more details.
  1. The "[TIM] Order xxxxxxx was changed since loaded." error will no longer be displayed if the poller runs during the export process.
  2. Custom Reports can now be generated without error. Previously, the error message "Unable to produce custom report. Value is too large or too small for an Int16" was shown when the primary key Syscode in the report was greater than 32767.

Order Details

  1. Launching the Makegood Report from the Preempt tab will now display all selected lines on the report. Previously, only the first 50 Preempt Lines would be displayed on the report unless the user scrolled to the last Preempt Line before launching the report.
  2. By Day preempt lines that include a skipped day (e.g., M-Tu,Th-Sa), will now be created successfully. Previously, the error message "Please fix the following errors. Passed Units array length should match line.UnitDistribution array length"
  3. The Makegood Report launched from the Traffic Snapshot will now show all lines where the Current PE Units column is greater than 0. Previously, if the Current PE Units value was less than the number of units preempted on that line, the line would not be displayed in the Makegood Report. was shown.

Custom

  1. Orders will now successfully be created when using the SaveOrder WS call whether the Population and Impressions fields have values or not. Previously, starting in 7.1.0, LIFT orders that had NULL values in either of those fields would not save to OneTIM.

OneSUITE v7.1.0

Released 2/21/22
Application Compatibility: VIEW v3.3.2, RCM (Legacy) v2.1j

eRevisions

  1. New layouts can again be created for the Traffic and Sales Snapshots. Previously, starting in 7.0.0, the Layout Name field would be disabled preventing the user from creating a new layout.
  2. An error message will now be shown when traffic sends a Priority Code that does not exist in OneTIM. Previously, when applying this traffic change, a foreign key error was displayed.

OneCONNECT

  1. Removed unused Agency and Rep Firm contact info from the Import screen.
  2. In order to make buyer revisions easier to read, Date Range selections will now be considered when the Changed Lines filter is applied in OC Order Details screen.
  3. To simplify reading buyer revisions, the Order Details - Changed Lines filter will now only consider these fields (Lines with changes in any other fields will not be shown on the screen when the Changed Lines filter is enabled.):
  • Unit Length
  • Rating
  • Impressions
  • Network
  • Daypart
  • Rate
  • Units
  1. To simplify reading buyer revisions, the Compare screen fields highlighted in yellow are now limited to (Note: the comparison text is still shown for all other fields - e.g., CPM, CPP, etc., but now without the yellow highlight):
  • Bookend
  • Unit Length
  • Rating
  • Impressions
  • Network
  • Daypart
  • Rate
  • Units
  • Comments
  1. Performance has now been improved when opening a OneCONNECT order from OneTIM Order Details.
  2. The initial work to route Ampersand orders to OneCONNECT is now complete. OneCONNECT Hub v2.7.0 or higher is required and has been deployed. Further development is required to complete this effort.
  3. The AE mapping can now be updated multiple times. Previously, this action would cause a re-import to fail.
  4. Orders will no longer reload when a column in the OneCONNECT Order Inbox is re-sized.
  5. The following validation message(s) will now be displayed when re-importing OneCONNECT orders into OneTIM for the following scenarios:
  • If there is a change flag on the order: "Unable to import to OneTIM Order xxxxxx. Order has pending Traffic changes.
  • If the user doesn't not have permissions to edit the order: "Unable to import to OneTIM Order xxxxxx. User does not have permission to edit the order."
  • If the order is not editable: "Unable to import to OneTIM Order xxxxxx. Order is not editable."
  • For partial imports, if the OneTIM order is updated while the Import to OneTIM is still in process: "Changes have been made to this order by seller since import process started. Please review these changes in Order Details and import again."

OneTIM

  1. Users can now include apostrophes and other special characters when filtering on the Client Name column on the Order Status screen.  Previously, entering a client name with an apostrophe or another special character didn't return any results.
  2. The Application Error Log will now correctly filter for data and display more than 500 lines.  Previously, the user could not filter or search for data and would display blank pages if the log had more than 500 lines.
  3. The SAuthenticate call in the OneTIM WS will now work correctly. Previously this call was failing.
  4. The Program Name and other text-based user-entered fields will now retain the case entered when an order is saved.  Previously, the case in these fields could change when the order was saved.
  5. Users will now be notified if someone else opens, edits, or saves an order that they have open in OneTIM.  There are two new settings in Setup that will need to be activated to turn on this feature:
Order Details Setting
Setup - Configuration - Order Details
Checkbox "Notify users when the order they have opened is opened or saved by another user"
Profile Level Setting
Setup - Users -Profiles - Order Details Tab
Checkbox "Notify users when the order they have opened is opened or saved by another user"
  • The Open and Edit notifications will be displayed if another user opens or edits the order in OneTIM. These two notifications will not be displayed if another user opens or edits the order in OneCONNECT, VIEW, Traffic, or any other application other than OneTIM.
  • The Save notification will be displayed when the order is saved from any application including the eRevisions poller.
  • OneCONNECT will notify the user when they Import the order into OneTIM if that order is already open in OneTIM by another user.
  1. Monthly Contracted Totals are now displayed on the Totals tab for orders imported into OneTIM.
  • These values are calculated at the time of import when importing from OneCONNECT, Gateway, SCX file, or any application that saves orders using the OneTIM WS.
  • These values are read only for all users.
  • These values will be cleared if the user changes the Contracted Totals on the Lines tab.   
    • If the order is only 1 month long, changing the Contracted Totals on the Lines tab will not clear the Monthly Contracted Totals.
  • These values will also be cleared if the user changes the Start Date on the order
    • If the original flight dates and the updated flight dates are both contained within the same single month, then the Monthly Contracted Totals will not be cleared.
  1. Added TIM Advertiser ID and TIM Agency ID fields to the OneSUITE UI (These fields are read only for all users as they display the primary key for the record, allowing the user to distinguish Clients and Agencies with the same name from each other.):
  • TIM Advertiser ID is displayed on the Advertiser page in Setup and in the Client Search dialog launched from the ellipse button next to the Client dropdown in Order Details.
  • TIM Agency ID is displayed on the Agency page in Setup, in the Client Search dialog, and in the Agency dropdown in Order Details.
  1. A 'Traffic Changes Report' button has been added to the Traffic Snapshot screen. This Excel report includes the before and after changed field values.
  2. The "Billing Schedule" column can now be added to the Order Status grid.
  3. Updated a stored procedure used to load the Order Status page to help reduce database locking/blocking.
  4. Traffic Changes can now be applied if traffic has created a makegood or un-dropped a spot against a Preempt line where the Rate value is 0. Previously, traffic changes would be rejected because the PE Status on the Preempt line is Closed when the Rate = 0.

Order Details

  1. When importing an SCX file and the survey name is not fully defined, a warning message will be displayed and the order will function normally. Previously, an error message would be displayed stating "Error: Length cannot be less than zero. Parameter name: Length.".
  2. The Mass Edit and Create Makegoods dialogs will now work correctly when the ViewWrapper is down. Previously, both of these dialogs would show an error stating 'ViewWrapper Service could not be connected."
  3. The Show All Preempts checkbox setting will now be retained when the Preempt Units dialog is opened from the Lines tab. Previously, the Show All Preempts checkbox would be unchecked in this scenario.
  4. When exporting an SCX file from Order Details, if any line on the order has Order Line Type set to By Flight, a message will now be displayed stating that you cannot create an SCX file with By Flight lines.  Previously, an object reference error would appear.
  5. The Delete Lines button on the Preempt tab will now only be enabled if one or more lines are selected. Previously, if you selected one or more lines and then unselected them, the Delete Lines button would stay enabled.
  6. The "Display line cannot cross a calendar month since Billing Schedule is Calendar" error message will now only appear when adding new lines via the Line Wizard if the header end date crosses into a new calendar month.  Previously, this error message would appear even when the header end date was within the calendar month.
  7. When traffic un-drops spots on a line that has multiple PE lines associated to it and then applies the changes in the Traffic Snapshot, those un-dropped spots will now update as many PE lines as necessary. Previously, an error would be displayed preventing traffic changes from being applied.
  8. Duplicate demos will no longer be added to an order. Previously, some filtered lines were missing when duplicate demos existed.
  9. Updating the Rate value on a line in the Rate $ column where RC%=0 will no longer recalculate the Rate value to 0.  Previously, if the RC%=0 and a rate in the Rate $ column was updated by the user, the rate would update to 0.  

Setup

  1. The TIM User Password field from TIM application configuration dialog in Setup has been removed since this field is not being used. 

OneSUITE v7.0.4

Released 12/3/21

Order Details

  1. Revisions to an order that contain Makegood lines created in OneTIM will now export successfully to the traffic system. Previously starting in 7.0.0, the export would flag the MG lines as changed even though no changes were actually made on those lines.

OneSUITE v7.0.3

Released 11/11/21

eRevisions

  1. Traffic changes can now be applied when traffic un-drops units. Previously, starting in 7.0.0, applying traffic changes that contains un-dropped units would show an error, "Cannot delete a line that has preempt lines created".
  2. Non-exported preempt and/or makegood lines will now be deleted when a traffic change is applied. Previously, starting in 7.0.0, applying the traffic change would fail and an error message would be displayed stating that the user cannot delete a line that has an associated PE or MG. 

Order Details

  1. Lines can now be successfully preempted on an order where the Total $ value is 0. Previously, creating preempts would fail with the error message, "Error in adding preempts".
  2. The Notes value from the original line will now be copied to the Preempt Line when spots are preempted in Order Details or traffic.
  3. Preempting a Makegood line will now create a new PE line and not change any of the existing PE lines. Previously, the original PE line was updated along with adding a new PE line.

Reporting

  1. The Order History Report will now successfully open for orders where Preempt lines were created in OneTIM.

OneSUITE v7.0.2

Released 10/19/21

Order Details

  1. Revisions to an order that contains a Makegood line created in OneTIM will now export successfully to the traffic system. Previously starting in 7.0.0, the export would flag the MG lines as changed even though no changes were actually made on those lines.

OneSUITE v7.0.1

Released 9/27/21

Setup

  1. A new "Export MG Lines Created Against Traffic PEs as MG" checkbox has been added to the Setup | Configuration | Order Details page. When checked, makegood lines created against a Preempt line will be exported as a makegood line. If unchecked, these makegood lines are exported as a regular line.

OneSUITE

  1. Special characters will now display correctly in the Order Description and Program Name fields. Previously, starting in OneSUITE v7.0.0, special characters were not displayed correctly.

Order Details

  1. Lines where Units=0 and Preempt Units 0 will no longer be shown in the Lines grid when the Hide 0 Unit Lines box is checked. Previously, these lines were shown when Hide 0 Units was checked. 

OneSUITE v7.0.0

Released 8/16/21
Application Compatibility: VIEW v3.3.2, RCM v2.1j

OneCONNECT

  1. Orders that start in CRM D365 can now be linked to the OneTIM order # or the CRM Opportunity. OneCONNECT will maintain the connection between the order and the linked value. Refer to the "CRM Opportunity & Proposal Link in OneCONNECT" knowledge base article for further details.
  2. Orders sent using Comscore surveys can now be validated and processed. Previously, the Imps/Rtgs were imported without the associated survey information. OC Hub v2.6 or higher is required.
  3. A new "Zone Name" column has been added to the Inbox screen.
  4. All instances of the label "NCC" have been updated to "AMP". This change applies to the Source field in these screens: Inbox, Order Details, and Inbox Order Import.
  5. An "Advertiser" can now be changed if the Start Air Date has not passed. Previously, Advertiser mapping was locked after an order was imported to OneTIM.
  6. Exported makegoods will now match back to the original preempted line as long as only the days have changed and the number of units do not exceed the original line's units. This decreases the number of makegoods sent to a buyer.
  7. The Import and Makegood error messages have been simplified (e.g., Error confirming order and sending Makegood. Please try again once or twice and if it continues to fail, contact FreeWheel Client Service.). Previously, a Syntax or NullReference error message was shown.
  8. The OneTIM order Description will now remain static when a revision is imported. Previously, a user entered description was overwritten by the OneCONNECT 'Estimate Description'.
  9. The Preempt Modules Makegood Report is now compatible with Ampersand's AND system.
  10. The ability to partially import a revision when a buyer has made changes to past and/or current weeks has been added. OC Hub v2.5 or higher is required (and has already been deployed). Refer to the "OneCONNECT: Partial Import" knowledge base article for further details.
  11. Two new columns have been added to the Inbox screen, "Makegood Age" and "Modified Date".
  • Makegood Age: Number of days a makegood transaction has been waiting for a buyer response.
  • Modified Date: Date when a buyer or seller submits a change to the order:
    • Send Makegood
    • Cancel Makegood
    • Reject Makegood
    • Accept Makegood
    • Order Revision
    • Revision received while there is an active Makegood
    • Order Cancel
    • Order Cancel from Eleven while there is an active Makegood
For more information about these columns refer to the "OneCONNECT Order Inbox Overview" knowledge base article for further details.
  1. A warning message will now be shown when a DARE order's flight dates are extended beyond the buyer's dates; "OneTIM contains units outside the Buyer's current flight dates of \{Insert Dates}. Makegoods outside those dates will not be sent." Previously, this message was only shown for Eleven orders.
  2. The Order Details Bookend column now matches the OneTIM Bookends drop-down selections. Previously, these bookend selections (i.e. Null, All, Bookend Invalid, Bookend Valid, No Bookend) were not consistent.
  3. An Inbox "Loading" message will now be shown while the screen is loading data. Previously, the screen was blank.
  4. The Compare to OneTIM Date Filter will now correctly handle weeks with 0 spots when a seller extends an orders flight dates in OneTIM. Previously, a JSON error was thrown and sometimes prevented makegoods from being sent to a buyer.
  5. The Preview Makegood report can now be generated when the preceding makegood is in a rejected status. Previously, the report would not open.

OneTIM

  1. A new "requestLimits maxQueryString" setting has been added to the web.config file to allow extremely long URLs in OneTIM. Previously, opening a very large saved filter (e.g. containing all columns and 400 zones) would cause a "Failed to load filters. Status: error. Error: Not Found" error.
  2. A DSR button is now available in the Order Status screen. This function is designed to link to a custom module and can be enabled in Setup | Configuration | Application:
  • Check the Integration Enabled box.
  • Populate the DSR URL with correct value for the Dropped Spot Report location - must be 100 characters or less.
  1. A SET button is now available in the Order Status screen. This function is designed to link to a custom module and can be enabled in Setup | Configuration | Application:
  • Check the Integration Enabled box.
  • Populate the SET URL with correct location for the Special Event Tracker Tool - must be 100 characters or less.
  1. BOT Order Comments can now be hidden. To enable this feature, enter the BOT name in the "Filter out BOT Order Comments (BOT Name) field on the Setup | Configuration | OneTIM screen. By default any Order Comment with that name in the From column will automatically be hidden on the Order Status and Order Details screens. The user can click the BOT Comments button to view these comments.

Order Details

  1. Units can now be preempted in Order Details before exporting the order to traffic. Refer to the "Preempting Units in OneTIM" knowledge base article for further details.
  2. Orders can now be created using Comscore data. Note that orders cannot contain a mix of Nielsen and Comscore surveys.
  3. Performance improvements have been made on the Order Status screen for orders containing a large number of syscodes.
  4. The Contracted Var % and Initial Clearance % columns will now be correctly exported from the Order Status screen to an XLS or PDF file. Previously, these columns would always be blank in the exported file.
  5. When saving from VIEW, if the syscodes on the order do not exist in OneTIM, the error message displayed will now indicate that either the user is not assigned to the market OR the syscodes do not exist. Previously, the error message always stated that the user is not assigned to the market.
  6. Saving an order after removing non-insertable networks from an orbit will now work correctly, Previously, an "exceptions occurred: startindex cannot be less than zero. parameter name: startIndex" error message would be displayed and the component networks would not be saved/updated.
  7. The Total GRP and GIMP values will now be correctly calculated when an order is re-imported from OneCONNECT. Previously, these values were not always updating.
  8. Initial Clearance % will now be calculated correctly when the amount of inventory oversold is greater than the number of units sold on the line. Previously, this could cause the IC% value to be negative.
  9. Deactivated Priority Codes will no longer be listed in the Priority and Inventory Priority dropdowns in Order Details.
  10. If any errors occur when clicking the Split button to uncombine weeks for the first time, the Combine Weeks box will now be re-checked when the error message is displayed.
  11. Mass editing the Start or End Date on orders where the Billing Schedule is set to Calendar will now work correctly. Previously the Mass Edit screen would hang with a "Preparing Mass Edit" message and the changes would not be saved.
  12. The Makegood Report will now be successfully generated on orders that do not have the Agency field populated.
  13. The Start and End Month dropdown lists will now be populated in the AE History dialog. Previously, starting in OneSUITE v6.5.0, these dropdowns were always blank.
  14. The Total GRP and GIMP values will now be calculated correctly when changes are applied from traffic. Previously, these values were not always updated.

Security

  1. The following security issues have been addressed within this version: 
  • To address potential security vulnerabilities, the ServiceStack component was upgraded to that latest version and the DotNetZip.Semvered component was removed from the OneSUITE code.
  • Due to a potential security vulnerability, the CSV file export option is no longer available.
  • Error message text has been removed from the OneTIM URL for security reasons.
  • To address potential security vulnerabilities, an option to define the SMTP Port number has been added to the Setup | Configuration | System screen and the Base.AQM.exe.config file.
  • To address a potential security vulnerability,  all OneSUITE pages have been updated to display placeholders instead of actual passwords in the View Source option.
  • To address a potential security vulnerability, Cross-Site scripting has been prevented in all of the Order Status screens.

ZOS

  1. Performance has been improved when mapping headends to sycodes.
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk