Google Workspace Connect 9.0 Release Notes

Introduction

This document describes the new features, known limitations and known defects of Google Workspace Connect v9.0

Google Workspace Connect 9.0 introduced the following new feature:

The Cloud Identity and the Admin Console URL are now synchronized when provisioning new orders, as Google recently started providing such data in the customer information. The data will be stored in two new fulfillment parameters, which will be displayed in the activation template.

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.
Order renewal is not supported. Although CloudBlue supports the configuration of renewals, if renewal settings are changed in the platform, the processor will not receive any notifications. Therefore, the new renewal settings will not be sent to Google. For this reason, order renewal actions are not supported.
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 are not supported in UX1.

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.