Version 4.2

Important Notice #1

Please note that, due to the vCenter Chargeback product being sunsetted in June 2014, the “vCloud + vCenter Chargeback” integration (service module and device module) has been deprecated.
As the integration will be removed in a future release, we strongly recommend you start planning for an alternative solution as soon as possible if you are currently using this integration.

Important Notice #2

As announced in the 4.0.5 release changelog, the client.service_prorate API method has been removed.

Enhancements

General

  • Added the ability to create custom Usage Collectors for the Usage-based Billing Framework introduced in 4.1
  • Added support for ##first_name## and ##last_name## variables to password reset notices
  • Added a new Plugin Framework (read more about using Plugins and developing Plugins
  • Added background tasks manager
  • Added Event alerts when background tasks fail
  • Added inline documentation to the config.ini.php file, including all currently valid configuration options

Client Manager

  • Added new field to client profile to store the client VAT number, which when defined appears on invoices and credits documents
  • Added customizable invoices
  • Added Alipay Global Cross-border Website Payment support
  • Added Stripe Checkout support
  • Added support for ##invoice_total## variables to invoice notices, which displays the total amount on the invoice

Support Manager

  • Improved support for parsing incoming UTF-8 emails

Device Manager

  • Added the ability to delegate/sub-delegate DNS zones based on RFC 2317

Order Manager

  • outlook.com domain no longer allowed when using the “Non free email address” rule in order forms

Reports

  • The payment gateway used for each transaction is now visible in the Charge Log report

Bugfixes

General

  • Improved consistency between Settings menu links and their page titles
  • Updated zh_TW language name / description from “Taiwan Mandarin” to “Traditional Chinese”
  • Fixed a bug which could cause database schema updates to fail on MariaDB during upgrades

Client Manager

  • Removed the ability to change a client’s brand
  • Fixed some PHP notices when displaying details for OnApp Billing service module
  • Removed the no longer existing ECHOnline and KwikPay payment gateways, and removed “Protx” reference from Sage Pay payment gateway
  • Updated the Edit Service, Quick Edit Service, and Group Edit Service popups to be more consistent
  • Updated OnApp Billing service module to support billing by user ID, vCloud resource pool ID, and CDN ID. Billing by user ID now additionally bills the resources used by the user’s VMs
  • Fixed blank page (or 503 error page in some cases) when setting up OnApp Billing service module
  • Fixed an incorrect timeline being displayed in some circumstances on the service details page
  • Fixed a bug which could cause some service module errors not be caught correctly when executing invoice cron
  • Removed the no longer existing Cashigo payment gateway
  • Added some information to the Stripe payment gateway configuration page on how to deal with “Sending credit card numbers directly to the Stripe API is generally unsafe” Stripe errors
  • Invoice will now generate correctly when containing usage data based on a datasource from a disabled plugins

Support Manager

  • Fixed ticket printing to hide page header, footer and sidebar

Device Manager

  • Fixed issue on facility contacts report where “Notify” and “Third-Party Entry” values on CSV wouldn’t match report
  • Improved performance for listing of available IPs when adding IP assignments
  • Add IP assignment popup now shows the proper groups related to current client
  • Removed the unused “Portable” field from IP Assignment popups and views

Order Manager

  • Improved error when no order queues are defined so the page won’t prevent navigation away from the page
  • Fixed quote credit card pre-authorizations being captured immediately when using Authorize.Net

API

  • Removed API method client.service_prorate
  • Fixed error when processing Open Ticket order module via the order.process API method

Stay up to date with our product and company news

Subscribe for email updates