Skip to main content

Information Resource Center

What's New

Action Required / Breaking Changes

Note

  1. Advanced CPQ API supplier filtering: If your integration sends invalid or disconnected supplier names in providerInclude or providerExclude, update those names to valid connected suppliers; these requests now return HTTP 400 instead of silently widening the pricing request. See section 1.1 for details.

Release TCW.2026.R23 expands automated supplier coverage and gives teams greater control over quoting, partner administration and access to The Connected World (TCW). The changes support more informed supplier selection, more complete quote data and smoother day-to-day quoting workflows.

Buyer APIs

The Advanced CPQ API v2 and v3 now let buyers discover eligible connected suppliers and their supported product categories before requesting prices. Supplier-name validation helps prevent requests from unintentionally reaching all connected suppliers. Integrators should review supplier filters: invalid or disconnected names now cause an HTTP 400 response.

Seller APIs

New Seller Cloud APIs expand automated quoting coverage, while existing supplier integrations offer more products, speeds and pricing options.

New coverage

  • KALAAM TELECOM: A new Seller Cloud API provides pricing across Bahrain, Egypt, Jordan, Kuwait, Lebanon, Oman, Pakistan, Qatar, Saudi Arabia and the United Arab Emirates. Available services include Dedicated Internet, Ethernet, MPLS VPN and international private lines; coverage varies by product.

  • Netia: A new Seller Cloud API provides budgetary Ethernet and Dedicated Internet pricing in Poland.

Expanded supplier capabilities

  • Bell Canada WSS adds Dedicated Internet quoting; Optimum and Beyond Reach support additional speeds.

  • Ielo Eligibility expands its France offering with Ethernet, Broadband and burstable services as connections move to the Unified API Platform.

  • Colt eBonding improves pricing availability and supports optional third-party access pricing.

    Verizon Quote returns more supplier details in API Info.

Frontier ESB introduces scheduled WABB withdrawals beginning December 4, 2026, ahead of API retirement on April 2, 2027. Review the Action Required / Breaking Changes topic for affected states, connection prerequisites and compatibility considerations.

Administration & Security

Administrators gain more control over quoting and partner access. Teams can set a default P2P quoting view, constrain NNI selection by geography, export NNI rules and filter CPQ solutions by product name. Supplier Capability Matrices help fill missing quote details without overwriting supplier-provided values.

Business Partner Portal administration brings portal settings and sub-agency user management together.

TCW UI

Quoting teams can renegotiate submitted supplier pricing in CBM without recreating requests, with each negotiation round retained in the pricing history. Finalized quote details can now be exported directly from CPQ Step 4.

Clearer Finish Now progress messages and corrected supplier completion statuses make quote processing easier to follow. The Request NNIs modal now enforces product eligibility and displays configured speeds, helping prevent invalid NNI assignments.

1.1 Connected Suppliers Endpoint and Validated Supplier Filtering in the Advanced CPQ API

What's New:

  • New Connected Suppliers Endpoint (v2 & v3): API customers can now retrieve the full list of active, connected suppliers available to their instance via GET /advanced/v3/suppliers?companyId=<instance> (and /advanced/v2/suppliers).

    • Returns the exact supplier name accepted by pricing requests.

    • Returns the supplier’s quotingMethod (such as External API, Internal API, Internal API - Market Data Insights, Internal API - Supplier Carrier Data).

    • Returns supported productCategories for each supplier.

    • Automatically filters out inactive, manual, suspended, or blacklisted suppliers, returning one unique, alphabetically sorted entry per eligible supplier.

  • Strict Validation for providerInclude and providerExclude:

    • Case-Insensitive & Whitespace Matching: Supplier names sent in providerInclude or providerExclude are now matched case-insensitively and ignore leading/trailing whitespace, normalizing automatically to the system spelling.

    • No Silent Widening (HTTP 400 on Unmatched Names): If a request includes an invalid, misspelled, or disconnected supplier name, the API immediately returns an HTTP 400 Bad Request identifying the unrecognized supplier name(s). The request is rejected before any quote, location, or pricing request is created instead of silently widening the request without warning.

Benefits:

  • Prevents Unintended Pricing Requests: Previously, an unmatched or misspelled supplier name was silently dropped, causing pricing requests to unintentionally route to all connected suppliers. The API now returns an error if supplier name is not found rather than silently widening the request to ignore the include/exclude directive.

  • Removes Guesswork: Integrators no longer need to guess the exact naming convention or character casing required for supplier inclusion or exclusion.

  • Fail-Fast Error Handling: Clear error messages highlight invalid supplier names immediately so issues can be corrected before quotes are generated.

User Action Required:

  • Retrieve Suppliers: Call GET /advanced/v3/suppliers?companyId=<instance> (passing standard authentication and user headers) to discover all active connected suppliers and their supported product categories.

  • Filter Quotes in Create Pricing: Pass the returned supplier strings in the providerInclude or providerExclude arrays on POST /pricing.

  • Review Integrations: Ensure supplier names sent in existing pricing calls match valid connected suppliers to avoid HTTP 400 errors.

Who Is It For:

API customers, buyers, and technical integration partners using Advanced CPQ API v2 or v3 to automate quoting.

Additional Notes:

  • When both providerInclude and providerExclude are omitted or left empty, quotes continue to route using standard default pricing rules across all eligible suppliers.

  • Direct Import and Instance Data rows without an underlying seller connection are not listed, as they cannot be targeted for remote include/exclude pricing.

2.1 New KALAAM TELECOM API: instant pricing in the Middle East and Pakistan

What's New: A new KALAAM TELECOM Seller Cloud API returns KALAAM TELECOM prices directly in your quotes, with no manual quote request. It covers Dedicated Internet, Ethernet, MPLS VPN and international private line services in Bahrain, Egypt, Jordan, Kuwait, Lebanon, Oman, Pakistan, Qatar, Saudi Arabia and the United Arab Emirates. To use it, you need a connection to KALAAM TELECOM. For Ethernet - Switched quotes, you also need NNIs set up (see User Action Required).

Supported products, countries and speeds:

KALAAM TELECOM service

Product category / access media

Countries

Speeds (Mbps)

Direct Internet Access (DIA)

Dedicated Internet / Fiber, Copper

Bahrain, Egypt, Jordan, Kuwait, Oman, Pakistan, Qatar, Saudi Arabia, United Arab Emirates

1 to 20 (each whole number), 25, 30, 40, 50, 60, 70, 75, 80, 90, 100

Ethernet Private Line (Layer 2 MPLS)

Ethernet - Switched / Fiber, Copper

Bahrain, Egypt, Jordan, Kuwait, Lebanon, Oman, Pakistan, Qatar, Saudi Arabia, United Arab Emirates

1, 2, 4, 5, 6, 8, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 75, 80, 90, 100

Global VPN (Layer 3 MPLS)

MPLS / Fiber, Copper

Bahrain, Egypt, Jordan, Kuwait, Oman, Pakistan, Qatar, Saudi Arabia, United Arab Emirates

1, 2, 4, 10, 15, 20, 30, 40, 50, 100

International Private Leased Circuit (IPLC)

Ethernet - Dedicated / Fiber, Copper

Bahrain, Kuwait, Oman, Qatar

1, 2, 4, 10, 15, 20, 40, 50, 100

Supported terms: 12, 24 and 36 months.

Benefits: You can get KALAAM TELECOM prices straight away across the Middle East and Pakistan. Coverage varies by product; see the table.

