Bug Improvements & Performance Enhancements
This release was focused heavily on bug fixes and performance enhancements, as detailed below.
Ability to Reactivate Retired Plan Frequencies
In the past, if a plan frequency was retired, but then you decided at some later date that you wanted to offer that frequency again, it couldn't be re-added. To make this possible, Fusebill has added the ability to restore a retired frequency to draft, edit the pricing for any products that were added to the plan since the frequency was retired, then activate the restored frequency. For more information see the FAQ Why won't Fusebill allow me to add a frequency to a Plan? / How do I reactivate a retired Plan frequency?.
Authorize.net now supports sending of the CVV number
It is now possible to Specify the NetSuite location for Purchases through a dropdown in menu in the Quantity section for the Purchase page. This is important for tracked item purchase of devices where many devices are being purchased and therefore need to be sourced from multiple locations (for example, 50 from the Atlanta warehouse, 40 from the Seattle warehouse, and so on).
- Fixed the time range dates in the CSV file created by the Summary Journal Export to accurately reflect the time range specified by the report requestor.
- Fixed an error that was occurring when changing the Event Log page size from 10 to 100 after sorting by the Sent Timestamp column; pagination now works as expected.
- Fixed an issue that was occurring when cancelling a plan though the customer subscription grid. The spinner kept going, making it difficult to tell whether the cancellation had been applied or not. This now works as expected.
- Fixed an issue where the bulk purchase upload was interpreting the second-row helpful hint (describing what to put in the columns) as an item, which was causing false errors in the system. The second-row helpful hint is now ignored.
- Fixed a proration calculation issue that was occurring for subscriptions with multi-month frequencies (for example, three months) where billing was forced to the first of the month
- Fixed a draft and posted invoice issue that was occurring for day 31 customers when the previous month had less than 31 days; the due date is now being set correctly
- Fixed a proration calculation issue that was occurring for subscriptions added after a scheduled migration was set up
- Fixed an issue where, when a subscription was activated via the iframe in Salesforce, the subscription object in Salesforce was staying in draft until the update event was actually processed. The Salesforce object now immediately changes to “Active”.
- Fixed an issue where, when “Maintain Subscription Products in Salesforce” was disabled, edits to subscription products still caused them to be sent to Salesforce. This no longer occurs.