Page Comparison

We are excited to announce the availability of the End-Date Alignment feature for Coterminating New NCE Subscriptions, which can now be purchased with Installments, as a Billing Plan. The fusion of those two features, leads to an overall enhanced Storefront experience and purchase flexibility for your customers. Now, your CSP partners can easily align the end date of a new seat-based New Commerce Experience (NCE) subscription with an existing NCE subscription, and purchase an NCE base products and add-ons with the flexibility of monthly or annual installments (whenever applicable, when the Installments feature is enabled in the organization).

Feature Versions

• Current Version: Purchase and Coterm a new NCE subscription with Installments from the Storefront (for Direct Customers and Resellers in the Basic & Standard Edition).

• Upcoming Version: The End-Date Alignment feature becomes available for coterminating new NCE subscriptions purchased through the BSS.

In this release, users of BSS and Storefront can purchase Adobe Stock Credit Packs for Teams or Enterprise. Credit Packs are a flexible way to purchase assets on Adobe Stock. The product of type Asset is created automatically by running the Get Services Definition process inside the Adobe Service Manager. The products are created automatically, and the pricing is also retrieved automatically from Adobe.

With this release, BSS users can use the Edit Pricing Info option to update the pricing (via price list change or discount) of subscriptions with installments for the current billing cycle. This improvement includes subscriptions with external pricing and/or price protection.

For API v2.2, the method POST /api/Subscriptions/{subscriptionId}/pricinginfo can now affect subscriptions with installments for the current billing cycle.

From this release and onwards, when a BSS user changes their password from the BSS Setup > Administration > Personal Setup > Profile, the platform will also request the current password, for security reasons.

In the upcoming releases, we will introduce the Two-Factor (Authentication (2FA) to both our platforms, first the Storefront and afterwards the BSS. This security feature will enable Storefront and BSS administrators to offer their users an extra layer of protection during their login by enhancing the security of the platform and the privacy of the accounts.

We would like to inform you about a bug, related to the aforementioned release note, that we are working on correcting. This bug affects the transferring of upgraded and/or coterminated NCE subscriptions with or without installments when a Lite reseller is upgraded to a Tenant reseller, and transfers such a subscription. Specifically, a Lite reseller has an upgraded subscription with fewer installments than its billing term (e.g., 10), and some billing cycles have passed (e.g., 2) on the root organization. The Lite reseller is then upgraded to a Tenant reseller and decides to transfer their subscriptions. Allthough, only the installments of the upgraded subscription should be transferred to the tenant (i.e., 10 with 2 excluded), all 12 installments are transferred, which is incorrect, because this upgraded subscription never had 12 installments.

💡 Therefore, in case you wish to transfer an upgraded subscription or a coterminated subscription (with or without installments) you must not do this without our assistance. Please raise a support ticket at support@interworks.cloud, and our support department will assist you.

Certain CSS Class changes are introduced in this release and affect customers who utilize custom CSS code for certain Storefront buttons. Please review the list to verify if any of those changes affect your custom CSS code or not.

• First Change → “OK” button in the Confirm Modal [bootstrap-confirm-box-modal]: The CSS class btn btn-success is now changed to btn btn-primary .

• Second Change → “Close” button in the Alert Modal [bootstrap-alert-box-modal]: The CSS class used now is the btn btn-secondary .

  • Customers that utilize the CSS class btn btn-success will not see any change since the color will remain as is.

  • Customers that utilize the CSS class btn btn-danger will see the button changing its color to red.

• Third Change → “OK“ button in the Cookies Ribbon: The CSS class btn btn-cookie is now changed to btn btn-secondary . Customers that do not utilize our CSS Cookie Ribbon are not affected. However, for customers who do utilize it, the following CSS code changes need to also be applied:

  Code Block
  language css
  //MAIN STYLE .btn-cookie { background-color: red !important; border-color: red !important; color: white !important; } //ON HOVER STYLE .btn-cookie:hover:not(:disabled):not(.disabled), .btn-cookie:focus:not(:disabled):not(.disabled), .btn-cookie.focus:not(:disabled):not(.disabled) { background-color: yellow !important; border-color: yellow !important; color: black !important; } //ON ACTIVE STYLE (ex: WHEN CLICKED) .btn-cookie:not(:disabled):not(.disabled):active, .btn-cookie:not(:disabled):not(.disabled).active { background-color: purple !important; border-color: purple !important; color: white !important; }