What's New
Connectbase Software Release Notes
New features and enhancements in this release
Connectbase introduced the following new features, enhancements and bug fixes in this release.
API Enhancement
Zayo API has been implemented as an available External API integration with the following details.
Supported Countries: US, Canada, UK
Covered Products: Following products, access mediums and speeds are supported:
IP-DIA (Dedicated Internet) | Fiber, Copper: 10 20 30 40 50 60 70 80 90 100 150 200 250 300 400 500 600 700 800 900 1000 2000 3000 4000 5000 10000 15000 20000 25000 30000 35000 40000 45000 50000 100000
ETH-ELINE-UNI (Ethernet-Switched) | Fiber, Copper: 10 20 30 40 50 60 70 80 90 100 150 200 250 300 400 500 600 700 800 900 1000 2000 3000 5000 10000 20000 30000 40000
ETH-ELINE-P2P (Ethernet - Dedicated) | Fiber, Copper: 10 20 30 40 50 60 70 80 90 100 150 200 250 300 400 500 600 700 800 900 1000 2000 3000 4000 5000 10000 20000 30000 40000
WAVES-STD-P2P (Wavelengths) | Fiber, Copper: 1000 2500 10000 40000 100000
Supported Terms: 12, 24, 36, 48, 60 Months.
AT&T Price Quote has been implemented as an available External API integration with the following details.
Supported Countries: United States of America
Covered Products: Following products, access mediums and speeds are supported:
Wavelengths | Fiber: 1G, 10G, 40G, 100G, 400G
Supported Terms: 12, 24, 36, 60 Months.
Additional Notes: P2P is required for quoting this API.
We are updating our Verizon Quote integration to include the quoted “UNI Speed” in the API Info of results for the EVPL and Switched E-Line + products. Previously, this information was only available for quotes on Verizon’s TLS product.
We are updating how alternative speeds are offered for Broadband products that carry separate download and upload speeds (for example, 100/20).
Previously, an alternative was only offered when both the download and the upload moved in the direction of the requested speedPolicy. For asymmetric tiers this discarded valid options — a request for 1000/200 was not offered 1000/500, despite the identical download speed and a significantly better upload.
Going forward, either speed can satisfy the speedPolicy on its own, provided the other does not move backwards:
With NEXT_HIGHER, an alternative may have a higher download, a higher upload, or both — and neither speed may be lower than requested.
A request for 100/20 may now be offered 200/20 (higher download, upload unchanged), or 100/30 (higher upload, download unchanged).
An alternative of 120/15 is not offered against a 100/20 request, because the upload would drop.
With NEXT_LOWER, the same rule applies in reverse — neither speed may be higher than requested, and at least one must be lower.
With NEXT_HIGHER_AND_LOWER, both directions are evaluated.
Where more than one tier qualifies, the nearest alternative that improves both speeds is preferred and returned on its own. Only when no single tier improves both will up to two alternatives be returned — the nearest improvement to the download, and the nearest improvement to the upload.
For example, a request for 100/20 where the supplier offers 200/20 and 100/30 but not 200/30 will return both.
Requests for an exact speed match are unaffected, as is the existing setting controlling whether alternatives accompany an exact match. Term resolution is unchanged.
In light of AT&T’s impending end-of-year deprecation of their Wholesale Wireline SQ v3/v4 API, we are updating our AT&T New Experience integration with the following enhancements to facilitate the migration in full:
Enabling the quotation of the following ADI, AVPN, and ASE speeds based on the serviceability of its respective upper-bound AT&T speed.
If 50 Mbps is available, then requests for 30 Mbps and 40 Mbps will also qualify.
If 100 Mbps is available, then requests for 60 Mbps, 70 Mbps, 80 Mbps and 90 Mbps will also qualify.
If 1000 Mbps is available, then requests for 700 Mbps, 800 Mbps and 900 Mbps will also qualify.
When tier is unavailable in the AT&T response to use for setting Network Connection Status and Building Connection Status, the fiberOnSiteIndicator will be used instead:
If true → Building Connection Status = “OnNet” & Network Connection Status = “Connected”
If false → Building Connection Status = “Off Net” & Network Connection Status = “Not Connected”
We are adding the following information to the returned API Info:
Affiliate Name = affiliateName
ASE Wholesale Project ID = ProjectID associated with ASE Wholesale (ASE Only)
We are updating our integration with the AT&T Wireline API to display the Last Mile Supplier as “AT&T”, regardless of the building and network connection status returned for the service location. Previously, this returned as the LEC Name returned by the API, which has been respectively moved to the Notes as information.
TCW Enhancements
Added the ability to set Building Connection Status through CPQ Rules, enabling Building Status values to be assigned to pricing results from geography-based and other rate cards that are not associated with a building list.
Enhancement Details:
The Building Connection Status attribute is now available when configuring a CPQ Rule action of Set to. Rules can assign the following statuses:
OnNet
OffNet
Near Net
On Net-Limited Access
Prospect
The rule applies to both All Locations and Building pricing. When a rule matches the configured criteria, the resulting Building Connection Status is updated accordingly, including overwriting a status already returned in the pricing results.
Business Impact
This enhancement removes a limitation for geography-based rate cards, which previously could not provide Building Connection Status because they were not linked to a building list. It allows customer-specific pricing logic to distinguish between On Net, Near Net, and Off Net availability and supports Vodafone’s migration requirements for consistent Building Status values in downstream quoting and ordering workflows.
As a buyer utilizing CPQ selection rules to help me identify my lowest cost solutions from my automated pricing, I need the ability to write a CPQ Rule to select the lowest total order value (TOV) per address per product.
Requirements:
From CPQ Rules - create new or edit CPQ Rule:
When data type = “Pricing Criteria”, add a new use value of “Lowest TOV per Address per Product”. Currently only Lowest TOV per Address, and Lowest TOV per Supplier exists.
When rule is created for data type = pricing criteria and use value = lowest TOV per address per product and action = selection, the system should auto-select in CPQ Step 3 the solution with the lowest dollar value in the Total Order Value (TOV) field in CPQ Step 3.
Change should be logged in Automation and Quote Log consistent with existing CPQ Rules
Connectbase Software Release Notes
New features and enhancements in this release
Connectbase introduced the following new features, enhancements and bug fixes in this release.
API Enhancement
Cammington API has been implemented as an available External API integration with the following details.
Supported Countries: South Africa
Covered Products: Following products, access mediums and speeds are supported:
Comsol CX Broadband (Dedicated Internet | Wireless - Fixed): 10, 20, 50, 100
Comsol 5G (Broadband | Wireless - Fixed): 10/10, 20/20, 25/25, 50/25, 50/30, 100/30, 100/50, 200/30, 200/100
Supported Terms: Any (maintained via rate card)
We have updated our ENET Service Quotation integration to quote by Eircode rather than per-address, at ENET’s recommendation since pricing will be the same across all addresses within a common Eircode. Additionally, we have updated our integration to account for ENET increasing the daily limit of calls to a single Eircode from 10 calls to 30 calls. These two changes will allow significantly greater API throughput for quotes with multiple locations that share the same Eircode (“Zipcode” in the TCW UI).
We have updated our Verizon Exchange Quote integration to resolve some discrepancies in our logic for mapping Access Speed and Interface Speed for the Internet Dedicated+ product. Requests between 100 and 300 Mbps will now request a 1 Gbps interface instead of a 300 Mbps interface.
TCW Enhancements
A new Detailed View option has been added to the WIP – Requests Tab in CBM, enabling users to view all requirements across requests in a single list for faster action at scale.
What's New:
Detailed View Toggle — Switch between a summarized view (grouped by Request ID) and a flat, requirement-level list view directly from the Requests Tab.
Requirement-Level List — Displays all individual requirements in a single list with Request ID as a dedicated, sortable column.
Updated Quick Filters — Filter cards automatically reflect requirement-level metrics when Detailed View is active.
Filtering Retained — All existing filters remain fully functional in Detailed View.
Who Benefits: CBM users managing high volumes of supplier pricing requests who need to quickly identify and act on individual requirements across multiple requests.
The WIP and Global WIP views have been redesigned to improve usability, consolidate navigation, and give users deeper visibility into quote details — all without leaving WIP.
New Info Icon with Quote Details
Info Icon & Quote Details Pop-Up — Click the info icon on any quote to view and export a summary of all locations and configurations in the quote without navigating away from WIP.
UX Refresh & Navigation Consolidation
Action Menu Replaces Icons — Share Quote, Order Quote and Assign User individual action icons have been consolidated into a three-dot action menu on the far left of each WIP line item.
Quote Name Hyperlink — Quote names are now clickable links, replacing the previous "Go to Quote" arrow icon.
New Requirements Count Column — A new "Reqs" column displays the total requirement count (location × config) for each quote, including updates as new CBM pricing is added.
Quick Filter Cards — Five new color-coded quick filters added to WIP and Global WIP:
In Progress — Active quotes in Quote Created, Configuration, or Edit Pricing & Reference Data (Steps 1 - 3)
Pending > 30 Days — Quotes pending longer than 30 days
In Bid Management — Quotes with open CBM Requests
Requires Approvals — Quotes with pending Activity Rule approvals (shown only if approval rules are configured)
Expired Pricing — Quotes with supplier pricing past expiration
Blockers Sub-Menu Retired — The My Blockers sub-menu has been removed as part of consolidating WIP, Activities, and Blockers under a single WIP menu. All Blockers can be viewed by leveraging the “Requires Approvals” and/or “In Bid Management” quick filters in WIP.
Who Benefits: CPQ users who manage quoting workflows and need faster access to quote details, streamlined navigation, and at-a-glance filtering to prioritize work in WIP.
Clone Rule — Duplicate an existing rule via the actions menu. The cloned rule pre-fills with "CLONE - [Rule Name]" and carries over all conditions.
Description Field — A description can now be added when creating or editing a rule and is displayed as a column on the summary screen.
Rule Name Hyperlink — Rule names are now clickable, opening a detail summary view with inline edit access.
Audit Columns — New Created By, Created Date, Modified By, and Modified Date columns provide full change-tracking visibility.
Column Filtering & Sorting — All columns (including new audit fields) are now filterable and sortable.
Label Cleanup — "Activity" column renamed to "Active"; action menu items simplified to "Edit" and "Delete."
Configuration Templates — previously only accessible in CPQ Step 2 — are now fully available within the Quick Quote configuration screen.
What's New:
Select Template & Save Template buttons added to the Quick Quote configuration section, matching the existing CPQ Step 2 experience
Pinned Templates section displayed directly under "Choose Configuration" when one or more templates are pinned for the user's account
Full template interoperability — templates created or edited in Quick Quote are immediately available in CPQ Step 2 and vice versa
One-click configuration apply — selecting a template auto-populates all configuration attributes, allowing users to submit and run the quote immediately
Impact: Streamlines the quoting workflow by eliminating the need to navigate to CPQ Step 2 solely to access saved configuration templates. Users can now create, select, and apply templates without leaving Quick Quote.
The Product Catalog NNI Locations configuration screen now supports additional data fields to improve NNI visibility, management, and downstream quoting accuracy.
What's New:
Facility Owner — free-text field added to capture different facility owners at a POP location
Primary toggle (Yes/No) — identifies whether an NNI is the primary or backup; defaults to primary.
Active toggle (Yes/No) — allows users to mark an NNI as inactive for capacity or other issues and reactivate when appropriate; defaults to Active
NNI Capacity — dropdown field (1G, 10G, 100G, 400G, 800G) to record NNI capacity; informational today, with future use planned to exclude over-capacity NNIs from automated selection
Products — multi-select dropdown to identify which products are supported for each NNI, consistent with existing NNI Rules and NNI Locations pricing dropdown logic
All new fields are available in Manage Columns, the export file, and the import template; the template upload tip screen has been updated accordingly
Impact: Provides telecom buyers and admins with richer NNI configuration data, enabling more precise quoting logic and better management of NNI capacity and availability.
The legacy "Bid Manager (CBM) - Requests to Me" screen has been replaced with a new CBM Supplier Dashboard, giving suppliers a modern, Deal Desk–style experience for managing internal CBM pricing requests. This dashboard is for sellers responding to in platform buyer CBM pricing requests (Request Pricing for Fallout, Negotiate Pricing, Budgetary to Orderable requests)
What's New:
Redesigned dashboard — WIP/Requests-style layout with columns for Company, Status, Requester, Email, Contact Number, Created Date, Due Date, Age, Reqs, and Assigned
Supplier-side status workflow — new statuses (New → Assigned → Pricing Sent → Closed – Buyer Acknowledged) provide clear visibility into request progress from the supplier's perspective
Action menu — three-dot menu on each request with Assign to Me, Unassign, and Respond to Pricing Request options
Inline Supplier Response Portal — "Respond to Pricing Request" opens the full Supplier Response Portal (header info, notes, bulk edit, export/import) in an overlay without leaving the dashboard
Expandable requirements view — expand any request row to see all associated requirements
Info panel — info icon displays request summary fields and buyer notes at a glance
Global Requests — users with the Global WIP setting can view all requests
Quick filters — My Requests and Global Requests each offer targeted filters (Pricing Sent – Waiting on Buyer, New Messages, Approaching Due Date, New Requests)
Impact: Provides suppliers using the internal CBM flow with a feature-rich, self-service dashboard to receive, assign, and respond to pricing requests — replacing the legacy Bid Manager screen with a streamlined workflow that mirrors the buyer-side Deal Desk experience.
Pricing Geography now supports configuration and matching on country-specific postal regions/ postal code prefixes, eliminating the need to configure hundreds of individual postal code rules for regions that share a common prefix.
What's New:
New "Postal Region" Geography Type — available when creating or editing Pricing Tier geography rules, enabling prefix-based matching for supported countries
Supported countries: Canada (FSA, e.g. H3L), Portugal (4-digit, e.g. 1000), UK (outward code, e.g. SW1A), Netherlands (4-digit, e.g. 1234), and Ireland (routing key, e.g. A65)
Country-scoped matching — prefix rules match only within their designated country, preventing cross-country false positives
Impact: Significantly reduces configuration effort for international pricing geography rules. Customers pricing by postal region no longer need to enter every individual postal code — a single prefix rule now covers all matching locations within the specified country.
The maximum number of speeds that can be saved in a Configuration Template has been increased from 50 to 100.
What's New:
Speed selection limit raised — users can now save configuration templates with up to 100 speeds (previously 50)
Broadband support — allows up to 100 combinations of upload/download speeds in Broadband configuration templates
Validation messaging — users who attempt to exceed the 100-speed limit receive a clear error: "Templates cannot be saved with more than 100 speeds."
Impact: Removes a configuration constraint that was too restrictive for customers with large speed portfolios, enabling more comprehensive templates without requiring multiple template workarounds.
What's New:
Redesigned address validation experience in Quick Quote and Deals with improved usability, global-friendly labels, and personalized layout.
Both the original input address and the found quoting address are now displayed side by side in the validation results table.
Data Center search by name or address is now available directly from the typeahead.
Impact:
Faster, more intuitive address entry with fewer steps to move from validation to quoting.
International users benefit from globally appropriate terminology.
Easier comparison between entered and found addresses creates clarity and reduces steps to correct before quoting.
User action required: No action needed. The new screen will be enabled in all instances with the TCW.2026.R16 release.
The Address Autocomplete API has been upgraded to a new centralized autocomplete engine. The developer portal's Address Autocomplete API v2 endpoint now delivers expanded global address coverage with stronger support for international address formats and partial address entry, reduced duplicate suggestions, and improved reliability for searches containing apostrophes and special characters.
Impact: Developers integrating the Address Autocomplete API will see more accurate and relevant address suggestions, a cleaner and more consistent results list with fewer duplicates, and greater reliability across a wider range of address inputs globally.
Connectbase Software Release Notes
New features and enhancements in this release
Connectbase introduced the following new features, enhancements and bug fixes in this release.
API Enhancement
BT Wholesale MEF has been implemented as an available External API integration with the following details.
Supported Countries: United Kingdom
Covered Products: Following products, access mediums and speeds are supported:
Wholesale Optical (Wavelengths | Fiber): 10000, 20000, 30000, 40000, 50000, 60000, 70000, 80000, 90000, 100000, 400000
Wholesale E-Line (Ethernet - Switched | Fiber): 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1500, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 5500, 6000, 6500, 7000, 7500, 8000, 8500, 9000, 9500, 10000
Wholesale Ethernet Internet (Dedicated Internet | Fiber): 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1500, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 5500, 6000, 6500, 7000, 7500, 8000, 8500, 9000, 9500, 10000
Wholesale E-LAN (Dedicated Internet | Fiber): 0.2, 0.4, 0.6, 0.8, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 125, 150, 175, 200, 250, 300, 350, 400, 450, 500, 600, 700, 800, 900, 1000, 1500, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 5500, 6000, 6500, 7000, 7500, 8000, 8500, 9000, 9500, 10000
Supported Terms: 12, 36, 60 Months
Additional Notes: Superfast GEA is not currently available in the initial integration. This capability will be planned into a future release.
Cegecom MEF has been implemented as an available External API integration with the following details.
Supported Countries: Luxembourg
Covered Products: Following products, access mediums and speeds are supported:
DIA (Dedicated Internet | Fibre): Speeds vary per buyer
Online Business (Dedicated Internet | Fibre): Speeds vary per buyer
Supported Terms: 12, 24, 36 Months
We are updating our Verizon Exchange Quote API integration with more detailed quote results and messaging concerning the impact of the returned access on the Building Connection Status and Network Connection Status values. This includes the following changes:
Exposing the following info to the buyer verbatim: Access Type, Access Provider Name, and Lit Capability
Adding the following condition messaging for ID+, Switched E-Line +, and EVPL, based on the returned accessProvider:
“VZB” →; “This service is on-net because the access provider for this VZB product at this location is Verizon’s ‘VZB’ legacy network.”
“VZT” →; “This service is off-net because the access provider for this VZB product at this location is Verizon’s ‘VZT’ legacy network.”
Else → “This service is off-net because the access provider for this VZB product at this location is [accessProviderName].”
Reconfiguring the Network Connection Status with the following logic:
If TLS or OWS (VZT products) and successfully quoted -> On-Net & Connected
For all other products (VZB products), this is based on accessProvider:
“VZB” →; On-Net & Connected
“VZT” →; Off-Net & Connected
Else → Off-Net & Not Connected
The primary change is replacing the overall log mapping from being purely based on the Lit Capability that Verizon returns and instead reading out the logic from the base components available.
This change adds an 'NNI Location' attribute that enables NNI selection for the applicable supplier APIs.
We have enriched our Optimum integration with the capability to quote their Dedicated Internet product:
Fiber: 10M, 20M, 50M, 100M, 150M, 200M, 250M, 500M, 1000M.
TCW Enhancements
A new "Request NNI(s)" button has been added to CPQ Step 2 (Configuration) that allows users to review, override, and manually select NNI Locations for any or all requirements in a quote — directly from the configuration screen without navigating away. Clicking the button opens an expandable popup overlay displaying all locations in the quote/deal with their system-selected NNI, along with fields for Address, Site Group, Product Category, Commercial Product, Speed, Selected NNI Location, Selection Criteria, and an edit icon. Each row is pre-populated with the NNI determined by existing system logic (distance-based or rule-based), and users can override any selection individually or in bulk using a detailed "Select NNI Location" screen with geography pre-filtering and manual address search. A Selection Criteria column tracks how each NNI was determined — "Distance," "Rule," or "Manual" — and CPQ results honor manual selections as the highest priority, overriding both distance and rule-based logic.
Why it matters: Previously, users had no ability to override the system-selected NNI during the quoting process. If the default NNI (determined by distance or geography rule) was not the desired NNI due to existing infrastructure, contractual preferences, or business requirements — there was no mechanism to select an alternative. Users can now take direct control of NNI selection at the point of configuration, ensuring quotes reflect the intended NNI and associated supplier pricing, including cross-connect pricing when a Supplier NNI exists for the manually selected location.
How to use it: In CPQ Step 2, click the "Request NNI(s)" button near the bottom right and review the pre-populated NNI selections by quote location. Use the edit icon on any row to open the Select NNI Location screen to edit the NNI Location and save.
Who it's for: CPQ users and telecom buyers who need to override default NNI selections during the quoting process — particularly in scenarios involving preferred NNI locations, specific supplier infrastructure, or business requirements that differ from the system's distance-based or rule-based defaults.
Additional notes:
Manual NNI selections are the highest priority and override both distance-based and rule-based selections in CPQ results.
When a Supplier NNI exists for a manually selected NNI Location and product, it is returned with configured cross-connect pricing alongside the supplier's pricing results (e.g., DIA, Ethernet).
API-integrated customers can now submit an NNI Location in their POST Create Pricing request and have it honored for internally connected TCW suppliers — not just Carrier API suppliers. When a specific NNI Location address is submitted in apiRequestAttributes, the platform resolves the NNI using a three-step hierarchy: First, it checks for a matching NNI Geography Rule by address, supplier, and product category; if none is found, it looks up Active NNI Location records directly in the buyer's NNI Locations table; and if no matching record exists, it falls back gracefully to the existing proximity-based (Level 1) and geography rule (Level 2) NNI selection logic with an informative message at the supplier-result level. When NNI Location is not submitted or is set to "Nearest," existing default behavior is preserved with no change. Cross connect pricing is automatically applied from the matched NNI Location record when a Product Category match (or catch-all entry) exists.
Why it matters: Previously, the NNI Location override submitted via the API was only honored for specific Carrier API suppliers. For internally connected TCW suppliers, the platform always applied the default proximity-based or geography rule NNI selection — even when the buyer needed a specific NNI for business, contractual, or infrastructure reasons. Customers require the ability to select specific PoPs/NNI Locations when quoting because the nearest NNI may not always be the desired one depending on the circumstance. This feature closes that gap, giving API consumers full control over NNI selection across all supplier types in a single request.
How to use it: Submit the desired NNI Location address in the apiRequestAttributes field of your POST Create Pricing or POST Create Pricing with Site Groups request. The platform will resolve the NNI for each internally connected TCW supplier using the three-step hierarchy described above. Pricing results are returned for all matching NNIs with the corresponding nniLocation and customerNniId fields populated in the GET prices response. If no match is found, the response includes an informative message at the supplier-result level — "NNI Location not found for [Supplier]. Default NNI Geography Rules applied." — and other suppliers in the same request are unaffected.
Who it's for: API-integrated customers and buyers who need to override the default NNI selection for internally connected TCW suppliers during automated quoting — particularly in scenarios involving preferred NNI locations, specific supplier infrastructure, or business requirements that differ from the system's distance-based or rule-based defaults.
The NNI Locations screen now includes a new "Supplier NNI ID" field, distinct from the Customer NNI ID, allowing buyers to capture supplier-specific NNI identifiers. The "Buyer NNI ID" field has been renamed to "Customer NNI ID," and the TCW internal "NNI Location ID" is now visible in the table. The NNI Geography Rules editor has been upgraded — instead of an ambiguous address-only dropdown, selecting an NNI Location now opens a detailed pop-up displaying all NNI fields (including Supplier NNI ID) with checkboxes for precise selection. Additional UX improvements include an updated table design, expandable columns that reveal full content inline, accessible horizontal scrolling, and a Manage Columns option with persistent settings across sessions. Export files and import templates have been updated to reflect all new and renamed fields.
Impact: Buyers with multiple supplier NNIs at the same location can now clearly distinguish between them when configuring NNI Geography Rules, eliminating the risk of incorrect NNI selection and failed quotes. The pricing engine now uses the specific NNI Location ID captured during rule creation, ensuring accurate NNI and pricing are returned. This resolves scenarios where identical address keys caused ambiguous rule mappings and pricing failures.
User action required: Customers with existing NNI Geography Rules where multiple NNIs exist for the same supplier at the same location should review those rules to ensure the correct NNI is now selected using the new selection pop-up. CSMs may assist with this review. No changes are needed for single-NNI-per-location configurations.
Before vs After: Previously, the NNI Geography Rule editor displayed NNI Locations in a dropdown showing only the address — when two NNIs shared the same address, there was no way to distinguish between them during the quoting process. Now, selecting an NNI Location opens a detailed pop-up showing Supplier NNI ID, Customer NNI ID, address, and all other NNI fields, allowing admins to clearly identify and select the intended NNI.
Deal Desk users can now formally reject a request directly from the Requests Work-in-Progress (WIP) view using a new "Reject Request" action. When rejecting, the user is presented with the high-level details of the request, a required dropdown of standardized Rejection Reasons, and a required notes field to explain the rejection. Upon submission, the request is moved to a terminal CBM-Rejected status — which cannot be reopened — and all associated Requirement-level statuses are automatically set to Canceled. The rejection note is captured as a message in the request's message section, the requester receives a detailed email notification with the rejection reason and notes, and activity log entry is recorded.
Why it matters: Previously, Deal Desk had no formal mechanism to reject requests that could not or would not be worked — such as duplicates, requests with inaccurate locations, or submissions missing critical information. Without a structured rejection workflow, these requests remained in an ambiguous state, creating noise in the WIP queue and leaving requesters without clear feedback. This feature gives Deal Desk a clean, auditable way to close out unworkable requests, keeps the WIP queue focused on actionable items, and ensures requesters are promptly notified with a clear reason and message so they can take appropriate next steps.
How to use it: From the Requests WIP view at the Request level, users with Deal Desk or Deal Desk Management permissions will see a new Reject Request action. Clicking it opens a rejection form showing the request's high-level details. Select a Rejection Reason from the dropdown, enter a required explanation in the notes field, and submit.
Who it's for: Deal Desk users and Deal Desk Managers who need to formally close out requests that cannot be worked, and CPQ requesters who need timely, structured feedback when their request is not accepted.
Supplier admins can now manage which users are available as contacts for CBM Supplier Pricing Requests through a user group setting called [CBM] Supplier Pricing Response. Admins can enable this setting from Admin → User Group Settings on an existing or new user group. Users in that group will appear as selectable contacts when buyers create Supplier Pricing Requests for that supplier. The setting tooltip reads: “Users are able to respond to CBM Pricing Requests from connected buyers.”
Why it matters: CBM Respond was previously managed as a per-user SuperAdmin entitlement, which required Connectbase support and gave supplier admins limited visibility or control. Moving it to User Group Settings gives suppliers a self-service way to manage their CBM response contacts, keep contact lists current, and remove stale or test users from buyer-facing workflows.
Release note: Upon release, any instance with one or more users who already have the CBM Respond entitlement will automatically receive a new user group called [CBM] Supplier Pricing Response. All users with the existing CBM Respond entitlement will be added to that group automatically. Admins can then audit, amend, or delete the group as needed. This preserves continuity of the user experience while giving admins control going forward.
How to use it: Go to Admin → User Group Settings, find [CBM] Supplier Pricing Response, and enable it for the group that should receive CBM Supplier Pricing Requests. Add or remove users from that group as contacts change. Users in the enabled group will be available to buyers as suggested Supplier Pricing Request contacts; removing a user from the group removes them from that contact list.
Deal Desk and CPQ users can now send and receive follow-up messages directly to and from supplier contacts on Supplier Pricing Requests — without leaving the Requests Work-in-Progress (WIP) view. A new "Add External Note" option has been added to the Messaging/Envelope icon at both the request and requirement level. When selected, a dialogue box with a rich text editor opens, allowing the user to compose and send a message. Upon sending, the note is captured in the messaging screen and highlighted in yellow to visually distinguish external notes from internal notes. An email notification is delivered to the original supplier contact with a formatted subject line, the message content, a CBM link to view (but not edit) the requirements and any previously submitted pricing, and a Reply button. Suppliers can reply directly from the email using a rich text editor, and upon saving, receive a confirmation that their message has been sent. The reply is then delivered to the Deal Desk or CPQ user via email with a View button that navigates directly to the relevant messaging view in Requests WIP.
Why it matters: This feature enables structured, trackable, two-way messaging between Deal Desk users and supplier contacts — keeping all communication tied to the specific request or requirement, reducing response times, and ensuring nothing is lost outside the platform.
How to use it: From the Requests WIP, click the Messaging/Envelope icon on any request or requirement and select "Add External Note." Compose your message and send. The supplier receives an email with the message and a Reply button — they can respond directly from the email without needing platform access. Their reply is delivered to you via email with a link back to the request or requirement messaging view in WIP, and the message thread is visible in the messaging screen.
Who it's for: Deal Desk users, CPQ users, and supplier contacts involved in Supplier Pricing Requests who need to exchange follow-up messages — whether to clarify requirements, request additional information, negotiate terms, or coordinate on pricing details.
Issues resolved in this release
Connectbase resolved the following issues in this release.
Internal Ref # | Issue/resolution |
|---|---|
Lumen – Off-Net Last Mile Provider Mapping Improved the Last Mile Provider displayed for Lumen Off-Net quotes in CPQ. Previously, the Last Mile Provider field always displayed Lumen Technologies for external API suppliers, even when Lumen returned the actual Off-Net carrier in its response. With this update, TCW now consumes the offnetVendorName value returned by the Lumen API and displays it as the Last Mile Provider for Off-Net services. If offnetVendorName is not present in the API response (for example, On-Net scenarios), the existing behavior is maintained and the supplier name continues to be displayed. Example:
Impact:
|
Connectbase Software Release Notes
New features and enhancements in this release
Connectbase introduced the following new features, enhancements and bug fixes in this release.
API Enhancement
AT&T AIA has been implemented as an available External API integration with the following details.
Supported Countries: United States of America
Covered Products: Following products, access mediums and speeds are supported:
AIA - Broadband | Copper, Fiber:: 0.768/0.128, 0.768/0.384, 0.768/0.768, 1/1, 1.5/0.384, 1.5/1.5, 3/0.512, 6/0.768, 12/1, 18/1.5, 24/3, 25/5, 25/25, 40/40, 45/6, 50/5, 50/10, 50/50, 70/70, 75/8, 100/10, 100/20, 100/100, 110/20, 150/5, 150/10, 150/20, 150/150, 200/10, 200/15, 200/20, 200/40, 200/200, 250/10, 250/15, 250/20, 250/25, 275/275, 300/20, 300/30, 300/75, 300/300, 400/20, 400/400, 500/25, 500/35, 500/50, 500/100, 500/500, 940/880, 1000/35, 1000/50, 1000/200, 1000/1000, 2000/2000, 5000/5000
Supported Terms: 12 Months
Telstra Quote has been implemented as an available External API integration with the following details.
Supported Countries: Australia
Covered Products: Following products, access mediums and speeds are supported:
Ethernet Access (Ethernet - Switched | Fiber, Copper): 0.5, 1, 2, 4, 6, 8, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 150, 200, 300, 400, 500, 600, 800, 1000, 2000, 5000, 10000
Managed Leased Line (Ethernet - Dedicated (P2P) | Fiber): 2, 4, 6, 8, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 150, 200, 250, 300, 350, 400, 450, 500, 600, 700, 800, 900, 1000, 1250, 1500, 1750, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 6000, 7000, 8000, 9000, 10000
Supported Terms: 12, 24, 36 Months
KPN B.V. has been implemented as an available External API integration with the following details.
Supported Countries: Netherlands
Covered Products: Following products, access mediums and speeds are supported:
WEAS (Ethernet - Switched) | Fiber): 1, 2, 3, 4, 5, 6, 8, 10, 15, 20, 30, 50, 80, 100, 200, 300, 500, 800, 950, 1000
WEAS MBE (Ethernet - Switched: 1, 2, 3, 4, 5, 6, 8, 10, 15, 20, 30, 50, 80, 100, 200, 300, 500, 800, 950, 1000
Fiber: 1, 2, 5, 10, 20, 50, 100
Copper: 1, 2, 5, 10, 20
DWDM (Wavelength) | Fiber: 1000, 2000, 10000, 100000
Supported Terms: 12, 24, 36, 60 Months
Colt has been implemented as an available External API integration with the following details.
Supported Countries: Austria, Switzerland, Spain, Denmark, Sweden, United Kingdom, Germany, Italy, France, Luxembourg, Portugal, Norway, Finland, Belgium, Ireland, Netherlands
Covered Products: Following products, access mediums and speeds are supported:
Colt Ethernet Hub and Spoke | Fiber): 2 Mbps, 4 Mbps, 6 Mbps, 8 Mbps, 10 Mbps, 20 Mbps, 30 Mbps, 40 Mbps, 50 Mbps, 60 Mbps, 90 Mbps, 100 Mbps, 150 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 600 Mbps, 1 Gbps, 2 Gbps, 3 Gbps, 4 Gbps, 5 Gbps, 6 Gbps, 10 Gbps, 20 Gbps, 30 Gbps, 50 Gbps, 60 Gbps
Colt Ethernet Line | Fiber): 2, 4, 6, 8, 10, 20, 30, 40, 50, 60, 90, 100, 200, 300, 400, 500, 600 Mbps, 1, 10, 40, 100 Gbps.
Colt IP Access | Fiber): 1 Mbps, 2 Mbps, 3 Mbps, 4 Mbps, 5 Mbps, 6 Mbps, 7 Mbps, 8 Mbps, 9 Mbps, 10 Mbps, 12 Mbps, 14 Mbps, 16 Mbps, 18 Mbps, 20 Mbps, 30 Mbps, 40 Mbps, 50 Mbps, 60 Mbps, 70 Mbps, 80 Mbps, 90 Mbps, 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 600 Mbps, 700 Mbps, 800 Mbps, 900 Mbps, 1 Gbps, 2 Gbps, 3 Gbps, 4 Gbps, 5 Gbps, 6 Gbps, 7 Gbps, 8 Gbps, 9 Gbps, 10 Gbps
Colt Wave | Fiber): 1 Gbps, 2 Gbps, 2.5 Gbps, 4 Gbps, 8 Gbps, 10 Gbps, 40 MGbps, 100 MGbps
Supported Terms: 12, 24, 36, 48, 60 Months
Previously, AT&T Alliance broadband products were limited to month-to-month (MTM) term availability through the Retail Platform. This update expands broadband to be available across all supported term lengths, allowing buyers to receive results for a wider range of term requests.
TCW Enhancements
API-integrated customers can now discover and submit supplier-specific request attributes (such as physicalLink, Cloud Provider, Fixed Wireless Plan, NNI Location, etc.) directly through the Advanced CPQ v3 API. A new discovery endpoint (GET /v3/accounts/{accountId}/deals/{dealId}/quotes/config/attributes) returns all available apiRequestAttributes for the company's connected suppliers, grouped by supplier and product — including valid values, attribute level, and effective defaults after customer-level overrides. A new optional apiRequestAttributes field has been added to the productCriteria object in both POST Create Pricing and POST Create Pricing with Site Groups, allowing consumers to submit attribute selections as part of the pricing request. Validation is enforced on unrecognized keys and invalid values, and submitted attributes are persisted on the resulting quote record.
Impact: API consumers no longer need out-of-band knowledge of each supplier's attribute schema or manual intervention through the TCW UI to configure supplier-specific parameters when creating pricing requests. This enables full programmatic control over supplier options across 13+ active suppliers, supporting use cases like NNI Location selection, Class of Service, Port Bandwidth, Cloud Provider, and more — all via the API. Site Groups can be leveraged for per-location attribute differentiation within a single request.
User action required: API consumers who wish to use this capability should call the new discovery endpoint to retrieve available attributes for their configured suppliers, then include the desired selections in the apiRequestAttributes field of their POST Create Pricing or POST Create Pricing with Site Groups requests. If no attributes are submitted, the platform applies the effective defaults — no changes are required for existing integrations.
Before vs After:
Before: Supplier-specific request attributes (e.g., physical link type, billing method, cloud provider) could only be selected through the TCW user interface. API consumers had no way to discover or submit these options programmatically.
After: A dedicated discovery endpoint exposes all available attributes per supplier and product, and the pricing endpoints accept attribute selections directly — enabling end-to-end API-driven quoting with full supplier configuration control.
The CPQ Step 3 Results Grid now displays a "Location Type" column that explicitly identifies whether each result is an A-Z Location (Point-to-Point) quote or a Simple Location (Single-Site) quote. This value is carried forward from the existing Location Type field in Validation Step 2. Additionally, Location Type has been added as a selectable condition in CPQ Rules, with a single-select dropdown offering "A-Z Location" and "Simple Location" as the available values.
Impact: Previously, there was no explicit indicator in CPQ Step 3 to distinguish between Point-to-Point and Single-Site quotes. Rule authors had to rely on formula-based flags or indirect field values that were unreliable — especially in Hub → Spoke → Buyer architectures with sub-quoting enabled. This made it difficult to write CPQ rules that accurately targeted one quoting type over the other, increasing the risk of incorrect pricing or solution visibility in reseller and multi-instance use cases. With Location Type now visible in the grid and available as a rule condition, users can write precise CPQ rules that apply only to P2P or only to Single-Site quotes.
User action required: No action is required for existing workflows. To take advantage of this enhancement, users can create new or edit existing CPQ Rules and add "Location Type" as a condition, selecting either "A-Z Location" or "Simple Location." The Location Type column will automatically appear in the CPQ Step 3 Results Grid for all quotes going forward.
Before vs After: Previously, CPQ Step 3 did not expose the quoting type, so users could not visually distinguish between A-Z Location (P2P) and Simple Location (Single-Site) results, nor could they write CPQ Rules based on this distinction. Now, the Location Type is displayed as a column in the CPQ grid carried forward from Validation Step 2, and is available as a single-select condition in CPQ Rules — enabling targeted rule logic based on quoting type.
Hub Type is now available as a selectable condition in Activity Rules, CPQ Rules, and Financial Rules. When selected, the value dropdown is automatically pre-populated with only the Hub Type values present in the Supplier Capability Matrix for suppliers the user is connected to. Rules containing a Hub Type condition are evaluated against the Hub Type value in quote results and applied only when a match is found.
Impact: Customers such as Vodafone can now create targeted rules based on Hub Type — for example, writing capacity check rules in Activity Rules with specific criteria for ENNI hub types versus other hub types. This eliminates the need for broad, less precise rule conditions and enables more granular control over rule execution based on supplier capability data.
User action required: No action is required for existing rules. To take advantage of this enhancement, users can create new or edit existing Activity Rules, CPQ Rules, or Financial Rules and add Hub Type as a condition. Hub Type values will only appear in the dropdown if they have been configured in the Supplier Capability Matrix for connected suppliers.
Before vs After: Previously, there was no way to use Hub Type as a condition when creating rules, so users could not differentiate rule behavior based on hub type (e.g., ENNI vs. other types). Now, Hub Type is available as a condition across all three rule types, with values dynamically sourced from the Supplier Capability Matrix.
Improvements:
Centralized autocomplete across TCW workflows including My Locations, My Accounts, My Locations spatial search, Quoting, the TCW landing page map search, and the Business Partner Portal.
Expanded global address autocomplete coverage with stronger support for international address formats and partial address entry.
Added data center search by name, code, or associated address, with a visual distinction between the name and address.
Reduced duplicate address suggestions for a cleaner, more consistent, and less cluttered results list.
Improved reliability for address searches containing apostrophes and special characters.
Impact: .
Users can find accurate service addresses faster and with fewer manual corrections.
The address search experience is more consistent across all areas of the platform.
Quote Desk users can select the correct data center facility without needing the exact street address.
Cleaner suggestions reduce selection errors and improve the overall search experience.
Issues resolved in this release
Connectbase resolved the following issues in this release.
Internal Ref # | Issue/resolution |
|---|---|
Comcast (Advanced CPQ v3) – Expanded High-Speed COAX/HFC Support We've extended high-speed serviceability for Comcast COAX/HFC results. What's New:
Why it Matters: You can now quote and close higher-bandwidth Ethernet services on Comcast COAX where they're genuinely available, removing the previous silent failures on 300M and 500M requests and giving you accurate pricing across the full supported speed range. | |
API Audit Log Elapsed Time Resets and Shows Incorrect Values Issue: The elapsed time displayed in the API Audit Log on CPQ Step 3 reset to zero each time a user clicked the "Details" link to view the log and then closed it. The elapsed time in the Audit Log also did not match the elapsed time shown in the CPQ Step 3 API Status bar. Additionally, after a quote completed processing, the status bar elapsed time displayed 0:00 instead of the total elapsed time. Resolution: Fixed the backend to save the pricing start time on the first pricing run. Previously, the start time was only saved when a user clicked Refresh, leaving it blank on the initial run. The backend now reads start and end times consistently, and the elapsed time is displayed uniformly across the Audit Log and the API Status bar. Note: This fix applies to quotes priced from this release forward. Older quotes will reflect the corrected behavior once re-priced. Impact: All CPQ users who monitor pricing progress via the API Audit Log or API Status bar on CPQ Step 3 were affected. The inconsistent timers made it difficult to accurately track how long pricing was taking or had taken to complete. |
Connectbase Software Release Notes
New features and enhancements in this release
Connectbase introduced the following new features, enhancements and bug fixes in this release.
API Enhancement
Orchest MEF has been implemented as an available External API integration with the following details.
Supported Countries: ANGUILA, ANTIGUA & BARBUDA, ARGENTINA, BAHAMAS, BARBADOS, BELIZE, BERMUDA, BOLIVIA, BRAZIL, CANADA, CAYMAN ISLANDS, CHILE, COLOMBIA, COSTA RICA, DOMINICA, DOMINICAN REPUBLIC, ECUADOR, EL SALVADOR, FRENCH GUYANA, GRANADA, GUADALUPE, GUATEMALA, GUYANA, HAITÍ, HONDURAS, JAMAICA, MARTINIQUE, MÉXICO, MONTSERRAT, NETHERLANDS ANTILLES, NICARAGUA, PANAMÁ, PARAGUAY, PERÚ, PUERTO RICO, SAINT KITTS & NEVIS, SAINT VINCENT AND THE GRANADINES, SAINT LUCIA, SURINAME, TRINIDAD & TOBAGO, TURKS AND CAICOS, UNITED STATES OF AMERICA, URUGUAY, VIRGIN ISLANDS (BRITISH), VIRGIN ISLANDS (US), VENEZUELA
Covered Products: Following products, access mediums and speeds are supported:
Ethernet (Ethernet - Switched | Fiber): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000
DIA (Dedicated Internet | Fiber, Wireless, Satellite): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000
MPLS (MPLS | Fiber, Wireless, Satellite): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000
Broadband (Broadband | Fiber, Wireless, Satellite): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000
Cross X (Ethernet - Switched | Fiber, Wireless, Satellite): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000
Supported Terms: 12, 24, 36 Months
Bell Canada WSS has been implemented as an available External API integration with the following details.
Supported Countries: Canada
Covered Products: Following products, access mediums and speeds are supported:
Ethernet Internetworking EVPL (Ethernet - Switched | NNI Required | Fiber): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 150, 200, 300, 400, 500, 600, 700, 800, 900, 1000
Ethernet Internetworking EPL (Ethernet - Dedicated | P2P Required | Fiber): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 150, 200, 300, 400, 500, 600, 700, 800, 900, 1000
Supported Terms: 12, 24, 36, 60 Months
Axtel API has been implemented as an available External API integration with the following details.
Supported Countries: Mexico
Covered Products: Following products, access mediums and speeds are supported:
ELine (Ethernet Switched | Fiber): 10 Mbps, 20 Mbps, 30 Mbps, 40 Mbps, 50 Mbps, 60 Mbps, 70 Mbps, 80 Mbps, 90 Mbps, 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 600 Mbps, 700 Mbps, 800 Mbps, 900 Mbps, 1000 Mbps
Supported Terms: 12, 24, 36 Months
Verizon Quote integration has been updated to no longer support quoting for the Dedicated E-Line and Internet Dedicated Ethernet (IDE) products, based on the Verizon Partner Solutions Exchange July 2026 API Release Preview.
Please note that with the deprecation of IDE, Verizon’s Internet Dedicated+ product must now be quoted for internet services.
We have enabled the following speeds to be quoted in France via Eurofiber WAZA:
Dedicated Internet (Fibre FTTO): 30M, 40M, 50M, 400M
Ethernet - Dedicated (Fibre FTTO): 30M, 40M, 50M, 400M, 2G
Dedicated Internet (Fibre FTTO): 30M, 40M, 50M, 400M, 2G, 3G, 4G
We have additionally enabled the following speeds to be quoted in Netherlands and Belgium via Eurofiber Network Availability:
Dedicated Internet (DIA - GigE Interface): 10M, 20M, 30M, 40M, 50M, 300M, 400M
Ethernet - Dedicated (P2Pop Ethernet - GigE RJ45 Interface): 10M, 20M, 30M, 40M, 50M, 300M, 400M
Dedicated Internet (Ethernet to NNI - GigE RJ45 Interface): 10M, 20M, 30M, 40M, 50M, 300M, 400M
A new "No Preference" option has been added as the default selection to the "Last Mile Provider" API Request Attribute on Dedicated Internet for the ESUN integration. When selected, no lastMileProvider is specified in the API request such that ESUN selects the value to return in the resultant quote.
TCW Enhancements
"Buyer" has been added as a new condition data field in Financial Rules, enabling sellers to create rules that apply margin, markup, or discounts on a per-connected-buyer basis. When selected, the value dropdown is pre-populated with the seller's connected buyers (displayed as Buyer Name & Instance Number). When a buyer-based rule is active and a connected buyer makes a pricing request, the system evaluates and applies the rule — presenting the adjusted price as Provider MRC/NRC without exposing the underlying markup or margin to the buyer.
Additionally, in CPQ Rules, the existing "Buyer" field — which was actually pulling connected suppliers — has been renamed to "Supplier" to accurately reflect its function. A new, correct "Buyer" field has been added to CPQ Rules that properly pulls in connected buyers.
Impact: Sellers — particularly resellers — can now self-service buyer-specific pricing rules directly in the rules engine without requiring custom stored procedures for each buyer. This eliminates manual intervention, reduces dependency on engineering for each new buyer setup, and corrects a field-naming inconsistency in CPQ Rules that could cause confusion.
User action required: Sellers who previously relied on stored procedures to manage buyer-level margin should create equivalent Financial Rules or CPQ Rules using the new "Buyer" condition. Existing rules and stored procedures remain functional and are unaffected. In CPQ Rules, note that the former "Buyer" field has been renamed to "Supplier" — its behavior is unchanged.
Before vs After:
Before: No "Buyer" condition available in Financial Rules or CPQ Rules. Buyer-specific margin/markup required a custom stored procedure per buyer instance. In CPQ Rules, the "Buyer" field label incorrectly referenced connected suppliers.
After: "Buyer" is available as a condition in both Financial Rules and CPQ Rules. Sellers can create and manage buyer-specific pricing rules through the UI. The CPQ Rules field that pulls suppliers is now correctly labeled "Supplier."
A new end-to-end workflow that allows Deal Desk and CPQ/Sales users to identify and revalidate supplier pricing that has expired. Expired pricing is now visually flagged across CPQ Step 3 results, WIP, and Requests WIP with alert icons, and a new "Revalidate Expired Pricing" engagement reason and action enable users to request that suppliers extend or update their pricing directly from the Requests WIP.
Why it matters: Previously, there was no built-in way to identify which quotes had expired supplier pricing or to ask suppliers to revalidate without starting a new request from scratch. This feature gives Deal Desk users immediate visibility into expired pricing across their workflows and a streamlined path to get updated pricing from suppliers — reducing quote turnaround time and preventing deals from stalling due to stale pricing.
How to use it:
Spot expired pricing: Look for the alert icon on requirements in CPQ Step 3 results, at the quote level in WIP, and at both the request and requirement levels in Requests WIP.
Filter for it: Use the new "Expired Pricing" quick filter in Requests WIP to surface all requests with one or more expired requirements.
Revalidate: Select the "Revalidate Expired Price" action on a request. You'll see a summary of suppliers with expired pricing, a list of affected requirements, pre-populated supplier contacts, and a notes field. Click send to notify the supplier via email with a link to the original request.
Supplier response: Suppliers receive the revalidation request in the Supplier Response Portal, where expired requirements are flagged. They must update the expiration date to a future date before submitting. If the supplier only extends the expiration (no price change), the requirement is auto-approved. If pricing also changes, the requirement moves to "Pricing Received" for Deal Desk review.
Who it's for: Deal Desk users, CPQ/Sales users, and suppliers who respond to pricing requests through the Supplier Response Portal.
Additional notes: The engagement reason "Revalidate Expired Pricing" is also available in the Internal Bid Management and Supplier Pricing Request forms, and will be pre-populated when the pricing is expired. Supplier Price Expiration and Supplier Quote ID fields have been added to both forms. Requirements currently in an active CBM process will not reflect the most current expiration date in CPQ Step 3 until the requirement is pushed back from CBM. Alert icons only appear for in-progress CBM requests — completed, rejected, no-bid, closed, and canceled requirements are excluded.
A comprehensive activity log that captures a complete, timestamped history of all actions taken on CBM requests and their individual requirements. Two new collapsible sections — "Request Activity Log" and "Requirement Activity Log" — are available within the Request Details and Requirement Details panels in WIP/Requests (Global & My Requests).
Why it matters: Previously, there was no centralized way to understand how a request was initiated, who touched it, why statuses changed, or when it moved through major workflow stages. Users had to piece together the history from scattered sources. Activity logging gives Deal Desk and CBM users full transparency into the lifecycle of every request and requirement — supporting accountability, auditing, and faster troubleshooting when questions arise about how a request reached its current state.
How to use it:
Navigate to WIP/Requests (Global or My Requests) and click the info icon on a request to open Request Details. Expand the Request Activity Log section under Notes/Messaging to see request-level history.
Click into a requirement to open Requirement Details and expand the Requirement Activity Log section for requirement-level history.
Each log entry includes the user who performed the action (or the auto-assignment rule name, if applicable), a plain-language description of the action, and a formatted date/timestamp.
Request-level events logged include: request creation (Internal Bid Management or Direct Engagement), request assignment/unassignment (manual and auto-assignment), sending pricing requests to suppliers, supplier responses received, and request closure upon completion of all requirements.
Requirement-level events logged include: requirement assignment/unassignment (manual and auto-assignment), pricing requests sent to specific supplier contacts, supplier chase reminders, supplier responses (pricing received or no bid), user-added or user-edited prices (with product, speed, address, MRC/NRC, and disposition details), requirement approval or rejection, requirement cancellation, and automatic closure due to past-due status.
Who it's for: Deal Desk users, CBM users, and anyone with access to the Requests WIP who needs visibility into the full history of a request or requirement.
Additional notes: Auto-assignment events — whether triggered by CBM rules at the request level or auto-assignment rules at the requirement level — are logged with the rule name that initiated the assignment. When some (but not all) requirements within a request are assigned, the request-level log notes the partial assignment and directs users to the requirement-level log for details.
A new Export button has been added to the Requests WIP page header toolbar (immediately left of the Analytics button), enabling CBM users to download request and requirement data as a CSV file. The Export dialog provides configurable options including scope (Global Requests or My Requests), level of detail (Request level or Request + Requirement level), status filters with Include/Exclude modes, Request ID filtering, and a created date range filter. A live preview row count updates in real time as filters are adjusted, and the Export CSV button is disabled when no rows match.
Impact: CBM users can now analyze request and requirement data outside the platform without manual data gathering. Request-level exports produce one row per request with key fields (Request ID, Account, Deal, Quote Name, Status, Created/Due Dates, Engagement Reason, Requester, Assigned, Quote Type, and more). Request + Requirement–level exports include all request fields plus detailed requirement data (Supplier, Address, Product, Speed, Term, MRC/NRC, Disposition, Requirement Status, and 20+ additional fields) — one row per requirement. Status filters operate independently per level, and request-level filters (date range, Request ID) cascade to requirements, ensuring child requirements are excluded when their parent request is filtered out.
User action required: None. The Export button is available on the Requests page for users with CBM access.
Before vs After:
Before: No way to export request or requirement data from the Requests WIP. Users had to manually compile data outside the system for reporting or analysis.
After: A single Export action with flexible filtering options produces downloadable CSV files at the request or request + requirement level, with real-time row count previews and proper file formatting for spreadsheet use.
A new in-platform messaging system has been added to the Requests WIP, enabling Deal Desk and CPQ users to communicate directly at both the request and requirement level. A new envelope icon appears next to the info icon on each row — clicking it opens a dedicated messaging screen where users can compose internal notes and view full message history in an expandable, threaded layout. Each sent message triggers both an email notification (with a direct "View Request" or "View Requirement" link back to the WIP) and an in-platform notification under a new "CBM Notifications" tab in the notification center, which can be set as the default view. Unread messages are indicated by a red dot on the envelope icon, and a new "New Messages" quick filter in My Requests surfaces requests with unread messages.
Impact: Deal Desk and CPQ users now have a structured, centralized way to exchange follow-up messages directly within the request or requirement they relate to — eliminating reliance on ad-hoc external channels and ensuring communication context stays tied to the work item. Email and in-platform notifications keep recipients informed without requiring them to manually check for updates.
User action required: None. The envelope icon and messaging functionality are available on the Requests WIP for all Deal Desk and CPQ users.
Before vs After:
Before: No built-in messaging between Deal Desk and CPQ users within the Requests WIP. Follow-up communication happened through external channels with no direct link to specific requests or requirements.
After: Users can send and view threaded internal messages at both the request and requirement level, with automatic email and in-platform notifications, unread indicators, and a quick filter to find requests with new messages.
Note: This release covers internal messaging only (Deal Desk ↔ CPQ). External messaging to suppliers is planned in a future release. The existing notes/messaging section in the Requirement and Request Level Details panel is retained until external messaging is available.
A new "Find Suppliers" button has been added to the Quoted section of the Supplier Pricing Request form, allowing users to search for additional suppliers directly from their existing quoted results.
Why it matters: Previously, after receiving pricing back from a supplier, there was no way to search for additional options from within the Quoted section — users could only find suppliers from the Fallout section. This enhancement gives users more flexibility to explore alternative suppliers without leaving their current workflow.
How to use it: When viewing a Supplier Pricing Request (via Direct Engagement or Deal Desk flow), look for the new "Find Suppliers" button in the Quoted section. It works the same way as the existing button in the Fallout section.
Who it's for: CBM users who submit and manage Supplier Pricing Requests.
Issues resolved in this release
Connectbase resolved the following issues in this release.
Internal Ref # | Issue/resolution |
|---|---|
Advanced CPQ v3 GET Prices API Missing Carrier Zone Field Issue: The Advanced CPQ v3 GET Prices API was not returning the "Carrier Zone" field in the response, even though the field was visible in the CPQ UI and documented in the API specification. Customers using the v3 API were unable to retrieve carrier zone data for their quotes. Resolution: The carrierZone field has been added to the GET Prices endpoint in Advanced CPQ v3. When carrier zone data is available, it returns an array containing the tier type and value. When no data is available, the field returns an empty array ([]) to maintain a consistent response structure. Impact: Customers who migrated from the v2 API to v3 — at Connectbase's recommendation — were unable to access carrier zone information needed for their quoting workflows. |
Connectbase Software Release Notes
New features and enhancements in this release
Connectbase introduced the following new features, enhancements and bug fixes in this release.
API Enhancement
A1 Telekom Austria AG has been implemented as an available External API integration with the following details.
Supported Countries: Austria
Covered Products: Following products, access mediums and speeds are supported:
Internet Access (Fiber / Mobile / Copper):
Dedicated Internet: 2, 4, 6, 8, 10, 15, 20, 30, 40, 50, 60, 80, 100, 150, 200, 250, 300, 400, 500, 600, 700, 800, 900, 1000 Mbps
Broadband:
Asymmetric: 2/0.2, 6/0.5, 10/1, 16/2.5, 20/8, 40/15, 50/20, 80/25, 100/30, 150/40, 300/50, 500/70, 700/80, 1000/100 Mbps
Symmetric: 2/2, 4/4, 8/8, 16/16, 20/20 Mbps
L2 Ethernet - Ethernet Switched - Fiber: 2, 4, 6, 8, 10, 15, 20, 30, 40, 50, 60, 80, 100, 150, 200, 250, 300, 400, 500, 600, 700, 800, 900, 1000 Mbps
Supported Terms: 12, 24, 36, 60 Months
DNA API has been implemented as an available External API integration with the following details.
Supported Countries: Finland
Covered Products: Following products, access mediums and speeds are supported:
Ethernet VPN (Ethernet - Switched on Fiber Access Medium): 2 Mbps, 5 Mbps, 10 Mbps, 20 Mbps, 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1Gbps, 2Gbps, 3Gbps, 4Gbps, 5Gbps, 6Gbps, 7Gbps, 8Gbps, 9Gbps, 10Gbps
Ethernet VPN Wireless (Ethernet - Switched on Wireless Fixed Access Medium): Mbps, 10 Mbps, 50 Mbps, 100 Mbps, 200 Mbps, 400 Mbps, 600 Mbps, 1000 Mbps
Internet Access (Dedicated Internet on Fiber Access Medium): 2 Mbps, 5 Mbps, 10 Mbps, 20 Mbps, 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1Gbps, 2Gbps, 3Gbps, 4Gbps, 5Gbps, 6Gbps, 7Gbps, 8Gbps, 9Gbps, 10Gbps
Internet access Wireless (Dedicated Internet on Wireless Fixed Access Medium): 2 Mbps, 10 Mbps, 50 Mbps, 100 Mbps, 200 Mbps, 400 Mbps, 600 Mbps, 1000 Mbps
IPVPVN (MPLS on Fiber Access medium): 2 Mbps, 5 Mbps, 10 Mbps, 20 Mbps, 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1Gbps, 2Gbps, 3Gbps, 4Gbps, 5Gbps, 6Gbps, 7Gbps, 8Gbps, 9Gbps, 10Gbps
IPVPVN Wireless (MPLS on Wireless Fixed Access Medium): 2 Mbps, 10 Mbps, 50 Mbps, 100 Mbps, 200 Mbps, 400 Mbps, 600 Mbps, 1000 Mbps
Broadband (Broadband on Fiber Access Medium): 200/100 Mbps, 400M/200 Mbps, 600M/300 Mbps, 1000M/500 Mbps, 2000M/1000 Mbps
Broadband Wireless (Broadband on Wireless Fixed Access Medium): 50/10 Mbps, 200/200 Mbps, 200/100 Mbps, 400/320 Mbps, 600/320 Mbps, 1000/320 Mbps
Supported Terms: 12, 24, 36 Months
We are updating the following supplier API integrations to return provided the Last Mile Provider (last_mile_supplier) value that they provide in their respective payloads in our CPQ results:
Earthlink Partner Connect
AT&T New Experience SQ
AT&T Wholesale Service Qualification
Resolute Nexus
Spectrum Charter GIS
When this value is not provided by the API response, the supplier themselves will be displayed in this field. This change improves the level of detail concerning the returned Building Connection Status and Network Connection Status, as the information is available.
The Qoolize API was returning an outdated error message for error code 2301 that referenced a monthly reset period, which no longer reflected the actual API behaviour.
The error code 2301 message was updated to reflect the correct daily reset period. Daily and monthly rate limits confirmed with the supplier and updated in Confluence accordingly. Customers will now see an accurate error message when the daily limit is reached, clearly indicating the limit resets at midnight.
TCW Enhancements
A new action button at the request level that allows users to send follow-up reminders to suppliers who haven't yet responded to a CBM pricing request. Users can select one or more suppliers in a "Waiting for Supplier" status, review the request summary, and send a chase notification — all from within the Requests tab.
Pricing delays from unresponsive suppliers slow down deal cycles. This feature gives users a streamlined way to nudge suppliers directly from the platform, reducing back-and-forth and helping ensure bids are returned on time.
How to use it: From a pricing request, click the Chase Supplier action button. Select the supplier(s) you'd like to follow up with, review the pre-populated details (due date, contacts), add any notes, and click Send. The supplier will receive an email reminder with a link back to the original bid request.
Who it's for: Deal Desk or CPQ users managing supplier pricing requests.
Additional notes:
When a supplier is chased, their status updates from Waiting on Supplier to Supplier Chased.
The "Waiting on Supplier" filter now includes both Waiting on Supplier and Supplier Chased statuses.
Configurable email templates for the chase notification are planned for a future release.
An enhancement to the Supplier Pricing Request form that automatically suggests all Linkbase "My Partners" suppliers who can serve a location when preferred suppliers have not been configured in Linkbase-My Partners.
Many customers haven't yet configured preferred suppliers, which means the Supplier Pricing Request form returns no auto-suggestions for fallout — reducing its value. This update ensures users get immediate, relevant supplier suggestions out of the box by leveraging the partners they've already established in Linkbase.
How to use it: When creating a Supplier Pricing Request, the fallout section now works as follows:
No preferred suppliers configured? The system automatically suggests any My Partners supplier that can serve the country based on Linkbase settings.
Preferred suppliers configured? Only preferred suppliers are pre-suggested (existing behavior).
Find Suppliers search: Use the new My Partners checkbox to filter Network Intelligence results to only show suppliers in your My Partners list.
Who it's for: Deal Desk users and CPQ users managing supplier pricing requests and fallout workflows.
A new Admin setting under User Management → User Groups called [CPQ] Restrict Generate and Send Quote, When enabled for a user group, users in that group are prevented from advancing past CPQ Step 3 (Pricing and System Reference Data), effectively blocking them from generating or sending quotes.
Not all users should have the authority to generate and send quotes. Previously, there was no way to restrict this at the user group level, meaning any CPQ user could proceed through all steps. This setting gives Admins granular control over who can generate quotes, supporting better governance and approval workflows.
How to use it:
Navigate to Admin → User Management → User Groups and select a user group.
Enable the [CPQ] Restrict Generate and Send Quote setting and save.
Users in that group will now see the Next button greyed out on CPQ Step 3. Hovering over it displays: "You do not have permission to generate quote."
To restore access, simply de-select the setting and save.
Who it's for: Admins managing CPQ user permissions and entitlements.
Additional notes:
The setting is off by default and is not enabled on any existing user groups upon deployment — no existing workflows are impacted.
If a user belongs to multiple user groups and any one of them has this restriction enabled, the restriction is enforced.
Changes take effect immediately upon the user's next navigation to or refresh of CPQ Step 3.
The Media Type field in CPQ Step 2 and the Advanced CPQ v3 API is now optional. When no media type is selected, the system will return pricing across all configured media types for that instance. Making the field optional ensures all available media types are considered by default, giving buyers broader pricing visibility and increasing exposure for all providers on the platform.
How to use it:
CPQ Step 2: Simply leave the Media Type field blank during quote configuration. All configured media types will be included in the pricing request.
Advanced CPQ v3 API: Submit an empty array for mediaTypes (e.g., "mediaTypes": []) or omit the field entirely to request all configured media types.
Who it's for: CPQ buyers configuring quotes, API integrators using the Advanced CPQ v3 API who seek broader inclusion of media type options.
Additional notes: Admin-level media type exclusions configured via instance settings are respected — if an admin has excluded a specific media type from their instance, it will not be included even when no media type is selected.
An enhancement to Activity Rules that adds a new action type: CBM (Bid Management). Admins can now configure an Activity Rule to require CPQ users to initiate a CBM engagement — not just a generic approval — when specific conditions are met. The Activity Rules summary screen has also been redesigned for improved usability.
With the ability to now configure a Deal Desk to manage CBM requests, many scenarios that previously triggered a generic approval are better served by sending an Internal Bid Management Request to the Deal Desk/procurement team instead. Until now, Activity Rules only supported a single approval action, forcing teams to manage CBM requirements outside the system. This update lets Admins enforce CBM engagement directly through rules, ensuring quotes don't advance until Deal Desk has completed their review.
How to use it:
Setting up a rule:
Navigate to Admin → Rules → Activity Rules and click Add New Rule.
In the new Action section, choose one of two options:
Approval — works as before; assign to a user or user group and name the approval type (e.g., "Capacity Check").
CBM (Bid Management) — routes the request to Deal Desk automatically. No manual assignment is needed; use CBM Auto-Assignment Rules to configure routing.
Define your rule conditions and save.
What CPQ users see in Step 3:
If a CBM rule is triggered, the Next button changes to "Initiate CBM" — clicking it launches the CBM workflow just like the manual action menu option.
Specific requirements that have met the Activity Rule conditions will be flagged with a CBM or Approval label so users can easily see which requirement require action.
If an Approval rule is triggered, the existing "Approval Required" button and workflow remain unchanged.
If both rule types are triggered on the same request, the button displays "Action Required" and presents all outstanding actions that must be completed.
Who it's for: Admins configuring Activity Rules and CPQ users working through the quoting process.
Additional notes:
All existing Activity Rules are automatically defaulted to Action Type = Approval — no changes to current workflows upon deployment.
Users cannot advance past CPQ Step 3 until all triggered actions are resolved (approvals received and/or CBM requests completed so that rule condition no longer exists).
The Activity Rules summary screen now includes an Action column (color-coded: blue for Approval, yellow for CBM), a Description column, and Created Date and Modified Date columns for improved traceability.
Existing email notifications for Activity Rules apply only to the Approval action type — CBM actions follow standard CBM notification routing.
The Tenant API V2 now includes a new response field, totalMonthlyNetworkSpend, which returns the monthly network spend for the specific queried location.
Previously, the API only returned monthlyNetworkSpend, which represents the company-level aggregate spend across all locations. This made it difficult to determine how much spend belongs to a particular address when querying a single location.
UI Improvements:
Refreshed the Home button and page navigation button styles for improved visual consistency across the dashboard.
Updated button styles to match the refreshed navigation design language.
Market Page Improvements:
Renamed the "Solutions Found" summary card to "Solutions" and refined its definition: the metric now counts seller responses to Quote that contains a price (measured at location + config level).
The “Buyer Quote Request Results” bar chart has been updated to reflect Quote Requests only. Previously, this chart included all Request types; Serviceability-only Requests are no longer counted in this metric.
Product Page Improvements:
Refreshed summary cards: added tooltips for clearer definitions, removed the "Quotes" card, and added a "Solutions" card.
Renamed buttons for clarity: "API Overview" is now "Solutions Summary by API," and "Unique Locations by Product" is now "Quoted Locations Summary."
Renamed the "Solutions Found" field to "Solutions" across the Solutions metrics views and added thousands separators to numeric values.
Added tooltips to "Solutions Summary by Buyer" and "Quoted Locations Summary."
Renamed "Quote Requests by API Source" to "Requests by API Source" for consistent terminology.
Added "Solutions Found" and "Solutions" data points in the tooltips of the Requests by API Source graphs.
Improved the API Source view and Time Period view within "Requests by API Source".
Standardized pie chart and bar chart data labels to display in thousands by default.
Performance Page Improvements:
Updated summary cards:
Avg Quote Turnaround (min) — fixed the average call duration calculation to be weighted by call volume, providing a more representative measure of typical API performance. Renamed from "Avg API Call Duration (min)" to better reflect what the metric represents and aligns with business terminology.
Avg Quote Turnaround (Excl. Outliers) (min) — new card using the same volume-weighted calculation with outlier records excluded (calls exceeding 60 minutes), offering a cleaner view of standard response time unaffected by extreme values.
Added an error count data point to the tooltips of the Daily Success Metrics view and a success count data point to the tooltips of the Daily Error Metrics view.
Issues resolved in this release
Connectbase resolved the following issues in this release.
Internal Ref # | Issue/resolution |
|---|---|
P2P Address Import Issues in Deal View When uploading a Point-to-Point (P2P) address CSV file into a Deal, Z-end addresses were being overwritten by their corresponding A-end addresses. Additionally, imported address pairs were being sorted alphabetically rather than preserving the original row order, causing A-end and Z-end addresses to become mismatched. Validation of larger address sets (more than 15 pairs) also failed silently, with the import module disappearing without processing. Fixed CSV import parsing to correctly preserve A-end and Z-end address pairs as defined in the source file, and resolved the validation handling to support larger batch sizes. Affects users importing multi-location P2P address lists via CSV in CPQ Deal workflows. Without the fix, users had to manually re-enter addresses or limit imports to 15 pairs at a time. | |
CPQ Missing Quote Results When Same Location Appears in Multiple Site Groups When a customer submitted a quote with the same location included in multiple Site Groups (e.g., to compare different speed tiers or configurations), CPQ only priced the location on its first occurrence and silently dropped it from all other Site Groups. This caused quotes to return significantly fewer results than expected — for example, 3 locations across 6 Site Groups returned approximately 3 results instead of the expected 15. Updated the location deduplication logic to be Site Group–aware. Locations are now treated as unique per Site Group, so the same address appearing in multiple Site Groups is retained and priced independently in each one. Deduplication still applies within a single Site Group to prevent true duplicates. Affected customers using Site Groups to compare multiple configurations (speeds, terms, products) for the same location within a single quote. Deutsche Telekom was directly impacted, as this blocked their Site Group–based quoting workflow. | |
CSV Address Import Fails When Single Address Has Custom Fields When importing a single address via CSV upload that included custom fields (e.g., "Flex Field 1," "Flex Field 2"), the address silently disappeared from the import results. The Address Import modal would shrink and neither step 1 nor step 2 of the import process was visible — leaving users unable to select or submit the imported address. Updated the address validation logic to synthesize a canonical address key when Standard Address returns a fully resolved address without one. Added a safety net so that when the validation batch yields no results, the original input addresses are echoed back rather than returning an empty response — ensuring an address is never silently dropped. Affected users importing addresses via CSV in Deal workflows, particularly when addresses included custom fields and were resolved by Standard Address without an internal address key. |
Quote Visibility & Finalize Quote Features (Release 11)
How to Use Quote Configuration Templates for Faster Quoting (Release 11)
Unique Site Requirements by Site Group (Release 10)
New TCW Admin Features (Release 9 & Release10)