- bug fix 17111: ‘(Recurring)’ and ‘Expires’ are now reserved words for Custom Invoice Item Description. When Recurring and Expires are checked, the words ‘(Recurring)’ and ‘Expires…’ will trimmed from the description.
- bug fix 17399: Extra zeros at the end of subscribers’ zip are now removed in the invoice PDF.
- tticket fix 12653+ : Default tax is now being set when signups are through towercoverage prequalification.
- bug fix 17408: Voided transactions are now excluded in ISP Auto-pay calculation. CC payment will now be processed on the specified autopay date.
Archives for 2014
Section 5.3 of the FCC’s 477 reporting requirements is for all blocks where you *can* provide coverage, not just the blocks where you have subscribers. Be sure your report in Section 5.3 is accurate to help prevent large telcos from securing government funding to roll competing services in areas you already have coverage.
Ultimate Back Office reports the blocks where you have subscribers and does not yet have a means to show your entire coverage area and the blocks covered by your network. Exporting this detail is a function of a coverage mapping system.
So in order to accurately represent your coverage for Section 5.3 of the Form 477, we recommend consulting with a coverage mapping provider, such as TowerCoverage.com who can build the report for you. Building the report is a complex and still somewhat manual process, so there a modest fee of $250 per report. TowerCoverage.com also integrates with UBO to enhance it’s mapping power. Simply enter your account details in the ISP Config > STEM Settings.
Note: Extended submission for FCC report is until December 11, 2014.
Google recently updated its API to require an additional layer of user authentication and no longer supports access without the end user’s authentication. This caused an issue in UBO even if you already had it setup in UBO before. UBO has now been updated to support the latest API of Google Calendar, which our developers reported was cleaner and has the added benefit of being more responsive, especially for accessing maps from within UBO.
Here are the steps you need to follow for that: https://visp.net/tsm-instructions/
- tticket fix 12625+ : When you don’t have a Merchant Account enabled, “Please set my account up for Automatic Billing:” text portion in the PDF will be hidden for your subscribers’ invoice PDF.
- bug fix 17369 : Source and Source Details can now be added in the Main Table if Display Marketing Source and Source Details is checked in the ISP Config > Subscribers.
- bug fix 17333 : Over-usage charge line items are now displayed using the normal font size.
- bug fix 17303 : Ticket and Schedule Manager now works as expected and will now require a one-time authorization to connect UBO to their Google calendar account.
- bug fix 17276 : In MAC Yosemite, ISPs can now enter data in the fields of the Add New subscriber after the window opens.
- bug fix 17081 : Send option for Queued Invoices is now available. It would have the same behavior as the Send option in Monthly Invoice.
- bug fix 17282 : eCheck option is now hidden from the Account Manager if subscriber has no stored eCheck data.
- bug fix 17336 : STEM Settings will now display the saved email and password correctly.
- bug fix 16601 : Deleted subscribers are now excluded from the update paid-thru date script.
- tticket fix 12534+ : Paid Thru Date has now been updated for invoices generated for unsuspending packages upon payment for those who do not invoice suspended packages.
Google now has an authorization process that would restrict the UBO to continue accessing the Google Calendar of the accounts that you provided in the STEM Settings.
In order to continue connecting your Google Calendar with UBO, you would need to allow access for UBO visp.net to access the calendar. This is just a one-time authorization and does not require you to do it again.
Here are the steps to follow:
- When scheduling a ticket or syncing tickets, a popup would appear:
- After clicking OK, your default browser will open the Google authorization page.
- If there is no existing Google account logged-in, the Google sign-in page will be displayed and will redirect to the auth page after signing in.
- If there is an existing Google account logged-in, the authorization page will default to using that account. Check the account logged-in in the upper right corner of the page.
- In the Google Authorization page, click Accept button to allow UBO visp.net to access the Google Calendar of the email account indicated in the upper-right corner.
- You will be notified that you have successfully authorized UBO visp.net to access your calendar.
- You can now go back to the software and continue the task you were doing, whether it was syncing tickets or saving and scheduling a ticket.
- You can actually verify if you have authorized UBO to access your calendar. Here are a few steps to follow:
- In your Google page, click on the Google image in the upper-right, and select Account.
- Click on the Security tab. In the Account permissions category, click View All in the Apps and websites field.
- You can now see UBO visp.net permitted to access your Google Calendar.
- If you need to Revoke Access UBO visp.net in your current Google Account and change your STEM calendar Google Account, kindly inform Visp.net Client Success Team to further assist you since you already have a saved authorization code saved in our database that cannot be overwritten automatically for security reasons.