User Action Required:

  • Connection: You need a connection to KALAAM TELECOM, set up with your own KALAAM TELECOM credentials. Contact Connectbase Support to set it up.

  • Ethernet - Switched: You need NNIs (Network-to-Network Interfaces, the points where KALAAM TELECOM's network hands over to yours) before you can quote this product. KALAAM TELECOM provides the NNI details by email on request. They are then added in TCW under Product Catalog > NNI Locations and NNI Geography Rules, with supplier KALAAM TELECOM. Ethernet - Switched quotes fail until this is done.

  • Dedicated Internet, MPLS and Ethernet - Dedicated quotes do not need NNIs.

Who Is It For: Buyers who need connectivity in the Middle East and Pakistan, especially those who already work with KALAAM TELECOM.

Additional Notes: Results show KALAAM TELECOM as the supplier.

2.2 New Netia API: instant Ethernet and Dedicated Internet pricing in Poland

What's New: A new Netia Seller Cloud API returns Netia prices directly in your quotes for Ethernet and Dedicated Internet in Poland, with no manual quote request. For each address, it checks whether Netia can connect the site and returns a price for the speed and term you request. To use it, you need a connection to Netia (see User Action Required).

Supported products and speeds:

Product category

Access media

Speeds (Mbps)

Ethernet - Switched

Fiber, Copper, Wireless - Fixed

2, 4, 6, 8, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000

Dedicated Internet

Fiber, Copper, Wireless - Fixed

Same speeds as Ethernet - Switched

Supported terms: 12, 24 and 36 months. Prices for 48 and 60 months are returned only where Netia has enabled those terms for your account.

Benefits: You can get Netia prices in Poland straight away.

User Action Required:

  • Agreement with Netia: Netia requires you to have an agreement with them before you connect.

  • Connection: Once you have an agreement, contact Connectbase Support to set up the connection with your Netia credentials. Netia also needs to approve the connection from Connectbase.

  • NNIs: None are needed.

Who Is It For: Buyers who need Ethernet or Dedicated Internet in Poland.

Additional Notes:

  • Same price for both products: Netia prices a location once, whichever product you request. For the same address, speed and term, Ethernet - Switched and Dedicated Internet return the same monthly and installation price and the same on-net status.

  • Budgetary prices: Netia's prices are budgetary quotes.

  • Daily limit: By default, Netia accepts 100 price requests per buyer per day. Each combination of location, speed and term counts as one request: for example, 10 locations at 5 speeds and 2 terms uses all 100. Netia can raise the limit by agreement.

  • Address accuracy: Results depend on accurate Polish city names and postcodes.

2.3 Verizon Quote: more Verizon details returned in API Info

What's New: Verizon Quote prices now carry more of the details Verizon returns. The details are added to the price's API Info, which appears in two places:

  • the API Info column for each price in CPQ;

  • the apiInfo field of the Advanced CPQ API (v3) Get Prices response.

The new values appear as "Label = value", with the value passed through from Verizon, and values are separated by semicolons. The new values are:

  • All products: Colo Restrict, Location Detail.

  • Ethernet - Switched: UNI Performance and EVC Performance, shown when the price request sent to Verizon included them. UNI Speed was already shown.

  • EVPL and Internet Dedicated+: Operation Performance, Application Performance.

  • EVPL only: Service Type, Carrier Diversity.

Until now, when Verizon returned a quote but left one of these values empty, the value was simply missing from API Info. It now shows as "Not provided", so you can tell that Verizon didn't supply it. This applies to the new values above, and to Access Type, Access Provider, Lit Capability and Optical Extension where those apply to the product. Values that Connectbase sends to Verizon (UNI Speed, UNI Performance, EVC Performance) and LATA are still left out when empty.

User Action Required: Use the values to compare Verizon options, or as conditions in CPQ rules that check API Info.

User Action Required: None. If you have CPQ rules or integrations that read API Info text, check them: some values that used to be missing now appear as "Not provided".

Who Is It For: Buyers connected to Verizon Quote.

Additional Notes: A connection to Verizon Quote is required.

2.4 Bell Canada WSS - DIA is now available for quoting

What's New: We have enhanced our Bell Canada WSS API integration with the capability of quoting DIA.

User Action Required: No user action required. This can be done by requesting Dedicated Internet over Fiber for the following:

  • Speeds: 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, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000

  • Contract Terms: 12, 36, 60

Who Is It For: All buyers connected to Bell Canada WSS for quoting.

Additional Notes: A connection to Bell Canada WSS is required for this.

2.5 Frontier ESB: WABB service withdrawn state by state from December 2026

What's New: Verizon/Frontier is withdrawing Wholesale Advantage Broadband (WABB), including WABB Static Internet, state by state. WABB is quoted through the Frontier ESB API integration. From each date below, Frontier ESB is no longer asked to quote in the listed states. For new quotes, those locations come back as not serviceable, and Frontier ESB's status in the quote shows a message naming the withdrawn states and date. On December 4, 2026, for example, the message is: "WABB services have been withdrawn from AL, NC, NM, and SC as of Dec 4, 2026."

  • From 00:01 Eastern Time (ET) on December 4, 2026: service ends in NC, SC, AL and NM.

  • From 00:01 ET on January 29, 2027: service also ends in CT, GA, MI, MS, NY, OH, PA, TN and WV.

  • From 00:01 ET on February 26, 2027: service also ends in FL, IL, IN, IA, MN, NE, TX and WI.

  • From 00:01 ET on April 2, 2027: Frontier retires the Frontier ESB API itself. Frontier ESB is then no longer asked to quote anywhere, including AZ, CA, NV and UT, From then on, no Frontier ESB prices are returned in any state, and its status in the quote shows "Frontier ESB is being decommissioned."

User Action Required: None. Quotes in withdrawn states come back as not serviceable automatically.

Who Is It For: All buyers connected to Frontier ESB for quoting.

2.6 Colt eBonding: more Colt prices for IP Access and Ethernet Hub and Spoke, with optional third-party access

What Changed: This applies to buyers who quote Colt IP Access or Colt Ethernet Hub and Spoke through a Colt eBonding API connection in TCW. They should now get a Colt price at more sites, with no action needed. They can also ask to see Colt prices over third-party access. Customers with legacy Colt connections through the Global Platform are not affected, and their configurations are unchanged.

  • Better choice of Colt fibre: For each site, Colt lists the network connection points it could use. Colt eBonding now picks the first point Colt marks as available, in this order: on-net, FTTx, near-net, then off-net. FTTx points are skipped if the connection is set up to return third-party options as well. Until now it could pick a point Colt was not able to price, and so return no price.

  • Partial failures: If one access option at a site fails, prices from the other options at that site are still returned. Until now they were lost.

New options: Connectbase can now set up your Colt eBonding connection to:

  • return Colt prices over third-party (leased line) access as well as Colt's own fibre, with several third-party options for each site;

  • use third-party access only where Colt fibre isn't available;

  • give priority to your preferred third-party access suppliers when there are more options than can be priced.

Benefits: More sites return a Colt price, and you can see Colt's third-party access options alongside Colt fibre.

User Action Required:

  • Improved Colt fibre results: No action needed.

  • Third-party (leased line) prices: Raise a request with Connectbase Support. Say whether you want third-party prices as well as Colt fibre, or only where Colt fibre isn't available, and list any preferred third-party suppliers. Connectbase then updates your Colt eBonding connection. Third-party pricing makes Colt quotes noticeably slower; see Additional notes.

Who Is It For: Buyers with a Colt eBonding API connection in TCW who quote Colt IP Access or Colt Ethernet Hub and Spoke.

Additional Notes:

  • Third-party access is slower: Colt has to collect prices from third-party suppliers, so quotes take noticeably longer than Colt fibre only. In one test with Colt fibre and third-party options together, a call went from under a second to over 30 seconds. If you use third-party access only where Colt fibre isn't available, only those sites are affected. Very slow Colt responses can time out without a price.

  • With third-party access turned on, up to 10 network points (Colt fibre plus third-party options) are priced for each site.

  • Point-to-point Ethernet Line products are unchanged.

2.7 Optimum - New Coax Broadband speeds enabled

What's New: We have enhanced our Optimum - EasyQuote API integration to support quoting for more Broadband speeds over Coax/HFC.

User Action Required: No user action required. This can be done by requesting Broadband over Coax/HFC for the following:

  • Speeds: 300/50, 500/50, 1000/50, 1000/100

  • Contract Terms: 12, 24, 36, 60

Who Is It For: All buyers connected to Optimum - EasyQuote for quoting.

Additional Notes: A connection to Optimum - EasyQuote is required for this.

2.8 Beyond Reach - New Ethernet & Broadband speeds enabled

What's New: We have enhanced our Beyond Reach API integration to support quoting for new speeds under Ethernet (10M, 20M) and Broadband (300/30).

User Action Required: These speeds can be requested by the following service requirements:

  • Ethernet - Switched, Wireless - Fixed, 10M & 20M, 12/24/36/60-Month

  • Broadband, Wireless - Fixed, Download: 300, Upload: 30, 12/24/36/60-Month

Who Is It For: All buyers connected to Beyond Reach for quoting.

Additional Notes: A connection to Beyond Reach is required for this. The 300/30 Broadband rate is available only at some locations.

2.9 Ielo Eligibility moves to the Unified API Platform and adds Ethernet, Broadband and burstable services in France

What Changed: The Ielo Eligibility API integration for France now runs on Connectbase's Unified API Platform (UAP). Until now it quoted only Dedicated Internet over fiber. It now also quotes Ethernet, Broadband and burstable services, and adds lower speeds. Existing connections will be moved for you, so you don't need to do anything.

Additional products and speeds:

Ielo service

Product category / access medium

Speeds (Mbps)

Availability

FTTO (fiber to the office)

Dedicated Internet / Fiber

2, 4, 5, 10, 20, 30, 40, 50, 60, 80, 100, 200, 300, 500, 1000, 2000, 4000, 10000

Available before; 2 and 4 Mbps are new

FTTO

Ethernet - Switched / Fiber

Same speeds as FTTO above

New

FTTO Burst (can use more bandwidth than the committed speed)

Dedicated Internet / Fiber

Same speeds as FTTO above

New as a separately labelled product

FTTO Burst

Ethernet - Switched / Fiber

Same speeds as FTTO above

New

FTTH (fiber to the home)

Broadband / Fiber

300/250, 1000/250, 1000/500 (download/upload)

New

Supported terms: 12, 24, 36 and 60 months.

Benefits:

  • You can quote more Ielo services in France through one connection.

  • Each price now shows whether it is delivered over Ielo's own network (on-net) or over a partner operator's network (off-net). The operator's name is shown with each price, as before.

User Action Required:

  • Existing connections: No action is required. Connectbase will move existing Ielo Eligibility connections to the UAP version as an internal task. The additional products are available once your connection has moved.

  • New connections: All new connections are made to the UAP version, which is listed as Ielo Liazo Eligibility when you set up a connection.

  • To move sooner: Raise a request with Connectbase Support.

Who Is It For: Buyers quoting in France who are connected to Ielo Eligibility, or who want to connect to it.

Additional Notes: A connection to Ielo Eligibility is required. The earlier version of this integration is deprecated, and all new connections are made to Ielo Liazo Eligibility.

3.1 Set Point-to-Point (P2P) or Single Location as the Default Quoting View

What's New:

  • Admins can now configure the default view presented to users when starting a quote:

    • Added a new setting, CPQ Address Import Default View, under Admin → Company Default Settings → Default Attributes.

    • Two options are available: Single Location (default) and P2P Mode.

  • When P2P Mode is selected, all quoting screens (including Quick Quote and the deal location import/entry screens) default to the P2P view for all users in that instance, including external users in the Business Partner Portal (BPP).

Benefits:

  • Saves time and clicks: Teams and partners who primarily or quote point-to-point services no longer have to manually toggle to P2P mode on every quote.

  • Guides partners: Business Partner owners can ensure their external partners immediately land in the correct P2P quoting flow.

User Action Required:

  • Go to Admin → Company Default Settings → Default Attributes.

  • Find the CPQ Address Import Default View dropdown.

  • Select P2P Mode (or Single Location) and save.

  • The selected view will automatically display as the default for all users in your instance the next time they quote.

Who Is It For:

Admins, CPQ users, quote desk teams, and Business Partner Portal owners/partners—especially those primarily quoting point-to-point services.

Additional Notes:

  • No change for existing workflows: All instances default to Single Location until an admin explicitly changes the setting.

  • Users can still manually toggle between Single Location and P2P Mode within the quoting screen whenever they need to quote a different service type.

3.2 Enhanced NNI Geography Rules with Same-Geography Controls and Rule Export

What's New:

  • Clarified NNI Assignment Logic: In Rules → Geography → NNI Geography Rules, the rule creation and edit workflows have been streamlined to clearly separate fixed assignment from dynamic distance calculation:

    • Users can now define either a Specific NNI or toggle Selected by Distance, but not both.

    • When multiple rules with specific NNIs match a quoted location, the platform automatically selects the nearest specific NNI to the quoted site by default.

  • New "Same Geography" Distance Constraint: When Selected by Distance is enabled, admins can now configure "NNI Location must be in same geography":

    • Yes: Restricts distance matching strictly to NNIs located within the defined rule geography (preventing cross-border NNI selection when quoting within a specific country or region).

    • No: Considers all supplier NNIs by proximity, allowing cross-border assignments if the closest NNI is in a neighboring geography.

    • If multiple overlapping rules apply with differing geography constraints, the rule with the highest priority is honored.

  • Rule Import & Export:

    • Added full Export capability to download existing NNI Geography Rules into a spreadsheet matching all active rule attributes.

    • Updated the Import template to include the new "NNI Location must be in same geography" field (values: Yes/No).

Benefits:

  • Eliminates Unintended Cross-Border Assignments: Ensures quoting respects local regulatory, commercial, or operational preferences where quotes must terminate at an in-country NNI.

  • Intuitive Rule Configuration: Removes ambiguity between distance toggles and specific NNI assignments, ensuring pricing rules behave predictably.

  • Easier Rule Auditing & Maintenance: Teams can now export their complete NNI rule sets for bulk verification, offline updates, and seamless re-importing.

User Action Required:

  • Navigate to Rules → Geography → NNI Geography Rules.

  • When adding or editing a rule:

    • Choose a Specific NNI if a fixed location is required, OR

    • Turn on Selected by Distance and set "NNI Location must be in same geography" to Yes (to keep the NNI within the defined boundary) or No (to allow cross-border distance selection).

  • To manage rules in bulk, use the new Export button to review your configuration or download the latest template before re-importing.

Who Is It For:

Administrators, product catalog managers, and pricing desk teams managing NNI rules and quoting behavior.

Additional Notes:

  • Existing quoting behavior remains unchanged until rules are updated or new same-geography constraints are applied.

3.3 Maintain Supplier Capability Matrix in Product Catalog for Buyers and Sellers

What's New:

  • Product Catalog Management for Capability Matrix: Buyers and sellers can now directly create, manage, and audit Supplier Capability Matrices within the Product Catalog UI.

    • Buyer-Managed Matrix (Supplier Pricing): Available under Product Catalog → Supplier Pricing. Buyers can define baseline capability rules for their suppliers (supporting connected suppliers and carrier API suppliers).

    • Seller-Managed Matrices (Company Pricing): Available under Product Catalog → Company Pricing as "Your Capabilities." Sellers can define capability baselines for their own products, speeds, and media types without specifying a supplier name.

  • Automated CPQ Step 3 & Advanced CPQ v3 Field Mapping: Matches capability rules by Country, Supplier, Product Category, Product Name, Building Connection Status, Speed, and Media Type to automatically populate missing quote details:

    • Mapped Fields: Hub Type (hub_type), Interface Type (interface_type), Connector (connector), Install Interval (install_interval), MTTR (mttr), SLA (sla), Quote Validity Days (quote_validity_days), and Notes (notes).

  • Standardized Precedence & Fallback Logic:

    • Fields are populated during CPQ post-processing only when automated pricing results do not return them.

    • Supplier-provided values (via seller capability matrix, company rate card, or carrier API mappings) always take primary precedence.

    • If the supplier does not provide these values, the buyer-defined capability matrix values automatically backfill the missing information.

  • Bulk Import & Export: Full CSV import and export capabilities for rapid onboarding and updates. Imports use strict atomic validation (saves all valid rows or none) and clearly identify any invalid rows and validation errors.

Benefits:

  • Eliminates Quote Data Gaps: Ensures quotes consistently include crucial operational and technical details (SLAs, MTTR, install intervals, interface, connector) even when suppliers do not provide them in their automated rate cards or API feeds.

  • Saves Sellers Time: Sellers can define standard delivery, SLA, and interface specifications once across their product portfolio and have them automatically flow into all outbound quotes.

  • Gives Buyers Control: Buyers can set operational standards for specific suppliers or carrier partners to streamline quote evaluation and downstream ordering.

  • Reliable Data Maintenance: Direct CSV import/export and audit history make ongoing maintenance seamless for catalog administrators.

User Action Required:

  • For Buyers: Navigate to Product Catalog → Supplier Pricing → Supplier Capability Matrix to view, add, export, or import rules for your suppliers.

  • For Sellers: Navigate to Product Catalog → Company Pricing → Supplier Capability Matrix to configure capability baselines for your own products.

  • Specify your matching parameters (Country, Product Category, Product Name, Building Connection Status, Speed, Media Type) and enter the default values to apply for SLA, MTTR, Install Interval, Interface Type, Connector, Quote Validity Days, and Notes.

Who Is It For:

Administrators, product catalog managers, pricing desks, and buyers/sellers configuring standard product quoting parameters in Connected World and the Advanced CPQ API.

Additional Notes:

  • Capability matrix mapping never overwrites values actively returned by a supplier or carrier API; it operates strictly as a fallback to complete missing fields.

3.4 Add Product Name as an Available Condition in CPQ Rules

What's New:

  • Product Name Condition in CPQ Rules: When adding or editing rules in Rules → CPQ Rules, Product Name is now available as a selectable data type/condition.

  • Connected Buyer Rate Card Options: The dropdown populates with valid product names from connected buyers' rate cards.

  • Rule Execution: When a quote result meets the defined Product Name condition, the rule applies as configured (such as filtering or suppressing matching solutions).

Benefits:

  • Targeted Solution Filtering: Quoting teams can suppress or filter specific supplier solutions directly by product name (e.g., removing specific broadband tiers or dynamic solutions from quote results).

  • Eliminates Manual Quote Cleanup: Removes the need to manually review and remove unwanted products from quote proposals.

User Action Required:

  • Go to Rules → CPQ Rules and select Add New or Edit.

  • Select Product Name under condition data types, choose the target product name, and set the rule action.

Who Is It For:

CPQ administrators, pricing desk teams, and quoting users across all customer accounts.

Additional Notes:

  • None

3.5 Business Partner Portal Admin and Sub-Agency User Management

What's New:

  • Centralized Business Partner Portal Administration: Administrators now have a dedicated Business Partner Portal configuration section in Admin (under Company Details / Company Settings):

    • Portal Details & URL: Displays your company’s Business Partner Portal (BPP) URL and core portal settings in one centralized view.

    • Terms & Conditions: Portal terms and conditions configuration has been relocated from Company Default Attributes to this page for streamlined management.

    • Dedicated Business Partner User Roster: A dedicated Users tab provides a filtered view of all users assigned the Business Partner role.

  • TSD & Sub-Agency Configuration:

    • Admins can configure whether their Business Partner Portal is leveraged for Technology Solutions Distributors (TSDs) and Sub-Agents.

    • When enabled, admins can define and maintain a custom list of supported sub-agencies directly within portal administration.

  • Sub-Agency User Setup & Profile Classification:

    • In Admin → User Management → Users → Add New / Edit, assigning the Business Partner role now allows selecting a partner type: TSD, Sub-Agent, or N/A (default).

    • When Sub-Agent is selected, the company dropdown dynamically populates with the list of configured sub-agencies, allowing sub-agents to be properly associated with their agency without requiring standalone corporate account setup.

    • The classification (TSD, Sub-Agent, or N/A) and associated sub-agency are saved to the user’s profile and visible in the Business Partner user list.

Benefits:

  • Accurate Partner Attribution: Sub-agents representing or working under TSDs can now be set up under their correct sub-agency identity, ensuring clear visibility and tracking.

  • Streamlined Portal Management: Brings portal URLs, terms and conditions, and partner user visibility into a single, dedicated administrative hub.

  • Flexible Partner Onboarding: Admins can quickly configure and update eligible sub-agencies as partner relationships evolve, removing user creation bottlenecks.

User Action Required:

  • Configure Portal & Sub-Agencies: Navigate to Admin → Business Partner Portal to review portal details, terms & conditions, and Business Partner users. Enable TSD & Sub-Agent support and enter your list of supported sub-agencies.

  • Provision Sub-Agent Users: In Admin → User Management → Users, create or edit a user with the Business Partner role. Select Sub-Agent, choose the appropriate sub-agency from the dropdown, and save.

Who Is It For:

Company administrators, partner relationship managers, and portal administrators managing Business Partner Portal access for TSDs, agents, and sub-agencies.

Additional Notes:

  • The Business Partner Portal admin menu is available for company instances with Business Partner Portal enabled.

  • Existing Business Partner users remain set to N/A until explicitly updated by an administrator.

  • This change lays the foundation for adding additional TSD/Sub-Agent specific features and improvements in the future.

4.1 Quote Progress: Timeout Display Error resolved

Issue and Resolution: Since early October 2026, the Supplier Progress panel in CPQ could show a supplier as Timeout even after all of that supplier's prices had arrived in the quote. The supplier hadn't actually timed out: its progress was never marked complete once its prices were delivered. Supplier Progress now shows the supplier as complete as soon as its prices arrive. Only the status display was wrong; prices were delivered as normal.

User Action Required: None. If an older quote shows a supplier as Timeout but that supplier's prices appear in the quote, you can ignore the Timeout. If a supplier shows Timeout and none of its prices appear, that supplier really did not respond in time. If you have questions, contact Connectbase Support.

Additional Notes: This affects buyers who quote in the CPQ user interface.

4.2 Clearer Progress and Controls When Using "Finish Now" in CPQ Step 3

What's New:

  • In CPQ Step 3, the Finish Now workflow has been updated with clearer visual feedback and improved button state handling:

    • New "Running post processing" status: Once backend post-processing starts, the screen displays "Running post processing" so users immediately know the system is actively working on their quote.

    • Button stays available until processing begins: The Finish Now button remains visible and enabled right up until the post-processing phase actually begins, rather than disappearing prematurely.

Benefits:

  • Removes guesswork: Users get clear, immediate visual confirmation that clicking Finish Now worked and that the quote is actively finalizing.

  • Seamless status updates: The screen transitions automatically without requiring manual page refreshes.

User Action Required:

  • No change in workflow is required.

Who Is It For:

CPQ users, sales representatives, and quote desk teams who generate and manage quotes in CPQ.

Additional Notes:

  • Standard quoting behavior is unchanged when quotes complete normally without using Finish Now, or before post-processing begins.

4.3 Renegotiate Pricing with Suppliers in Connected World Bid Manager (CBM)

What's New:

A new Renegotiate action under the Approve / Reject menu lets assigned users ask suppliers to revise pricing they've already submitted via a manual CBM process. It opens the Supplier Pricing Request form already filled in with the supplier, requirements, latest NRC/MRC, previous due date and original contact. Suppliers get an email with a link to their earlier response, with the buyer's notes shown at the top. From there they can update their pricing or select No Bid. Solutions can go through multiple negotiation rounds, and each round is saved in the Activity Log and under Solution Details → Access Pricing.

Benefits:

  • You no longer have to reject quotes or recreate requests to negotiate pricing.

  • Turnaround is faster because suppliers see their earlier answers and the buyer's guidance right away.

  • Existing pricing is kept if the supplier selects No Bid.

  • Pricing history is visible round by round, which helps with auditing.

User Action Required:

  1. On a solution with supplier pricing received, select Approve / Reject → Renegotiate.

  2. Enter a future due date, confirm the contact and add notes if needed.

  3. Submit. The solution changes to Waiting for Supplier and the supplier is notified.

Who Is It For:

Deal Desk teams, direct engagement buyers, CBM users who manage supplier pricing, and participating suppliers.

Additional Notes:

Only the assigned user can see Renegotiate, and only after supplier pricing is submitted. If you cancel before submitting, nothing changes and no notifications go out.

4.4 CPQ Request NNIs Modal Product Scope Enforcement & Speed Display

Issue:

In CPQ Step 2 under the Request NNIs modal, the NNI preview logic ignored product category constraints and NNI Geography rule product scopes. As a result, NNI Locations scoped exclusively to Ethernet products (Ethernet - Switched / Ethernet - Dedicated) were pre-filled and saveable for non-applicable products such as Broadband and Dedicated Internet (DIA). Additionally, the modal's Speed column displayed "—" on all rows instead of reflecting the configured speeds.

Resolution:

Updated the NNI preview logic and the Request NNI Locations modal to strictly enforce product scope against NNI Geography rules and NNI Location definitions. Products without applicable NNI rules or support now display "No NNI applicable" / "Not Applicable", are disabled from selection or editing, and are skipped during "Select All". In addition, the Speed column now correctly populates with configured product speeds.

Before/After:

  • Before: Opening the Request NNI Locations modal pre-filled Ethernet-scoped NNI Locations across all configured products—including Broadband and DIA—allowing invalid NNI assignments to be saved. All rows rendered "—" in the Speed column.

  • After: Only eligible products matching active NNI Geography rules receive NNI Location assignments. Unsupported products are marked "No NNI applicable" / "Not Applicable" and disabled, and configured speeds display accurately.

Additional Notes:

  • None

4.5 Export Quote Details from CPQ Step 4

What's New:

  • Export Action on Step 4: A new Export Quote Details action is now available on CPQ Step 4 after finalizing a quote.

  • Direct CSV Download: Generates and downloads a CSV containing all selected and finalized solutions, matching the columns, formatting, and row data of the Step 3 "Export Selected" export.

Benefits:

  • Eliminates Backtracking: Users can export quote data immediately upon finalizing a quote without having to navigate backward to Step 3.

  • Streamlined Workflow: Simplifies extracting raw quote data for external systems and downstream quote generation.

User Action Required:

  • On CPQ Step 4, select Export Quote Details to download the CSV of finalized solutions.

Who Is It For:

CPQ users and quoting teams who export quote data to external systems.

Release Notes TCW.2026.R22

October 30, 2026

Executive summary

This release expands supplier connectivity and brings more quoting and service change workflows into The Connected World, with clearer controls and more useful pricing information.

New coverage

  • Eurofiber: New Network Availability Seller Cloud API covering the Netherlands, Germany, Belgium and France, with Fiber options for Ethernet Dedicated, Ethernet Switched and Dedicated Internet.

Supplier API continuity: AT&T New Experience Service Qualification supports v2 credentials while existing v1 connections continue uninterrupted during the supplier transition.

More complete automated quoting: Advanced CPQ API v3 adds point-to-point quoting, mixed A-Z and single-location requests, and special pricing and construction cost details. The CBM API adds service upgrade, downgrade, shift and renewal requests with existing service context, helping The Connected World (TCW) handle more of the quoting lifecycle.

Faster evaluation and administration: Side-by-side CPQ comparisons highlight the lowest Provider MRC. NNI Location templates carry cross connect pricing for bulk maintenance, while clearer import errors help users correct files. New group controls govern Linkbase access and streamline supplier attribute prompts; email verification adds protection to off-platform supplier responses.

Consistent company access controls: Network Finder and My Locations menu items now follow company access settings. My Locations also prevents access through direct links when the feature is disabled, helping companies enforce their configured access restrictions.

Cleaner point-to-point results: New A-Z uploads retain one location pair per uploaded pair and eliminate repeated solutions caused by multiple building records, while preserving distinct matching zone and pricing tier options.

More efficient tenant synchronization and clearer downloads: Tenant API v2 adds a date-range endpoint for additions, updates and removals, allowing integrations to retrieve changed records rather than compare full datasets. Distribution email downloads use the list name and send date, making Building, Route and Pricing files easier to recognize.

New features and enhancements

1 API Enhancements
1.1 Eurofiber Network Availability [Implementation]

Eurofiber Network Availability has been implemented as an available External API integration.

Supported Countries: Netherlands, Germany, Belgium, France

  • Covered Products:

    • P2Pop Ethernet - Ethernet Dedicated

    • Ethernet to NNI - Ethernet Switched

    • DIA - Dedicated Internet

  • Access Mediums: Fiber

  • Speeds: 1G, 2G, 5G, 10G

  • Supported Terms: 12, 24, 36, 60 Months

1.2 AT&T New Experience SQ integration enabled for API v2 credentials

We have enhanced our AT&T New Experience Service Qual integration to enable v2 credentials for quoting as AT&T migrates API platforms. Connections that are currently using v1 credentials will continue uninterrupted as AT&T works to migrate all buyers to v2.

Why it matters: AT&T is no longer producing v1 credentials for this API. Buyers that have been enabled for this API since then have only been issued v2 credentials, which require an authentication method different from that of v1. This change enables this new mode of authentication and enables all buyers previously blocked with v2 credentials to have access to this API.

User Action Required: No user action is required for this.

Audience: This is for all buyers seeking to prospectively quote through the AT&T New Experience Service Qual API.

2 TCW Enhancements
2.1 Point-to-Point (P2P) Quoting Now Available in the Advanced CPQ API

What's new:

  • Buyers can now request quotes for point-to-point (A-to-Z) services directly through the Advanced CPQ API (v3).

  • Create Pricing (POST): There's a new optional field, locations[].zAddress. Adding a Z address to a location automatically marks it as a point-to-point (A-Z) location. Locations without one are still quoted as standard single locations.

  • You can mix point-to-point and single locations in the same request.

  • Get Prices (GET): The response now includes more Z-side location details: zLocationId, zAddressValid, zSecondaryDesignator, zSecondaryNumber, zUniqueKey, zGlobalLocationId, zSiteGroup and zAddressStatusId.

Benefits:

  • You can initiate point-to-point quotes via the API, that used to be limited to the UI.

  • One request can quote both point-to-point and single locations, so you send fewer calls.

  • The Z-side data now matches the A-side more closely, which makes P2P results easier to reconcile and use in your own systems.

  • Existing integrations keep working. The new request field is optional, and the response fields are additions only.

How to use it:

  • To quote point-to-point, add zAddress to each relevant location in the locations array of your Create Pricing request. It uses the same free-text format as address.

  • If you send zAddress empty or as whitespace only, the whole request is rejected with: "locations[n].zAddress cannot be empty when requesting P2P services." Leave the field out, or set it to null, for single locations.

  • Locations you submit appear on the deal in the UI as A-Z Location (point-to-point) or Simple Location (single).

  • If you want the new Z-side fields from Get Prices, update your integration to read them.

Who is it for: Buyers and integration partners who use the Advanced CPQ API (v3) to automate quoting, especially those buying point-to-point services from their sellers.

Additional notes:

  • Nothing changes for existing non-P2P requests.

  • Z-side fields that Get Prices already returned for P2P quotes are unchanged. The new fields are added alongside them.

2.2 Special Pricing and Construction Cost Details Now Included in Advanced CPQ API Price Results

What's New:

  • The Advanced CPQ API (v3) Get Prices and Get Selected Prices endpoints now return all special pricing and construction cost details for each price. Previously they returned only Supplier Contribution.

  • New special pricing fields: specialPricingProvided, specialPricingDetails, specialPricingMrc, specialPricingNrc and specialPricingExpiration.

  • New construction cost fields: customerConstructionCost, totalConstructionCost, constructionEta and constructionDetails.

  • Supplier Contribution (scContribution) is still returned as before.

Impact:

  • You get the full pricing picture through the API, including special pricing terms and construction costs, without checking the UI.

  • More complete data makes quoting, reporting, analysis and customer-facing outputs more accurate.

  • Existing integrations keep working. The fields are additions only.

User action required:

  • You don't need to change your requests. The new fields appear automatically in Get Prices and Get Selected Prices responses.

  • If you want to use special pricing or construction cost data, update your integration to read the new fields.

Who is it for: Buyers and integration partners who use the Advanced CPQ API (v3) to get quote prices and selected prices, especially those who rely on special pricing or construction cost information.

Additional notes:

  • Fields only appear when a price has a value for them. Empty fields are left out of the response.

  • specialPricingProvided is always returned: 1 when special pricing applies, 0 when it doesn't.

2.3 New User Group Setting to Restrict Access to Linkbase

What's new:

  • Admins have a new user group setting: [Linkbase] Restrict Linkbase.

  • Users in a group with this setting turned on can't see or use any part of Linkbase in TCW:

    • The Linkbase menu is hidden, including Find Partners and My Partners, restricting access to partner profiles, seller contact information, connection requests and partner details.

Benefits:

  • Admins get more control over who can see Linkbase content, including seller contact information in Find Partners profiles.

  • This covers the exceptions to the standard Linkbase access rules, for user groups that shouldn't have Linkbase access at all.

  • Users in groups without this setting keep the same access as before:

    • Find Partners: all user roles can view it.

    • Connection requests from Find Partners: Admin and Carrier Relations Admin

    • My Partners: Admin, Carrier Relations Admin and Billing Admin

How to use it:

  • Go to Admin → User Groups, then add or edit a user group.

  • Select [Linkbase] Restrict Linkbase and save the group.

  • Users in a user group with this setting will not have access to Linkbase

  • To give access back, turn the setting off or remove the user from the group.

Who is it for: Admins who manage user groups and permissions, and want to block some users or groups from Linkbase completely.

Additional notes:

  • The setting is off by default, so nothing changes until an admin turns it on.

  • If a user belongs to more than one group, being in any group with this setting is enough to restrict their access.

  • Changes can take up to about a minute to apply. Restricted users may need to refresh the page before the Linkbase menu disappears.

2.4 Upload and Download NNI Location Pricing by Product Category and Media Type

What's new:

  • The NNI Location bulk upload and download template now includes the pricing details for each NNI Location. You can now load cross connect pricing through the template instead of entering it by hand.

  • New template columns, added at the end of the file: Product Category, Media Type, Cross Connect MRC and Cross Connect NRC.

  • One row per pricing line: You no longer list several products on one row separated by semicolons. To give an NNI Location more than one Product Category and Media Type combination, repeat the row once for each combination. Each row becomes its own pricing line under that NNI Location.

  • Template layout changes:

    • Transaction Indicator is now the first column.

    • The Products column has been removed. Products are now filled in automatically from the NNI Location's pricing lines.

    • NNI Location Id stays in the template. The system assigns it, and it can't be changed.

  • Downloads match the new layout: Exported files use the same layout, with one row for each pricing line. That means you can download your NNI Locations, edit them and upload them again.

  • New Media Types column in NNI Locations: It appears next to Products. Both columns are filled in automatically from the NNI Location's pricing lines, whether those lines were uploaded or entered by hand.

  • Upload Tips & Cautions updated: The tips now reflect the new layout. They also show the current Product Category options, including Wavelengths, and the Media Type options.

Benefits:

  • You can set up NNI Locations and all their cross connect pricing in one upload instead of adding pricing by hand.

  • Bulk updates are easier, because a download can be edited and uploaded again.

  • The Products and Media Types columns always match the pricing lines, so you can see at a glance what each NNI Location supports.

  • If some rows in a file have errors, only those rows are rejected. The valid rows still load.

How to use it:

  • Download the new sample template from Product Catalog → NNI Locations. Templates in the old layout, including files with a Products column or semicolon-separated products, won't match the new format.

  • New NNI Locations (N): Leave NNI Location Id blank. Add one row for each Product Category and Media Type combination.

  • Updates (U) and deletes (D): Keep the NNI Location Id from your download. It's required for these rows and can't be changed.

  • Media Type: This field is optional. If you leave it blank, the pricing line applies to all media types.

  • Cross Connect MRC and NRC: These must be numbers, and they need a Product Category on the same row.

  • Updates replace pricing lines: When you update an NNI Location, the pricing lines in your file replace all of its existing pricing lines. Include every line you want to keep.

Audience: Sellers and suppliers who manage NNI Locations and cross connect pricing in the Product Catalog, especially those who load or update locations in bulk.

Additional notes:

  • Product Category and Media Type must match the options shown in the NNI Locations screen and in Upload Tips & Cautions. Rows with values that don't match are rejected.

  • Upload results, including the reason each rejected row failed, are sent in the upload results email.

2.5 Upgrade, Downgrade, Shift and Renewal Requests Now Available in the CBM API

What's New:

  • The CBM API now returns Upgrade, Downgrade, Shift and Renewal requests for existing services, along with the details of the service being changed.

  • GET List CBM Bid Requests:

    • engagementReason has 4 new values: Upgrade, Downgrade, Shift and Renewal.

    • requestType shows the type of request: UPGRADE_DOWNGRADE, SHIFT, RENEWAL or STANDARD.

  • GET List CBM Bid Solutions for a Request:

    • Upgrade, Downgrade and Renewal requests return the existing service details: existingCircuitRef, existingSupplier, existingMediaType, existingSpeed, existingTermEnd, existingCurrency, existingMrc, existingNrc, existingNni, existingPop, existingHubType and existingInterface. They also return nniLocation, customerNniId, supplierNniId, deliveryType

    • Shift requests return the same existing service details plus existingLocation, which is the address the service is moving from. They also return:

      • newLocationPop and newLocationNni

      • deliveryType: Parallel Build or Hot Cut

      • moveTimeFrame: During business hours or Outside business hours

Impact:

  • Requests for existing services are no longer limited to the UI. You can now pull them into your own systems through the API.

  • You get the current service details (circuit, supplier, speed, pricing, term end and NNI) together with the requested change, so you can compare the two without a separate lookup.

  • Existing integrations keep working. The changes only add new values and fields.

How to use it:

  • To handle the new request types, update your integration to read the new engagementReason and requestType values.

  • To use the existing service details, update your integration to read the new fields from the solutions response.

  • Use requestType to decide which fields to expect, because Shift requests return a different set of fields from Upgrade, Downgrade and Renewal requests.

Who is it for: Buyers and integration partners who use the CBM API to track and manage CBM requests, especially those handling upgrades, downgrades, moves and renewals of existing services.

Additional notes:

  • Standard requests work as before.

  • Some fields come back empty when no value was entered on the request.

2.6 Email Verification Added to Supplier Response Forms

What's new:

  • Suppliers without a Connectbase login receive pricing requests through an email link. When they open that link, they now have to verify their email address before they can see or answer the request.

  • Here's how it works:

    • The supplier opens the Supplier Response Form link from the pricing request email.

    • They enter their email address and get a second email with a one-time code.

    • They enter the code to open and fill in the form.

  • If the code is missing or wrong, the supplier can't get into the form.

Benefits:

  • Pricing request details are better protected. Having the link is no longer enough to open the form.

  • Buyers can be more confident that the right people are seeing and answering their requests.

  • Each sign-in is recorded, so Connectbase Support can look into access questions when needed.

How to use it:

  • Suppliers: Click the link in the pricing request email as usual. Enter your email address, check your inbox for the code and enter it to open the form.

  • Buyers: You don't need to do anything. Pricing requests are sent the same way as before.

Who is it for: Suppliers who answer bid manager (CBM) pricing requests by email without a Connectbase login, and the buyers who send them those requests.

Additional notes:

  • Suppliers with a Connectbase login keep answering requests on their Supplier Dashboard as before.

  • If the code email doesn't arrive, suppliers should check their spam or junk folder.

2.7 Option to hide the Supplier Attribute pop-up in CPQ

What's new: A new user group setting, [CPQ] Restrict Supplier Attribute Screen, stops the Supplier Attribute pop-up from appearing after users click Submit Configuration in CPQ Step 2. Instead, CPQ uses the default supplier attribute options.

Benefits: Quoting takes fewer clicks and causes less confusion.

User Action Required: Admins turn on the setting for a user group. It's off by default.

Who is it for: Admins, CPQ users and Business Partner users.

Additional notes: The pop-up still appears for suppliers whose attributes need user input.

2.8 Compare Solutions in CPQ Step 3

What's new:

  • Each location section in the CPQ Step 3 By Location view now has a Compare Solutions button.

  • Select the solutions you want and click Compare Solutions to see them side by side. The solution with the lowest Provider MRC (Cost) is highlighted.

  • If you aren't using margins (your Total MRC and NRC match Provider MRC and NRC), the Sell Price and Margin sections are hidden.

Benefits: Find the lowest-cost option for a location faster, without checking each solution one by one.

How to use it: In CPQ Step 3 (By Location view), select solutions within a location and click Compare Solutions.

Who is it for: CPQ users.

2.10 Clearer Error Details When a Location Import File Can't Be Uploaded

What's new: If a file you import into My Locations fails the upload checks, you now get a clear, easy-to-read summary of what went wrong.

  • An Import Errors window opens automatically as soon as the upload fails. You don't have to click anything to see it.

  • Errors are shown in a simple table, one row per type of error. For example, "Missing columns" is listed separately from "Unknown columns," and each row names the columns involved.

  • You can open the window again at any time by clicking the red ! icon next to the file in the Upload panel.

Benefits:

  • No more cut-off messages: Before, only part of the error appeared in the Upload panel and you couldn't click the red error icon. Now you can see the whole message.

  • Faster fixes: You can see exactly which columns are missing or not recognized, so you can fix your file and upload it again without guessing.

  • Less need for support: Clear, specific feedback helps you fix common file problems yourself.

How to use it No action is required. The new error window appears automatically.

  1. Go to My Locations, open the ⋮ (more actions) menu and select Import.

  2. Choose Simple Import, select your file and click Upload.

  3. If the file has problems, the Import Errors window opens and lists each issue.

  4. Fix the issues in your file and upload it again.

  5. To see the errors again after closing the window, click the red ! icon next to the file in the Upload panel.

Who is it for: Anyone who adds or updates buildings in My Locations by importing a spreadsheet.

3 Issues resolved in this release
3.1 Point-to-point (P2P) quotes no longer show duplicate solutions

Issue: Some P2P (A-Z) quotes showed the same solution several times, with identical supplier, product, speed, access medium, term and price. This happened when a location at either end had several building records, one for each custom pricing zone. Sellers often set locations up this way for zone-based P2P pricing. The system saved each uploaded A-Z pair once for every combination of building records at the two ends. That meant one pair could turn into dozens or hundreds of pairs.

Resolution: Each uploaded A-Z pair is now saved as one pair (2 locations) in the deal, however many building records exist at each end. When pricing a P2P pair, the system now checks every building record and pricing zone at both ends. It returns one solution for each distinct matching zone pair. Separate pricing tiers (for example, Bronze and Silver) still appear as separate solutions, so no valid prices are lost.

Before/After:

  • Before: A single A-Z pair whose ends had 4 building records each became 16 pairs (32 locations). The quote showed the same solution 16 times. In a larger example, 7 uploaded pairs became 292 pairs (584 locations).

  • After: The same single pair stays 1 pair (2 locations) and returns 1 solution. The 7-pair upload creates 14 locations in a single quote master, with one solution per distinct matching zone pair.

Additional Notes:

  • Pairs where each end has only one building record are unchanged: same prices, zones and number of solutions.

  • If a pair's zones match more than one pricing tier, each tier still comes back as its own solution. This is expected.

  • Existing deals won't be migrated. Deals created before this fix keep their current locations, and re-quoting them works as it did before.

  • A pair with no matching zone pair still gets the standard "prices not found" result.

3.2 Distribution email downloads were named with an internal ID instead of the list name

Issue: When a recipient opened the download link in a distribution email, the file was saved under the platform's internal storage key — for example 21708_20250515064214.xlsx — instead of a readable name. This affected Building Lists, Route Lists and Pricing Lists in every export format. Recipients of recurring distributions could not tell which list or which send date a file belonged to without opening it, and had to rename each file by hand. The file contents were always correct; only the name was wrong. The readable name had been sent until May 2023, when a change to streaming for large exports stopped it being passed to the browser.

Resolution: Distribution downloads are now named after the list and the send date, in the format <List Name> - yyyyMMdd — for example ASTOUND OnNet-NearNet Fiber - 20250515.xlsx. This applies to Building, Route and Pricing list distributions, scheduled and “Send now” alike, and to every format (xlsx, csv, GeoJSON, GeoPackage, Shapefile and multi-file zip), each keeping its correct extension. Where a list name contains characters that filenames do not allow, only those characters are replaced with a hyphen; spaces and ordinary punctuation are kept. File contents are unchanged.

Before/After:

  • Before: 7872_20261020062600.xlsx

  • After: List5068 - 20261020.xlsx

Additional Notes:

No action is needed from customers. Download links sent before this release also pick up the new name, so existing distribution emails keep working and name their files correctly. Requested by Astound Wholesale under CSD-8758. Export and import-error downloads (for example My Buildings exports and invalid_records.xlsx) are a separate path and are not changed by this release.

3.3 Network Finder and My Locations menu items now follow your company's access settings

Issue: For some companies, Network Finder and My Locations still appeared in the left-hand menu after access to them had been turned off. The setting was saved correctly, but the menu didn't apply it. Users could see features their company had chosen not to offer.

Resolution: The menu now checks your company's access settings before it shows these items:

  • If Network Finder access is turned off for your company, the Network Finder menu item is hidden.

  • If My Locations access is turned off for your company, the My Locations menu item is hidden. Anyone who opens the My Locations page from a direct link or bookmark is sent to Connected World instead.

  • If a company has no setting configured, both items stay visible, so no one loses access they currently have.

Before/After:

  • Before: Network Finder and My Locations showed in the menu for every user, even when the company had turned access off. My Locations could also be opened from a direct URL.

  • After: Each item shows only when it's turned on for your company.

Additional Notes:

If your company had My Locations or Network Finder access turned off before, those items will no longer appear after this release. If your users need either feature, contact your Connectbase account team to review your company's settings.

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
  1. Optus Networks - New Seller Cloud API Implementation

    Optus API has been implemented as an available External API integration with the following details.

    • Supported Countries: Australia

    • Supported Access Mediums and Speeds per Product: Following products, access mediums and speeds are supported:

      • Evolve Ethernet Optus P2A - Ethernet Switched on Fiber with 10Mbps, 20Mbps, 30Mbps, 40Mbps, 50Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps, 150Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 1000 Mbps

      • Evolve Ethernet EoNBN TC2 P2A - Ethernet Switched on Copper with 5Mbps, 10Mbps, 20Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps

      • Evolve Ethernet EoNBN Extended Ethernet P2A - Ethernet Switched on Fiber with 20Mbps, 50Mbps, 100Mbps, 250Mbps, 500Mbps, 1000Mbps

      • Evolve Ethernet EoTWEA Fibre P2A - Ethernet Switched on Fiber with 10Mbps, 20Mbps, 30Mbps, 40Mbps, 50Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps, 150Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 1000Mbps

      • Evolve Ethernet EoLL Fibre P2A - Ethernet Switched on Fiber with 10Mbps, 20Mbps, 30Mbps, 40Mbps, 50Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps, 150Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 1000Mbps

      • Evolve Ethernet Optus P2P - Ethernet Dedicated on Fiber with 10Mbps, 20Mbps, 30Mbps, 40Mbps, 50Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps, 150Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 1000 Mbps

      • Evolve Ethernet EoNBN TC2 P2P - Ethernet Dedicated on Copper with 5Mbps, 10Mbps, 20Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps

      • Evolve Ethernet EoNBN Extended Ethernet P2P - Ethernet Dedicated on Fiber with 20Mbps, 50Mbps, 100Mbps, 250Mbps, 500Mbps, 1000Mbps

      • Evolve Ethernet EoTWEA Fibre P2P - Ethernet Dedicated on Fiber with 10Mbps, 20Mbps, 30Mbps, 40Mbps, 50Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps, 150Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 1000Mbps

      • Evolve Ethernet EoLL Fibre P2P - Ethernet Dedicated on Fiber with 10Mbps, 20Mbps, 30Mbps, 40Mbps, 50Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps, 150Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 1000Mbps

      • Evolve Internet Optus - Dedicated Internet on Fiber with 10Mbps, 20Mbps, 30Mbps, 40Mbps, 50Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps, 150Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 1000 Mbps

      • Evolve Internet EoNBN TC2 - Dedicated Internet on Copper with 5Mbps, 10Mbps, 20Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps

      • Evolve Internet EoTWEA Fibre - Dedicated Internet on Fiber with 10Mbps, 20Mbps, 30Mbps, 40Mbps, 50Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps, 150Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 1000Mbps

      • Evolve Internet EoLL Fibre - Dedicated Internet on Fiber with 10Mbps, 20Mbps, 30Mbps, 40Mbps, 50Mbps, 60Mbps, 70Mbps, 80Mbps, 90Mbps, 100Mbps, 150Mbps, 200Mbps, 300Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 1000Mbps

      • Evolve Internet EoNBN TC4 - Broadband on Fiber with 50/20Mbps, 100/40Mbps, 250/100Mbps, 500/200Mbps, 1000/400Mbps

      • WaveLink - Wavelengths on Fiber with 10Gb

    • Supported Terms: 12, 24, 36 Months

  2. EnTelegent - New Seller Cloud API Implementation

    EnTelegent API has been implemented as an available External API integration with the following details.

    • Supported Countries: United States of America

    • Supported Products: Broadband (Fiber, Coax, Copper, Wireless): Any speed

    • Supported Terms: 12, 24, 36 Months

  3. Shaw NDA - New Seller Cloud API Implementation

    Shaw NDA API has been implemented as an available External API integration with the following details.

    • Supported Countries: Canada, United States of America

    • Supported Products:

      • E-Access EPL (Ethernet - Switched | Fiber): 2, 5, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 2000, 3000, 4000, 5000, 10000

      • EVPL (Ethernet - Switched | Fiber): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 10000

      • Ethernet over DOCSIS (Ethernet - Switched | Coax/HFC): 2, 5, 10, 15, 20, 30, 50, 100

      • E-Line (Ethernet - Dedicated | Fiber): 2, 5, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 2000, 3000, 4000, 5000, 10000

      • Fiber Gateway - DIA (Dedicated Internet | Fiber): 5, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000

      • Wholesale Business Internet (Dedicated Internet | Coax/HFC): 75, 300, 750, 1000, 1500

    • Supported Terms: 12, 24, 36, 48, 60 Months

  4. Uniti CQS - New Seller Cloud API Implementation

    Uniti CQS has been implemented as an available External API integration with the following details.

    • Supported Countries: United States of America

    • Supported Products:

      • DIA Prem (Dedicated Internet | Fiber): 3, 5, 10, 20, 30, 50, 100, 200, 250, 300, 500, 1000

      • E-Access EPL (Ethernet - Switched | Fiber): 3, 5, 10, 20, 30, 50, 100, 200, 250, 300, 500, 1000, 2000

      • E-Access EVPL (Ethernet - Switched | Fiber): 3, 5, 10, 20, 30, 50, 100, 200, 250, 300, 500, 1000, 2000

    • Supported Terms: 12, 24, 36, 60 Months

  5. Covage - New Seller Cloud API Implementation

    Covage API has been implemented as an available External API integration with the following details.

    • Supported Countries: France

    • Supported Products:

      • BPEA - Ethernet Switched

      • BPE - Ethernet Switched

      • DIA - Internet Dedicated

    • Supported Speeds:

      • Mbps: 10, 20, 50, 100, 200, 500

      • Gbps: 1, 2, 10

    • Supported Access Medium:

      • Fiber

    • Supported Terms: 12, 24, 36 Months

  6. Vodafone/Ziggo - Colt Testing - Price mismatch and others

    We have enhanced our Vodafone/Ziggo implementation with the following:

    • Split of existing product Wholesale Ethernet Access (Ethernet - Switched | Fiber) into two distinct product results: Wholesale Ethernet Access Premium & Wholesale Ethernet Access Lite

    • Split of existing product Direct Internet Access (Dedicated Internet | Fiber) into two distinct product results: Direct Internet Access Premium & Direct Internet Access Lite

    • Inclusion of returned access information in API Info

    • Bug fix resolving prices returning for incorrect terms

    • Improved accuracy of Building Connection Status & Network Connection Status information

  7. Cegecom - New Products/Changes

    We have enhanced our Cegecom implementation with the following catalog changes improvements:

    • New products

      • Connect Ethernet (Ethernet - Switched | Fiber): 10, 20, 50, 100, 200, 300, 500, 1000

        • NNI required

      • Online Corporate (Dedicated Internet | Fiber): 10, 20, 30, 50, 100, 200, 300, 500, 1000

    • Replacement of existing Online Business (Broadband | Fiber) speeds with 100/50, 500/250, 1000/500

  8. Cammington - Enable for Fiber

    We are updating our Cammington integration with a new fiber product catalog:

    • MFN DIA (Dedicated Internet | Fiber | 12/24-Month): 20, 50, 100, 200, 300, 500, 1000

    • MFN BB (Broadband | Fiber | 12/24-Month): 20/20, 50/50, 100/100, 200/200, 300/300, 500/500, 1000/1000

    • Frogfoot BB - MTB (Broadband | Fiber | 12-Month): 20/10, 40/20, 80/40, 150/75, 500/250, 1000/500

    • Frogfoot BB - STB (Broadband | Fiber | 12-Month): 20/10, 40/20, 80/40, 150/75, 500/250, 1000/500

    • Frogfoot BB - Preferred (Broadband | Fiber | 12-Month): 20/10, 40/20, 80/40, 150/75, 500/250, 1000/500

    Note: Existing connections to this API will require updates to their ratecard.

  9. Lumen Quoting - Differentiate A/Z-ends for "Level 3 Provided Access"

    We are updating our legacy Lumen Quoting integration to expose both the A- and Z-end Access Service values returned for Wave quote results. These will return as “A Access Service” and “Z Access Service”, respectively.

TCW Enhancements
  1. Allowed the comparison of existing fields as a rule attribute in CPQ Rules

    CPQ Rules can now compare one field against another field, not just against a fixed value. Before, the Use Field Value option only listed flex fields and custom fields. Now it lists all CPQ fields that match the selected data type:

    What's new:

    • Text fields are compared with other text fields, such as Supplier vs. Last Mile Provider.

    • Number fields are compared with other number fields, such as MRC or NRC.

    • Date fields are compared with other date fields, such as Quote Expiration Date.

    In Actions, you can now set a standard or custom field to another field's value when the rule runs.

    Why it matters:

    You can write more flexible, data-driven rules without typing in fixed values. For example, you can flag line items where Supplier doesn't equal Last Mile Provider. Empty fields are handled without errors.

  2. CBM Supplier Response Portal- Improve CBM Import Template/UI Consistency and Evaluate Conditional State Validation

    What's new:

    • Mandatory columns are marked: In the sample XLSX import file, every required column header is now marked so suppliers can see what they must fill in.

    • Import tips match the UI: In the import tips table, pricing fields now appear in the same order as the UI and export.

    • State is optional: State is no longer marked as required in the template or the UI. Imports work with or without a State value.

    • Missing required fields don't block imports: If a required field is blank, the file still imports. The portal points out the missing fields so suppliers can fill them in before submitting.

    Why it matters:

    The template, import tips and UI now use the same field order. Suppliers can fill in import files faster and make fewer mistakes, and they don't get validation errors for State where it isn't needed.

  3. Seller CBM Respond Contacts to Auto Populate Buyer My Partners Contacts

    What's new:

    • Supplier Identified CBM Responders show up automatically: Suppliers can set up users to respond to CBM pricing requests. Those users now appear in the buyer's My Partners → Contacts tab for that supplier. They're marked as CBM responders with a shield icon, and CBM Contact is turned on. The list always matches the supplier's current setup. If the supplier adds or removes a responder, the buyer's list changes to match.

    • Set a responder as the default: Buyers can't edit or delete responder contacts, but they can make one their Default Contact. The default contact is then filled in automatically in step 2 of the Supplier Pricing Request.

    • Buyer contacts are unchanged: Buyers can still add, edit and delete their own contacts.

    Why it matters:

    Buyers can pick the right supplier contacts during CBM, so pricing requests go straight to the supplier's dashboard.

  4. Added Bandwidth, Commercial Product Name, Supplier Product Name to NNI Geography Tier Definition

    What's new:

    Admins can now set up NNI Geography rules using more than just supplier and product category. Go to Rules → Geography → NNI Geography → Add New / Edit. The new fields are optional:

    • Bandwidth condition: Limit a rule to a bandwidth range using >=, >, <, or <=. The rule's NNI is only used when the solution's bandwidth meets the condition. This lets you send higher-bandwidth services to higher-capacity NNIs.

    • Commercial Product Name: Limit a rule to the buyer's own commercial product name, if configured, either alongside product category or instead of it. Reach out to your CSM for information on configuring Commercial Product Name, if interested.

    • Supplier Product Name: Limit a rule to a specific supplier product name.

    Rules without these fields work the same as before.

  5. Reseller sub-quote returns thousands of near-identical rows — surface Last-Mile Provider or collapse per productn

    Sub-quote calls grouped in API audit tracing

    What's new:

    On reseller quotes with sub-quoting, the API audit tracing log no longer lists every call as its own row. Sub-quote calls are now grouped into one line per supplier and product category, so large quotes are much easier to scan. To see it, go to CPQ Step 3 → API Status → Details

    • Grouped lines: Each line shows the supplier, the product category and how many calls it holds, for example "SUPPLIER – Ethernet - Dedicated (11 calls)".

    • Expand for details: Expand a line to see each call in it.

    • Line status: If any call in a line has an error, the line shows Error.

    • Filters: Status filters, column filters and search look at each call. A line appears if at least one of its calls matches, and expanding it shows only the matching calls.

  6. Finalize quotes and customize the Quote PDF

    Sellers now finalize a quote before generating the PDF, and can edit the PDF in a preview before it's created. The PDF itself also has a cleaner layout.

    Finalizing a quote (CPQ Steps 3–4)

    • Finalize Quote: On CPQ Step 3, the Next button is now Finalize Quote. A confirmation step lets you check your selected solutions before you commit. A quote can't be changed once it's finalized.

    • Selected Solutions tab: A new tab on Step 3 shows only the solutions you've selected. Selections stay the same across the Default, By Location, By Supplier and Selected Solutions views.

    • Step 4 is now "Finalized Quote": Step 5 has been removed. Step 4 is where you generate the Quote PDF and send the quote. Send Quote becomes available once a PDF has been generated.

    • New "Quote Finalized" status: Shows in the WIP view and in Accounts → Deals → CPQ. The existing Quote Generated and Quote Sent statuses haven't changed.

    Quote preview (before the PDF is generated): Users can now preview and edit the quote PDF before generating and sending.

    • Location & General notes: Notes are filled in from the Step 3 results and can be edited or replaced for each location. General notes can also be added that will appear below the pricing.

    • Hide content: Remove the Total MRC, Total NRC and Total Value lines, the Product Name and NNI columns, and the logo.

    • Edit sender details: Change the Contact Name, Contact Email and the "From" name shown in the PDF heading.

    Quote PDF updates:

    • New header: The heading now reads "Official Proposal from [Instance Name or edited name]". Below it are Channel, Customer, Deal, Quote, Quote Date and Quote Expiration. The instance logo appears in the top right if one has been uploaded.

    • Line items:

      • API Product Name and Product Name are combined into one Product Name column.

      • Catalog now appears as Channel in the header.

    • Terms & Conditions: Admins can add standard quote terms in Admin → Company Default Attributes → Quote PDF Terms & Conditions. When configured, the T&Cs will populate in the quote PDF.

    Quote-PDF.png
  7. Order quoted solutions in Orderbase directly from CPQ

    What's new:

    CPQ users on instances with Orderbase can now send a quote's selected solutions straight to an Orderbase order. You no longer have to find and pick them again.

    Where to start an order:

    • CPQ Step 4: A new Order button sits next to Generate PDF and Send Quote.

    • WIP → Quotes: A new Order action is in the quote's … menu. It works the same way as the Step 4 button.

    • When it's available: The quote must be in Quote Finalized, Quote Generated or Quote Sent status.

    • Access: You must have access to Orderbase to take advantage of this feature.

    What happens when you click Order:

    • Opens Orderbase Create Order: You're taken to Orderbase → Order → Create, already filtered to the quote you started from.

    • Basket already filled: All the solutions you selected in the quote are already in the order basket. You can still remove any solution you don't want to order or unfilter and add solutions from a different quote.

    • Basket/project ID: Each basket gets a unique basket/project ID, linked to the basket and the quote it came from.

    • New "Ordered" status: Once you start an order, the quote moves to Ordered and its Order actions are turned off.

  8. Smarter Supplier Suggestions for Fallout in Bid Management Supplier Pricing Request form

    Enhancement:

    In the Fallout section of the Supplier Pricing Request (SPR) form, a supplier is now suggested only if it can serve the requirement's country, product and access medium. Before this change, suppliers were suggested based on country alone.

    Benefit:

    Users get more relevant supplier suggestions and spend less time ruling out suppliers that can't serve the request.

    Example:

    For a requirement in Italy for DIA over Coax, a supplier that serves Italy and DIA but only offers Fiber will no longer be suggested.

  9. Bulk On-Demand Distribution of Building Lists

    What changed:

    We have added the ability to send building lists to many buyers at once on an ad hoc basis. Users can select individual rows of their Distributions grid via checkboxes or select all rows using the header checkbox, then initiate a bulk send via the toolbar action.

    Impact:

    • Usability & Efficiency: Eliminates repetitive manual work by allowing suppliers to distribute building list updates to hundreds of buyers in a single action instead of clicking each row individually.

    • Reliability: Distribution requests are processed smoothly in the background without browser timeouts. The system provides a clear summary of triggered vs. skipped distributions, automatically updating the Last Sent Date.

    User action required:

    None. The multi-select checkboxes and bulk Send now button are automatically available on the Distributions screen. Existing single-row send and scheduled distribution behaviors remain unchanged.

    Note: The list contains both Active and Expired lists. It is recommended to filter on a Status of Active before selecting lists to send.

  10. Buildings API: Building Category Filtering & Delta Synchronization

    What changed:

    The Buildings API (/v5/buildings) now supports category filtering, allowing users to query and retrieve records by specific Building Categories (e.g., Commercial). In addition, date-range filtering can be used in conjunction with category parameters to retrieve newly created or modified records for incremental synchronization.

    Impact:

    Significantly improves synchronization performance, reduces payload sizes, and minimizes processing overhead. Integrations no longer need to pull and process the entire building population to extract specific building categories or recent changes.

    User action required:

    None. This update is backward-compatible, and existing integration queries will continue to work without modification. To utilize category filtering, include the optional category parameter in requests to /v5/buildings (category IDs can be retrieved via the GET /api/v1/buildings/buildingCategory reference endpoint).

Issues resolved in this release

Connectbase resolved the following issues in this release.

Internal Ref #

Issue/resolution

TCW-3458

Fixed an issue where Instance ID(s) were no longer displayed alongside the company name in My Partners. Instance IDs are now displayed after the company name and concatenated when multiple instances are associated with the same supplier.

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
  1. Spectrum Charter GIS - New Seller Cloud API Implementation

    Spectrum Charter GIS API 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:

      • Coax - (Broadband/Cable): 50/15, 100/25, 250/25, 500/35, 750/35, 300/10, 600/35, 1000/35, 300/50, 500/50, 700/50, 940/50, 100/10, 300/30, 1000/50, 25/5, 50/10, 100/20, 200/20, 25/3, 50/5, 150/15, 10/1, 20/2, 60/5, 300/20, 1000/30, 250/15, 500/20, 1000/20, 2/2, 5/5, 10/10, 20/20, 30/30, 40/40, 50/50, 60/60, 70/70, 80/80, 90/90, 100/100, 150/150, 200/200, 250/250, 300/300, 400/400, 500/500, 600/600, 700/700, 1000/1000, 25/25, 75/75, 1250/35, 10000/10000, 940/35, 400/20, 200/10, 1000/35, 600/20

    • Supported Terms: 12, 24, 36, 48. 60 Month

  2. TDC Nordics - New Seller Cloud API Implementation

    TDC Wholesale Price Tool API has been implemented as an available External API integration with the following details.

    • Supported Countries: Denmark

    • Covered Products: Following products, access mediums and speeds are supported:

      • Nordic EVPN (Ethernet - Switched | Fiber): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 40, 50, 60, 70, 80, 90, 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

      • Nordic IPVPN (MPLS | Fiber): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 40, 50, 60, 70, 80, 90, 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

      • Nordic Internet (Dedicated Internet | Fiber): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 40, 50, 60, 70, 80, 90, 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, 48, 60 Months

  3. Orange Eligibility - New Seller Cloud API Implementation

    Orange Eligibility API has been implemented as an available External API integration with the following details.

    • Supported Countries: France

    • Covered Products: Following products, access mediums and speeds are supported:

      • Ethernet Switched

      • Supported Access Mediums and Speeds per Product:

        • Optimum Ethernet - Ethernet Switched on Fiber: 2 Mb/s, 4 Mb/s, 10 Mb/s, 20 Mb/s, 30 Mb/s, 40 Mb/s, 50 Mb/s, 100 Mb/s, 200 Mb/s, 300 Mb/s, 500 Mb/s, 1 Gb/s, 2 Gb/s, 4 Gb/s, 10 Gb/s

        • Optimum Ethernet Enterprises - Ethernet Switched on Fiber: 2 Mb/s, 4 Mb/s, 10 Mb/s, 20 Mb/s, 30 Mb/s, 40 Mb/s, 50 Mb/s, 100 Mb/s, 200 Mb/s, 300 Mb/s, 500 Mb/s, 1 Gb/s, 2 Gb/s, 4 Gb/s, 10 Gb/s

        • Core Ethernet Lan (SDSL) - Ethernet Switched on Copper: 0.5 Mbps, 1 Mbps, 2 Mbps, 4 Mbps, 8 Mbps, 12 Mbps, 16 Mbps

        • Core Ethernet Enterprises (SDSL) - Ethernet Switched on Copper: 0.5 Mbps, 1 Mbps, 2 Mbps, 4 Mbps, 8 Mbps, 12 Mbps, 16 Mbps

        • Core Ethernet Lan - Ethernet Switched on Fiber: 2 Mb/s, 4 Mb/s, 10 Mb/s, 20 Mb/s, 30 Mb/s, 40 Mb/s, 50 Mb/s, 100 Mb/s, 200 Mb/s, 300 Mb/s, 500 Mb/s, 1 Gb/s, 2 Gb/s, 4 Gb/s, 10 Gb/s

        • Core Ethernet Entreprises - Ethernet Switched on Fiber: 2 Mb/s, 4 Mb/s, 10 Mb/s, 20 Mb/s, 30 Mb/s, 40 Mb/s, 50 Mb/s, 100 Mb/s, 200 Mb/s, 300 Mb/s, 500 Mb/s, 1 Gb/s, 2 Gb/s, 4 Gb/s, 10 Gb/s

    • Supported Terms: 12, 24, 36 Months

  4. Qoolize - Removed API Exclusion Regex Logic

    We have updated our Qoolize API integration to remove a formatting validation on postal code based on a deprecated regex field that the API actively returns per-country.

TCW Enhancements
  1. Added Custom Pricing Zone to Bulk Search Results

    Users can now view and export the Custom Pricing Zone associated with locations in a Deal, improving visibility into pricing tiers directly within bulk address search results.

    Enhancement Details:

    • Deal View Column: Added Custom Pricing Zone as a selectable column under Manage Columns in Deal View (Accounts > Deal > Deal View), positioned adjacent to LOS Distance.

    • Data Source: Values populate directly from the local instance’s My Locations list.

    • CSV Export Support: Custom Pricing Zone is now included as a standard column in the Network Intelligence Export file.

    • Duplicate Handling Alignment:

      • When [CPQ] Allow duplicates in CPQ Address Imports is enabled, locations with multiple unique Custom Pricing Zones display in separate rows with their respective zone values.

      • When disabled, duplicate locations consolidate into a single row showing the total duplicate count.

  2. Extended Messaging Feature to Approvals Dashboard

    Extended internal messaging to WIP Approvals dashboard, enabling direct collaboration between requestors and approvers.

    Enhancement Details:

    • Approvals Dashboard Messaging: View, send, and track internal messages with rich text and attachments directly from the WIP Approvals grid via a new envelope icon with unread badge indicators.

    • CPQ Step 3 Notes & External ID: Add an initial submission note and an External Reference ID when requesting approval, and capture decision notes upon approval or rejection into the message thread.

    • Email Alerts & Deep Linking: Automated email notifications for new messages include direct links that open the relevant message thread on the Approvals dashboard.

  3. Allow Users to Submit CBM Requests for Shift of Existing Service

    Users can now submit requests to move or shift active services from an existing location to a new location directly within CPQ. This expands upon the capabilities introduced in Release 18 for changes to existing services (Upgrades, Downgrades, and Renewals).

    Key Capabilities

    • CPQ Step 2 Shift Request: Select the new Shift request type to pair existing service locations with target new locations within a Deal and provide relevant service and circuit details.

    • Deal Desk Dashboard Integration: Shift requests appear on the CBM Deal Desk Dashboard with a dedicated Shift engagement type, presenting new location line items for manual pricing or supplier engagement.

    • Supplier Pricing Requests: Send pricing requests that indicate a location shift alongside circuit details, enabling suppliers to quote the new location or submit a no-bid.

    Requirements & Availability

    • Requesting changes to existing services requires Connectbase Bid Management (CBM).

    • If a customer is interested in this capability, please reach out to their CSM to enable the feature.

  4. Allow User to Submit Diversity Request

    Users can now submit access pricing requests with specific diversity requirements directly within CPQ Step 2 and validate primary versus backup solution diversity in CPQ Step 3.

    Key Capabilities:

    • CPQ Step 2 Diversity Configuration:

      • Added a Diversity Required checkbox to standard access request configurations.

      • Supports four diversity requirement types:

        • POP Diversity: Validates different NNI locations between routes.

        • Carrier Diversity: Requires selecting at least two different suppliers before submitting.

        • Technology Diversity: Requires selecting at least two different media types before submitting.

        • Full Separation: Flags routes requiring route/KMZ verification.

      • Built-in form validations display inline alerts and prevent submission if required multi-supplier or multi-media criteria are not met.

    • CPQ Step 3 Layout & Diversity Matching:

      • Default Grouping: Automatically defaults results to a By Location view for diversity requests.

      • Primary / Backup Designator: Added a dedicated column allowing users to pair primary and backup solutions per location.

      • Diversity Status Indicator: Displays real-time visual feedback based on the selected diversity rule:

        • Green: Diversity criteria met (different POP/NNI locations, distinct carriers/last-mile providers, or different media types)

        • Red: Diversity criteria failed (matching POPs, shared carriers/last-mile providers, or identical media types).

        • Grey: Indeterminate status (missing NNI data or Full Separation, prompting KMZ review).

  5. Show Supplier NNI ID in CPQ Step 3 Results

    Users and API consumers can now view the Supplier NNI ID alongside the Customer NNI ID, NNI Location, and NNI Capacity across CPQ Step 3 results, CSV exports, and API responses.

    Key Capabilities:

    • CPQ Step 3 Grid & Export:

      • Added the Supplier NNI ID column adjacent to the NNI ID and NNI Location columns.

      • Repositioned the NNI Capacity column next to the NNI attribute fields for improved layout grouping.

      • Included Supplier NNI ID in the CPQ Step 3 CSV export file.

    • AdvCPQv3 API: Added supplierNniId and nniCapacity as standard response fields in the Get Pricing endpoint (/advanced-cpq/v3/quotes/{quoteId}/prices).

  6. Added "Wavelengths" to Product drop-down in NNI Locations and NNI Geography Rules

    Added Wavelengths as a selectable product option when managing NNI locations and geography rules, enabling NNI mapping and routing configurations for wavelength services.

    Key Enhancements

    • NNI Locations: Users can now select Wavelengths from the Product drop-down when adding or editing NNI locations under Product Catalog > NNI Locations.

    • NNI Geography Rules: Added Wavelengths to the Product drop-down when creating or modifying rules under Rules > Geography > NNI Geography.

  7. CBM Supplier Response Mandatory Fields & Attachments

    Enhanced the supplier pricing response experience by introducing mandatory response field validations, request-level notes and attachments (including .kmz/.kml support) and updated action button placement.

    Key Enhancements

    • Mandatory Response Fields & Validation: Required columns (Supplier Product Name, Currency, New MRC, New NRC, Disposition, Building Status, Supplier Price Expiration, Supplier Quote ID) are marked with an asterisk (*), highlight missing cells, and block submission until completed.

    • Notes & Attachments: Replaced the "Leave a comment" line with an Add Notes & Attachments action that allows suppliers to submit rich-text messages and attach files (including .kmz and .kml) at the request level with unread indicator alerts.

    • Action Button Updates: Moved action buttons to the bottom of the Supplier Response Form and renamed them to No Bid and Submit Pricing (previously Approve Request and Reject Request).

  8. Business Partner users should not see audit logs or details

    Enhanced role-based access controls in CPQ to restrict supplier audit logs and technical execution details from Business Partner users in the Business Partner Portal (BPP), ensuring sensitive internal supplier data remains confidential.

    • Supplier Progress Bar: Removed the Details button for BPP users. The progress bar now displays only high-level status (Pending, In Progress, Complete), elapsed time, and supplier count.

    • CPQ Step 3 Results: Removed the Audit Log action from the 3-dot menu for BPP users.

    • Internal User Access: Full access to supplier audit logs and execution details remains available for internal associates and administrators.

  9. Location-level employee count in the Tenant API

    The Tenant API v2 response has a new field, noOfEmployeesAtLocation, which gives the number of employees at the location in your request. The existing noOfEmployees field still returns the entity's total employee count across all its locations. Existing fields are unchanged, so current integrations keep working.

  10. New permission "[CPQ] Restrict Request NNIs"

    Admins can now hide the Request NNIs button in CPQ Step 2 for specific user groups. Assign the new [CPQ] Restrict Request NNIs permission to a group in Roles &amp; Permissions, and that button disappears for everyone in the group. Nothing changes until an admin assigns it, so the button stays visible for all current users.

Issues resolved in this release

Connectbase resolved the following issues in this release.

Internal Ref #

Issue/resolution

QTO-3959

Updated reseller quoting logic so that when Last Mile Provider (LMP) masking is enabled, underlying supplier information remains accessible for seller financial rules and margin calculations while remaining hidden from external quote outputs.

Key Changes:

  • External Quoting & Exports: When Hide Sub Supplier is enabled (Yes), the LMP field is left blank in Adv CPQ API responses and CPQ Step 3 exports rather than substituting the reseller name.

  • Financial Rule Accuracy: Seller financial rules and pricing logic continue to evaluate against the actual underlying LMP internally, ensuring margin rules apply seamlessly without compromising supplier privacy.

TCW-3233

When typing into the search bar, autocomplete suggestions experienced a noticeable delay or failed to appear immediately, making the search feature seem unresponsive or broken.

Resolution:

Optimized the search query and match logic so autocomplete triggers after typing at least 3 characters and sorts results after 8 or more characters, significantly reducing latency and speeding up suggestion response times.

Impact:

Affects all users searching for addresses and buildings across the platform; restores fast, responsive autocomplete behavior.

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
  1. SUNRISE - New Seller Cloud API Implementation

    SUNRISE has been implemented as an available External API integration with the following details.

    • Supported Countries: Switzerland

    • Covered Products: Following products, access mediums and speeds are supported:

      • WHS Optical (33) - Wavelengths

      • WHS Internet Direct (31) - Dedicated Internet

      • WHS EoMPLS E-Line (29) - Dedicated Ethernet

      • WHS EoMPLS E-Access (28) - Switched - Ethernet

      • WHS Internet Broadband (32) - Broadband

      • WHS Carrier Ethernet E-Line (30) - Dedicated Ethernet

      • WHS Carrier Ethernet E-LAN (72) - Dedicated Ethernet

      • WHS Carrier Ethernet E-Access (1) - Switched - Ethernet

    • Speeds

      • Mbps: 1, 2, 4, 6, 8, 10, 10/1, 10/2, 15/1, 20, 20/2, 20/4, 30, 30/6, 30/10, 40, 40/4, 40/8, 45, 50, 50/10, 60, 70, 80, 80/16, 100, 100/20, 155, 200, 200/40, 250/50, 300, 300/60, 400, 500, 500/100, 600, 700

      • Gbps: 1

    • Access Mediums: Fiber, Copper

    • Supported Terms: 12, 24, 36 & 60 Months.

    • Additional Notes: NNIs are not required for quoting E-Access

  2. Ceske Radiokomunikace - New Seller Cloud API Implementation

    Ceske Radiokomunikace has been implemented as an available External API integration with the following details.

    • Supported Countries: Czech Republic

    • Covered Products: Following products, access mediums and speeds are supported:

      • Ethernet Switched

    • Supported Access Mediums and Speeds per Product: Fiber with 2 Mbit/s, 4 Mbit/s, 6 Mbit/s, 8 Mbit/s, 10 Mbit/s, 20 Mbit/s, 30 Mbit/s, 40 Mbit/s, 50 Mbit/s, 100 Mbit/s, 200 Mbit/s, 300 Mbit/s, 500 Mbit/s, 1Gbs

    • Supported Terms: 12, 24 Months

    • Additional Notes: A rate card is needed for this supplier

  3. Added information to DTAG migration from GP & enabled address-specific quoting

    We are enhancing our PXC Partner API integration with a call to their address service for more specific location-based quoting. If an exact match is not found for the provided service location, then quoting will proceed based only on the provided postcode value (previous default functionality) with a note clarifying this in the quote results accordingly.

  4. Verizon Quote – Added Wavelength (OWS) Product (P2P)

    We are enhancing our Verizon Quote API integration to allow quoting of Verizon’s Optical Wave Services (OWS) product.

    • Product: Wavelength

    • Access Media: Fiber

    • Contract Terms: 12, 24, 36, 60

    This product may be quoted in and out of P2P Mode. When quoted out of P2P Mode, the provided service location will be quoted alongside the nearest NNI location configured for this product.

  5. Lumen Quote - Populated supplierQuoteId with PCAT Quote ID

    We have enhanced our Lumen Quote API integration to populate the Supplier Quote ID field with the generated PCAT Quote ID in successful quotes.

TCW Enhancements
  1. New Feature: Private Accounts & Access Control

    Organizations can now designate sensitive customer accounts as Private Accounts in CPQ. This restricts account visibility, quotes, and Connectbase Bid Management (CBM) workflows strictly to authorized users while filtering them out from global pipeline views.

    Enhancement Details:

    • Private Account Tagging: Designate accounts as Private during account creation in TCW or toggle status anytime via the Accounts management table.

    • Role-Based Permissions ([CPQ] Allow Private Account Access): A new permission in Admin -> Users -> User Groups controls visibility. Only the Account Owner and users in authorized groups can access private accounts and related records.

    • Global Pipeline Filtering: Users without access cannot view private accounts across WIP / Global WIP, Requests / Global Requests, or Approvals / Global Approvals.

    • Protected Assignments & Sharing: Reassignment and sharing workflows enforce privacy rules—preventing private CBM requests, deals, or quotes from being assigned or shared with unauthorized users.

    How to Configure

    • Admins: Enable [CPQ] Allow Private Account Access under Admin -> Users -> User Groups for relevant teams.

    • Users: Select Private Account when creating a new account in TCW, or update the setting on existing accounts from the Accounts page.

  2. Feature Enhancement: Solution-Level Approval Status in Audit Logs API

    Enhanced the GET Audit Logs API endpoint (logType=activityAudits) to return approval details broken down at the individual solutionId level.

    Enhancement Details:

    • Solution-Level Granularity: When querying audit logs with logType=activityAudits, the API response now includes solutionId alongside each activity approval record.

    • Accurate Approval Tracking: API consumers can now distinguish approval states (PENDING, APPROVED, REJECTED) for each individual solution within multi-solution quotes governed by Activity rules.

    API Details:

    • Endpoint: GET /advanced-cpq/v3/audit-logs/{quoteMasterId}?companyId={companyId}&logType=activityAudits

    • Updated Response Attribute: Each item in data[] now returns solutionId mapped directly to its corresponding activityName and status.

  3. Legacy API Versions Retired

    As part of Connectbase’s API lifecycle management, legacy versions of the Buildings and Network Intelligence APIs have reached End of Life and are no longer supported. The following API versions have been retired:

    • Buildings API v2 → migrate to Buildings API v5

    • Network Intelligence API v4 and v5 → migrate to Network Intelligence API v6

    These legacy versions are no longer accessible. Customers using deprecated API versions should migrate to the supported versions to ensure continued access and compatibility.

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
  1. Zayo API - New Seller Cloud API Implementation

    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

      • Danish Ethernet VPN (via NNI) (Ethernet - Switched | Fiber): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 40, 50, 60, 70, 80, 90, 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

      • 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.

  2. AAPT FrontierLink - New Seller Cloud API Implementation

    AAPT FrontierLink 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:

      • E-Line (on Ethernet Switched - Access Medium=Fiber): Speeds from 1 to 10GB, as provided by the supplier in the rate card

      • E-Lan (on Ethernet Switched - Access Medium=Fiber): Speeds from 1 to 10GB, as provided by the supplier in the rate card

      • AAPT FastFibre Metro (on Ethernet Switched - Access Medium=Fiber): Speeds from 1 to 10GB, as provided by the supplier in the rate card

      • AAPT FastFibre NBN Fibre Tc2 (on Ethernet Switched - Access Medium=Fiber): 10 Mbps, 20 Mbps, 30 Mbps, 40 Mbps, 50 Mbps, 60 Mbps, 70 Mbps, 80 Mbps, 90 Mbps, 100 Mbps

      • AAPT FastFibre NBN Copper Tc2 (on Ethernet Switched - Access Medium=Copper): 5 Mbps 10 Mbps, 20 Mbps

      • AAPT FastFibre NBN Fibre Tc4 (on Broadband - Access Medium=Fiber): 12Mbps/1Mbps, 25Mbps/5Mbps, 25Mbps/10Mbps, 50Mbps/20Mbps, 100Mbps/40Mbps, 500Mbps/50Mbps, 250Mbps/100Mbps, 500Mbps/200Mbps, 750Mbps/50Mbps, 1000Mbps/100Mbps, 1000Mbps/400Mbps

      • AAPT FastFibre NBN Copper Tc4 (on Broadband - Access Medium=Copper): 12Mbps/1Mbps, 25Mbps/5Mbps

      • AAPT FastFibre NBN Wireless Tc4 (on Broadband - Access Medium=Fixed Wireless): 12Mbps/1Mbps, 25Mbps/5Mbps

      • AAPT FastFibre NBN COAX Tc4 (on Broadband - Access Medium=COAX/HFC): 12Mbps/1Mbps, 25Mbps/5Mbps, 25Mbps/10Mbps, 50Mbps/20Mbps, 100Mbps/40Mbps, 500Mbps/50Mbps, 250Mbps/100Mbps, 750Mbps/50Mbps, 1000Mbps/100Mbps

      • AAPT FastFibre NBN Satellite Tc4 (on Broadband - Access Medium=Fixed Wireless - Satellite): 12Mbps/1Mbps, 25Mbps/5Mbps

      • AAPT NBN Enterprise Ethernet (on Ethernet Switched - Access Medium=Fiber): 250 Mbps, 500 Mbps, 1 Gbps

      • National Wholesale Broadband Fibre (on Broadband - Access Medium=Fiber): 12Mbps/1Mbps, 25Mbps/5Mbps, 25Mbps/10Mbps, 50Mbps/20Mbps, 100Mbps/40Mbps, 500Mbps/50Mbps, 250Mbps/100Mbps, 500Mbps/200Mbps, 750Mbps/50Mbps, 1000Mbps/100Mbps, 1000Mbps/400Mbps

      • National Wholesale Broadband Copper (on Broadband - Access Medium=Copper): 12Mbps/1Mbps, 25Mbps/5Mbps

      • National Wholesale Broadband Wireless (on Broadband - Access Medium=Fixed Wireless): 12Mbps/1Mbps, 25Mbps/5Mbps

      • National Wholesale Broadband - Satellite (on Broadband - Access Medium=Fixed Wireless - Satellite): 12Mbps/1Mbps, 25Mbps/5Mbps

    • Supported Terms: 24, 36, 48 Months.

    Additional Notes:

    • NBN via National Wholesale Broadband Product (NWBP): This is AAPT's NBN aggregation product. AAPT became a certified NBN service aggregator in 2011, providing NBN, Telstra, AAPT and Optus services as an independent network aggregation. The idea is that AAPT sits between you (the RSP/ISP) and NBN Co: it connects to NBN's points of interconnect, carries the traffic over its own national backhaul, and hands it to you at a small number of aggregated handover points rather than making you build presence at all 121 PoIs. The aggregation product is offered to service providers as a coherent offering, rather than splitting it into NBN and non-NBN tiers — so you can order standardised NBN access (the residential/SME NBN Ethernet traffic classes — FTTP, FTTC, FTTN, HFC, fixed wireless) nationally without holding your own NBN Co wholesale agreement and backhaul. It's the right fit for volume/mass-market broadband resale.

    • NBN via Fast Fibre Fast Fibre is a different beast — it's a carrier-grade Ethernet access service over the AAPT/TPG network. Fast Fibre is a new-generation AAPT/TPG Ethernet access service delivering symmetric 250 Mbps, 400 Mbps, 1, 2, 5 and 10 Gbps connectivity, and it can also carry NBN Ethernet TC-2/TC-4 access as well as business NBN Enterprise Ethernet up to 1000 Mbps. The key architectural point is that Fast Fibre provides a single "access pipe" that can connect up to 4 products, letting you tailor and split bandwidth across data and voice services on one fibre tail. So "NBN via Fast Fibre" means the NBN service rides as one product on this shared high-capacity, SLA-backed business access (99.95% availability guarantee with 24×7 support), typically delivered with an NTU. It's aimed at business/enterprise connectivity rather than commodity broadband.

  3. Vodafone TOP - New Seller Cloud API Implementation

    Vodafone TOP 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 Internet Access ( Dedicated Internet | Fiber): 2, 4, 6, 8, 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, 6000, 7000, 8000, 9000, 10000 Mbps

      • Ethernet Wireline - Interconnect (Ethernet - Switched | Fiber): 2, 4, 6, 8, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000, 1500, 2000, 2500, 3000, 3500, 4000, 4500, 5000, 6000, 7000, 8000, 9000, 10000 Mbps

    • Supported Terms: 12, 36 Months.

    Additional Notes: NNI required for EWL

  4. China Telecom Global MEF - New Seller Cloud API Implementation

    China Telecom Global MEF has been implemented as an available External API integration with the following details.

    Covered Products:

    • Ethernet Layer 2 (Ethernet - Switched)

      • Access Media: Fiber, Copper, Radio (Quoted as ‘Wireless - Mobile’)

      • Speeds: 2, 4, 6, 8, 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, 750, 800, 850, 900, 950, 1000

      • Supported Countries: China, Hong Kong, Japan, South Korea, Singapore, Vietnam, Myanmar, Pakistan, Kazakhstan, Russia, United States, UAE, South Africa, Kenya, Nigeria, Egypt, Bahrain

    • DIA (Dedicated Internet)

      • Access Media: Fiber, Copper, Radio (Quoted as ‘Wireless - Mobile’)

      • Speeds: 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 500, 1000

      • Supported Countries: China, Hong Kong, Japan, South Korea, Singapore, Thailand, Indonesia, Cambodia, Myanmar, Russia, UAE, South Africa, Kenya, Djibouti

    • ADSL (Broadband)

      • Access Media: Fiber, Copper, Radio (Quoted as ‘Wireless - Mobile’)

      • Speeds: 100/10, 200/20, 300/30, 500/30

      • Supported Countries: China, Hong Kong, Japan, South Korea, Singapore, Thailand, Indonesia, Cambodia, Myanmar, Russia, UAE, South Africa, Kenya, Djibouti

    Supported Terms: 12, 24, 36 Months.

    Additional Notes: This integration does not currently support China Telecom Global’s SD-WAN or Cloud Connect products.

  5. Neos Networks - New Seller Cloud API Implementation

    Neos Networks 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:

      • P2P - Ethernet Dedicated

      • NNI - Ethernet Switched

      • IA - Dedicated Internet

      • Optical P2P - Wavelengths

      • P2CCT - Ethernet Dedicated

      • NNI2CCT - Ethernet Switched

    • Access Medium: Fiber

    • Speeds: 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000 Mbit/s, 2, 3, 4, 5, 6, 7, 8, 9, 10 Gbit/s, 100 Gbit/s, 400 Gbit/s, FTTC 80:20, FTTP 115:20, FTTP 220:30, FTTP 330:50, FTTP 550:75, FTTP 500:165, FTTP 1000:115, FTTP 1000:220

    • Supported Terms: 12, 24, 36, 48, 60 Months.

    Additional Notes: NNI IDs are retrieved by calling GetNNIAgreements. This returns a list of NNI agreements linked to the customer account. Use the Id field from each NNIAgreement as AEndNNIId in the quote request.

  6. Exponential-E - New Seller Cloud API Implementation

    Exponential-E 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:

      • Smart Wires - Ethernet-Switched

      • Smart EPL - Ethernet-Switched (Note: EPL is not included in the initial Exponential-E integration and will be added in a future phase.)

    • Access Medium: Fiber

    • Speed: 1, 2, 3, 4, 5, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000

    • Supported Terms: 12, 36 Months.

    Additional Notes: NNI/PoP is not required in the request.

  7. CityFibre TMF-Eth - Extend premise matching to secondaryDesignator / buildingName when streetNr is absent

    We are updating our CityFibre TMF-Eth API integration to allow matching to CityFibre locations based on the provided building name when no street number is present in the address of the provided service location. This will increase the successful quote rate of requests containing non-standard UK address information.

TCW Enhancements
  1. Admin-Configurable Connectbase Bid Manager (CBM) Access for Business Partner Users

    Administrators can now configure and toggle Connectbase Bid Manager (CBM) access for Business Partner Portal (BPP) users via Admin, providing granular control over feature visibility and entitlement access.

    Enhancement Details:

    • Admin-Configurable Entitlement: The "Allow CBM" setting is now an editable toggle in SuperAdmin and TCW Admin for Business Partner user accounts.

    • Default Disabled State: The "Allow CBM" setting defaults to disabled upon creation or role assignment of new Business Partner user accounts, requiring explicit administrator enablement.

    • Business Partner Portal Action Control:

      • Enabled: Business Partner Portal users can view and access the "Initiate CBM" action to send CBM requests to the Business Partner owner.

      • Disabled: The "Initiate CBM" action is hidden and restricted in the Business Partner Portal.

    Business Impact

    Provides administrators with modular feature governance, allowing organizations to selectively enable Connectbase Bid Manager for specific Business Partner accounts.

  2. Make 'Allow CBM' Admin Configurable Setting for BP users

    Connectbase Bid Manager (CBM) now offers programmatic read access via new public REST API endpoints. External consumers and integrated systems can now retrieve, filter, and monitor bid management requests and detailed line-item requirements.

    Enhancement Details:

    • Given an identified companyID and quoteID, user can retrieve information about a Bid Management request.

    • Attributes: requestID, origin (Direct Engagement vs. Deal Desk), status, account, deal, quoteName, createdAt, dueDate, quoteType (budgetary/final), confirmedOrder (yes/no), endCustomerName, externalReferenceId, age, requirementsCount, engagementReason, requester, assignedTo, and suppliers.

    • Flexible Query Filtering: Supports filtering across both backing sources by quoteId, status, date ranges (createdFrom/createdTo and dueFrom/dueTo).

    • Unified Pagination & Error Handling: Merges total counts across backends with default pagination of 100 records (maximum 500 per page). Returns 404 Not Found when a specified quoteId filter yields no matching requests.

    • GET List CBM Bid Requirements

      • Given an identified requestID and/or solutionID, user can retrieve detailed requirement level information.

      • Attributes: location, product, commercialProductName, supplierProductName, mediaType, downloadSpeed, uploadSpeed, term, currency, installInterval, lastMileProvider, supplierQuoteId, connector, interfaceType, hubType, mttr, originalMrc, originalNrc, originalDispositionCode, newMrc, newNrc, newDispositionCode, siteContactName, siteContactNumber, siteContactEmail, and attachments.

      • Lifecycle State Translation: Translates lifecycle states (e.g., Waiting for Supplier, Pricing Received, Approved, Rejected) and captures both initial quoted figures (originalMrc, originalNrc, originalDispositionCode) and supplier-updated responses (newMrc, newNrc, newDispositionCode).

      • Site Contact Information: Exposes site contact information (siteContactName, siteContactNumber, siteContactEmail) at the requirement level for streamlined location coordination.

      • Attachments: Requirements include an attachments array with file metadata and secure download tokens.

    Future Roadmap

    • Programmatic Creation via POST Endpoints: These initial GET endpoints constitute Phase 1 of the CBM API suite. Future updates will introduce POST endpoints to enable external systems to programmatically create and submit bid management requests and requirements directly.

  3. Upgrade, Downgrade and Renewals now supported in Quoting leveraging Connectbase Bid Management (CBM)

    Sales and Deal Desk users can now initiate and manage pricing requests for Upgrades, Downgrades, and Renewals of existing customer services. The workflow captures existing circuit details and requested change specifications, routes requests to suppliers for updated pricing, and delivers approved pricing directly into quoting results.

    Upgrade/Downgrade and Renewal request types initiate a manual quoting workflow and require Connectbase Bid Management access.

    New Capabilities:

    • Request Type Selection: A new Request Type field is available when configuring a quote, with options for Standard, Upgrade/Downgrade, and Renewal. Upgrade/Downgrade and Renewal are visible only to users with Connectbase Bid Management access.

    • Existing Circuit Details & Change Capture: Selecting Upgrade/Downgrade or Renewal expands the configuration to capture existing service details and requested change parameters per location. Site groups are supported.

    • Supplier Engagement & Response: Suppliers receive a refined notification email and can review full existing circuit context alongside requested changes directly in the Supplier Response Portal before submitting updated MRC/NRC pricing.

    • Pricing Approval & Results: Once a supplier responds, Deal Desk can approve or reject pricing. Approved pricing flows automatically into quoting results with status and request type updated accordingly.

    • API Additions: New attributes added to Deal Desk REST API endpoints: Quote Request Type, Existing Circuit Ref, Existing Term End, Existing POP, Existing NNI, and Delivery Type.

    Business Impact

    Missing.

  4. New Rule Conditions — Commercial Product Name, NNI Capacity & Location Type

    Three new fields are now available as conditions in the Rules Engine, enabling more targeted and precise rule configuration across Activity, Financial, and CPQ rule types.

    Screenshot_2026-09-01_at_02_59_23.png

    Commercial Product Name — Supports Equal, Not Equal, Contains, and Does Not Contain operators. Blank-named products are excluded from the condition value list.

    NNI Capacity — Supports six comparison operators (Equal, Not Equal, >, <, >=, <=). Values are ordered by throughput (1G, 10G, 100G, 400G, 800G), enabling range-based rules (e.g., NNI Capacity >= 10G). NNI Capacity is not available as a condition in Financial Rules. NNI Capacity is also now returned on CPQ Step 3 results and is available under Manage Columns and User Group CPQ View Rights.

    Location Type — Supports Equal and Not Equal operators. Previously available in CPQ Rules only; now extended to Activity and Financial Rules.

  5. Activity Rule Workflow Enhancements & Approvals Dashboard

    This update enhances the Activity Rule workflow in CPQ Step 3 and introduces a dedicated Approvals dashboard in Work in Progress (WIP), streamlining how approval-required solutions are identified, submitted, tracked, and approved.

    Enhancement Details:

    Missing:

    • CPQ Step 3 Improvements

      • Specific Approval Type Display: The Requirement column now displays the specific Approval Type (e.g., Capacity) rather than a generic approval label, complete with hover text showing configured descriptions.

      • Approval Filtering & Submission: Users can filter Step 3 results to show only solutions requiring approval. When approval-required solutions are selected, the Next button is replaced with Approvals Required, updating to Pending Approvals upon submission and advancing the quote status to Approvals.

    • WIP Approvals Dashboard

      • Dedicated Approvals Tab: Replaces the former My Activities sub-menu with a top-level Approvals tab in WIP, visible to users assigned to active activity rules or rule groups.

      • Status Tracking & Assignment: Adds clear status indicators (Waiting, Requested, Complete), Activity ID, Assignee column, and an Assign to Me action for group-assigned rules.

      • Streamlined Review & Action: Approvers can click Approve/Reject to open the quote pre-filtered to items needing review, supporting individual or bulk approval and rejection.

    • Quote Advancement Validation

      • Quotes are blocked from advancing to Step 4 if any selected solution has been rejected or remains in a pending approval state.

  6. CPQ Step 3 Alternative Results Views

    Users analyzing quote results in CPQ Step 3 can now switch between different layout views to group and evaluate pricing results by Supplier or Location, making it easier to compare options and make final selections.

    Enhancement Details:

    • Default View: Displays the standard, un-grouped results layout.

    • By Supplier View: Groups pricing results into collapsible sections by supplier name, with fallout items categorized under a No Supplier section.

    • By Location View: Groups pricing results into collapsible sections by location

    • Persistent Selections: Solution selections and deselections persist seamlessly across view switches and correctly feed downstream processes (e.g., Initiate CBM, advance to Step 4).

    • Consistent Column Settings: Custom column configurations set via Manage Columns apply uniformly across all views. Export file format remains unchanged.

  7. Pre-validate building imports on upload - Improved Customer Experience

    Building imports now perform instant file validation at the time of upload, before processing begins. When you upload a building import file, the system immediately checks for structural issues — including missing required columns (Country, State, City, Street Address, Network Build Status, Building Connection Status, Transaction Indicator), unsupported file formats (only .xlsx is accepted), and files exceeding the 100 MB size limit. If a problem is found, you receive a clear, actionable error message identifying exactly what needs to be corrected.

    Impact: Previously, structural file errors were only surfaced after the import job had started processing, which could delay your workflow. Now, validation completes in under one second, giving you immediate feedback so you can fix issues and re-upload without waiting. This significantly reduces time spent troubleshooting failed imports and provides a smoother, more predictable upload experience.

    User action required: None. This validation runs automatically on every building import upload. If your import files already meet the existing format and column requirements, you will see no change in behavior. If a file has a structural issue, you will now receive an immediate error message instead of encountering a failure later in the process.

Issues resolved in this release

Connectbase resolved the following issues in this release.

Internal Ref #

Issue/resolution

TCW-2911

Issue:

GeoJSON files containing point data (such as handhole or equipment locations) uploaded to My Layers were not visible on the map. The uploaded layer appeared to process successfully, but the point features were silently invisible when viewing the map. This occurred because the platform classified all GeoJSON uploads as line layers regardless of the actual data inside the file. At lower zoom levels, some point features could also drop off the map unexpectedly.

Resolution:

The platform now inspects the actual geometry within a GeoJSON file — points, lines, or polygons — and renders the layer accordingly. Point-based GeoJSON uploads now display correctly as pins on the map, consistent with other point-based formats such as CSV and KMZ. Existing uploads of line, polygon, KMZ, CSV, and KML layers are unaffected.

Impact:

Any customer who uploaded GeoJSON files containing point data to My Layers was affected. Points were invisible on the map with no error or warning. This fix applies to new uploads going forward; previously uploaded point GeoJSON files may need to be re-uploaded to display correctly.

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
  1. Zayo API - New Seller Cloud API Implementation

    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.

  2. AT&T Price Quote - New Seller Cloud API Implementation

    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.

  3. Verizon Quote - BT - Added uniSpeed to returned info

    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.

  4. Alternatives — Added inclusive speed matching

    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.

  5. AT&T New Experience SQ - Changes to facilitate Wholesale SQ migration

    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)

  6. AT&T Wireline - Map lastMileSupplier to display as "AT&T"

    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
  1. Ability to set Building status to On Net / Near Net via CPQ rules

    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.

  2. Lowest TOV per Address per Product

    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

  • Quote Visibility & Finalize Quote Features (Release 11)Release Notes TCW.2026.R11

  • How to Use Quote Configuration Templates for Faster Quoting (Release 11)Release Notes TCW.2026.R12

  • Unique Site Requirements by Site Group (Release 10)Release Notes TCW.2026.R10

  • New TCW Admin Features (Release 9 & Release10)Release Notes TCW.2026.R09Release Notes TCW.2026.R10