Google Workspace Connect 1.2.0 Release Notes

Introduction

This document describes the enhancements introduced in Google Workspace Connect v1.2.0

XDSB-12218. The connector now supports purchasing customer-specific offers instead of generic marketplace-wide offers. This means each customer can access tailored offers with unique discounts and pricing. This feature is available exclusively for existing customers during the purchase process. Now resellers can optionally specify a Customer-Exclusive Offer ID when purchasing a Google product. If no customer-exclusive offer ID is provided, the connector will attempt to automatically locate a matching offer ID from the general catalog in Connect, based on the product being purchased. If no matching offer ID is found in Connect, the connector will prompt the user to enter a custom offer ID.
For additional information see the FAQs in the Channel Operations Guide.
XDSB-13894. We have resolved an issue where a change request to increase the license quantity was incorrectly rejected by the connector, citing a downsize-related error.

Any billing change on the Google's Provider Panel will not be synchronized with the Connector/eCommerce Platform.
In N-Tier models, it is not allowed to move a customer account from a reseller with Cloud Identity A to a reseller with Cloud Identity B. Changing this channel partner link is not allowed.
As this product has Pay-as-you-Go items, the BSS systems must support the Google Flexible plans billing type, so that the billing is properly done. For these plans, usage will be reported daily with the current number of licensed users, so the BSS systems will prorate this usage information. It should not be managed following an "additive" model.

Note: To see more details about the Google Flexible plans billing type, refer to the following website: https://support.google.com/a/answer/1247362
Item validations in UX1 are not done when ordering flexible items.

When a transfer operation fails due to an unforeseen error, the customer is created in Google, but the API response only contains data from the customer that belongs to the original reseller, who has not been transferred yet. For this reason, when retrying the transfer process, it is necessary to manually copy the value of the Google Customer Identity parameter in the failed request and use it to populate the same parameter in the new request.