Chargebee Release Notes

The following issues were fixed with this release:

Avalara email notification to inform that the integration was not functional, was not sent to the user as expected.

Sales tax was found to be incorrectly displayed as 0 for the month of July for the state of Ohio within TaxJar due to non sync of TaxJar credentials.

We have updated the tool-tip message for third-party integrations on the Taxes page to fix a copy issue.

Attempting to add a one-time charge to a pending invoice with HSN code and Avalara tax code using API was generating a successful invoice response instead of throwing the error message 'Avalara not configured the site'.

We have fixed the 'Manage API Calls to Avalara' pop up window that was broken for Canada region.

We are thrilled to introduce the Feature Availability Metrics (FAM) feature in entitlements, offering insights into feature distribution across plans, addons, and subscriptions as well as the count of overrides for a feature. Use FAM to make data-driven decisions on trial management, packaging experimentation, and revenue growth. FAM primarily offers four essential metrics.

1. Feature Availability Across Items
2. Feature Availability Across Subscriptions
3. Count of Subscription Overrides
4. Count of Limited Period Overrides Learn more about Feature Availability Metrics (FAM) using our documentation.

We are excited to introduce an update to our filters on the index pages that aims to provide users with a more intuitive interface while simultaneously reducing the load on the system. These improvements will streamline the process of refining search results and enhance overall system performance.

Key enhancements include:

1. Multiple Condition Addition: Users can now add multiple filter conditions before applying the filter, simplifying the filtering process and making it more user-friendly. With this update, users no longer need to wait for the filter to be applied before adding a new condition, thus reducing the overall time spent while applying a filter.
2. Reduced System Load: The enhanced filter UI optimizes system performance by reducing the required API calls. Users can build their filtering criteria before applying the filter, which minimizes the strain on our backend systems and improves efficiency and responsiveness, especially during peak usage times.

We are confident that these changes will positively impact the user experience, and we encourage you to explore our updated filter UI to take advantage of these new features.

The following enhancements have been made to the full-page layout of Checkout:

1. Make Email Read-only for a Logged-in Customer: This change restricts customers from modifying their email ids once signed in.
2. Back to Cart Functionality Update: Users can now seamlessly return to their shopping cart from the product page, mirroring the expected behavior of a web browser's back button.
3. Support Addon Billing Cycles for Recommended Add-ons: This enhancement allows a billing cycle frequency configured by the merchant for a recommended addon to be honored in the full-page layout of checkout.

Note - This feature is in early access. Submit a request to enable this feature.

Previously, when attempting to map records based on external IDs, NetSuite would raise an exception stating, 'Transaction type specified is incorrect' if the same external ID was used for different entities. We are pleased to announce an improvement in how this situation is handled. Instead of the generic error message, we have refined the error handling process. Now, when entities with the same external ID exist in NetSuite, the system will display a more informative error message: 'This record already exists.' This enhancement will provide you with clearer and more actionable information when dealing with duplicate external IDs during mapping, leading to a smoother and more intuitive experience.

Note: This feature is in early access. Submit a request to enable this feature.

You now have the ability to override the default unit of measure that applies to addons during the checkout process. This override will be reflected in the Checkout interface.

If translations are provided for the unit of measure, they will be taken into account during the checkout process.

If a product in the catalog has an explicitly mentioned unit of measure, that unit of measure will be used for that specific product during checkout.

When the checkout is rendered in a non-primary language, translations provided in the language pack will be prioritized over the unit of measure provided in the catalog. If no translation is available, the fallback will be the unit of measure provided in the catalog.