Page Comparison

We are excited to announce a new feature that allows end-customers of Standard Edition (White Label) Resellers to upgrade (fully or partially) their subscriptions directly through the Standard Reseller’s Storefront. This feature lists possible upgrade options for products and calculates prices based on the product’s markup and the special price for the end customer, while the billing period will follow the reseller’s settings. After a successful upgrade, the updated subscription will appear on the Subscription List page, with the quantity of the initial subscription adjusted accordingly.

With this release, our platform now fully supports Adobe's "Minimum Purchase Quantity" for Educational products and add-ons. This enhancement is particularly advantageous for educational institutions looking to acquire specific Adobe Educational (EDU) offers because it is quite easy now to distinguish between products without and with a minimum purchase quantity during the ordering process. Specifically, our platform effectively meets this Adobe requirement by facilitating both automatic and manual updates for such EDU products via the Adobe Service Manager’s respective drop-down button. Additionally, each Adobe EDU product in the BSS portal now includes a designated field indicating the minimum purchase quantity (whenever applicable), meaning that this information is now clearly presented in both the product description (name) and the product details page.

We are excited to announce a significant enhancement to our platform’s security and privacy features.

Introducing the .personal-data CSS Class

To better protect personal and private data, by ensuring that the customer’s data will not be stored indirectly from translation services, we have developed a new CSS class called .personal-data, for every field containing such data. This class is designed for distributors who use translation systems like "Weglot" or similar services in conjunction with our platform.

Key Benefits:

• Exclusion of Personal Data: The .personal-data class allows administrators to exclude specific field values that are considered private or personal from being automatically translated. This ensures that these values remain untranslated and are not saved during the translation process.

• Field Labels Remain Translatable: While the actual values of the fields marked with .personal-data will not be translated, the labels, names, and titles of these fields will still be translated, ensuring clarity and usability.

It is the responsibility of the system administrators of these translation systems to utilize this new CSS Class to implement an exclusion rule, meaning that whenever the .personal-data class is applied to a field, the translation mechanism will recognize it and exclude the field’s value from translation.

This enhancement underscores our commitment to safeguarding your personal data and providing you with the tools to maintain privacy and security. We encourage all administrators of such translation systems to implement the aforementioned exclusion rule based on this new CSS Class to ensure the protection of sensitive information.

ℹ️ For more information on how to proceed with the suggested exclusion rule based on our CSS Class .personal-data, you can check the following “Weglot” documentation: https://support.weglot.com/article/95-how-to-exclude-urls-blocks-words-from-translation

⚠️ Please note that for old customer data that may be already stored as translations inside the Weglot or other translation systems, the removal can be performed manually, throughout the respective translation system.

The following issues were addressed, with fixes applied where necessary:

1. Erratic Bug During Microsoft Subscription Upgrade - Issue Resolved: We resolved a bug where upgrading an existing subscription from the Storefront failed due to license discrepancies between the platform and the Microsoft Partner Center. This error that was being caused by the bug also allowed changes to the subscription quantity, even though it had a Failed status, which should not have been possible. The root cause was identified in one of our checking processes, which did not handle multiple order items correctly. A fix has been implemented to address this specific bug.

2. User Permission Rule Defaulting During Sharing - Issue Resolved: We have resolved an issue where the “default” checkbox in permission rules was incorrectly set to TRUE for users with whom the rule was shared, even if the owner did not enable it. Now, the default setting will only apply as intended by the owner. Owners can simply edit and save the rule to update the default field. If a permission rule is marked as compulsory, the default value will remain TRUE for the shared user.