Google Workspace Connect 1.0.2 Release Notes

Introduction

This document describes the new features, enhancements and fixed issues introduced in Google Workspace Connect v1.0.2

The Connect processor was moved to Extension as a Service (EaaS).
COAD-4451. The validation of transfer tokens has been removed to align with new procedures implemented by Google.
COAD-4078. The Transfer Check tool has been added to the Google EaaS connector.
COAD-4591. A new ordering parameter is available to enable or disable the subscription's auto-renewal status.

CG-831. We have resolved an issue to prevent users from importing the same subscription twice.
CG-841. We have resolved an issue that sometimes prevented usage from being generated for flexible subscriptions.
GC-843. An error message is now displayed when an item does not have an offer_id configured.
CG-837. We have fixed an issue to ensure that the connector sends the email address provided in the corresponding parameter to Google in cases when the wrong email was provided initially.

The processor_skip_list parameter is now used to approve offline cancellations.
The ignored_customer parameter is no longer used.

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.
Item validations in UX1 are not done when ordering flexible items.
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

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.