- bug fix 12923 – Fixed issue on saving equipment needs exiting from UBO then logging back in
- bug fix 12935 – Fixed issue on record not found error when deleting package
- bug fix 12076 – When crons generates invoice on ISP’s invoice generation day, the terms should then be correct.
Archives for November 2012
In Microsoft Windows, Ultimate Back Office now detects if your computer has a PDF Reader installed. Now, a tooltip will appear when you hover over disabled PDF-related buttons to suggest a download unless UBO detects that a PDF Reader is installed. This improvement was recently applied to the following interfaces:
Statements tab > Credit/Debit Memo button
Statements tab > Credit/Debit Memo button
Statements tab > Receive Payment button
Statements tab > Receive Payment button (Receipt)
Statements tab > Statement Preview button
Invoice > View PDF button
ISP Config > Billing Options > Forms > Preview
- bug fix 12917 – The [$] is now temporarily disabled. It is also shown in the prompt.
- bug fix 12712 – If a PDF Reader is not installed, a tooltip will show up when hovering the disabled Print & Post button saying this: “This feature requires a PDF reader for viewing. You can download and install one from [download page link]Adobe[/link].” But if a PDF Reader is already installed, the Terms and Condition window will show up in front of all the other components of the software. These changes were applied to:
- a. View PDF of the Invoice
- b. Print Receipt for a Received Payment
- c. Statement Preview
- d. Credit and Debit Memo
- e. Forms Panel
- f. current monthly invoice
- g. queued items
- bug fix 12908 – The rates shown are now dependent on the billing cycle of the subscriber.
One of the challenges with a high level of automation is that if one critical cog in the machine is misaligned, it can create problems that may not show up until weeks or months later.
For UBO 6 Beta, certain exceptional sets of variables have resulted in errors in a small percentage of invoices over the last few months. We’ve manually repaired the invoices, and systematically repaired the code. We’ve also identified the common-denominator culprit, which has been edits to the Paid Thru date by innocent, well-intentioned app users. Unfortunately, at this point, so many automation functions are tied to the Paid Thru date that those edits can have unexpected consequences for that subscriber’s future automated invoicing.
To resolve these issues, we are doing the following:
- We’ve engineered a detailed map to navigate every known possible combination of billing scenario in Version 6.
- We’ve developed an exhaustive testing protocol for invoice changes and have executed the protocol on our “Time Travel” test server where we can prove in a matter of hours the invoicing functions as expected over a period of many months, by essentially forwarding the clock of the server and executing the scheduled auto-actions and crons.
- Every possible scenario where editing the paid through date has been required has been mapped out so that editing the paid through date will be unnecessary and the ability to edit the paid through date will be eliminated. The paid through date will be editable by our staff only to be sure it doesn’t cause unexpected behavior in your billing.
- Version 6 will not be released out of beta until we’re absolutely confident that there are no issues and the bug count (which is already at a record low) drops to and stays at zero for some period of time.
Update 11/28/2012: Paid Thru date changes are an external variable and just one piece of this puzzle. The remaining invoices affected are roughly 1 in 1000 where a few ISPs have all the right variables and have had multiple invoices affected and most other ISPs have been completely unaffected. We’ve written auditing tools to identify every affected invoice and are currently proactively correcting the errors. If you have affected invoices, we’ll follow up with you directly with full details. To significantly reduce the likelihood of these kind of issues appearing again, Version 7 invoicing code has been completely redesigned from the ground up to eliminate Paid Thru date dependencies and complex variable relationships.
– Todd Grannis, CEO
- bug fix 12883 – The column width, columns displayed are now included in the preferences and will now be remembered the next time you open the software and equipment manager.
There may be some packages you create and allow signups without requiring a credit card, such as a supporting a multi-tenant unit building where you simply send one bill to the building manager and internet service is included with the tenant’s rent. This scenario is now supported in UBO 6 giving you the option to turn off the credit card requirement for certain packages.
In ISP Config > Packages > [Package Name] > Options, you’ll notice the option to Require Credit Card Payments upon Signup. This option is checked by default when you create a new package.
Above is an example of the online signup page when you check the Require Credit Card Payments upon Signup box.
And this is an example of the online signup page when it’s not checked.