Cloud Console 2.2 - new version

What’s new

  • Availability of the Free AV tier within the Up-Front billing model.-
    In case your trial period expires or your payment is overdue you will be switched to the Free tier. You will be definitely notified about this situation in advance so you will have a lot of time to solve it.-
    The Add-ons column has been removed from the device list.-
    Ability to set up the SOCKS and NTLM proxy during the creation of the installer package.

What has been fixed

  • Fixed problem with wrongly reported date of some notification.-
    Fixed problem with missing information about a count of devices with the failed task result.-
    In case of click to the refresh icon, the focus of opened tab was lost.

Next release in 14 days will be quite a lot focused on improving our backend and paying technical debt. But as usually we will bring some new features as well.

Hi all, we found out a critical issue on production causing that all User Management functions (invite, delete, suspend/activate) don’t work for accounts created before last release (1.6.2016).

We will try to fix it today and go to a stage server. We are not sure, if we are able to deploy it to production today. We will do as much as possible to fix it asap. Definitely by Monday. We apologize for any inconveniences.

What does “paying technical debt” mean?

Good question. In general it’s improvements not visible for customers which makes the code more sustainable, robust, etc.

To be more concrete our plans are following

  • Upgrade Javascript framework
  • Use http://sass-lang.com/
  • Use standard Dependency Injection framework
  • Improve RMI calls between datacenters
  • Speed up our build process

We will deliver the changes continuously. Our internal rule is 60:20:20. 60% of development time spend on new features, 20% on bug fixing, 20% with technical improvements / paying technical debts.

We just deployed a hot fix to production. Everything related to user management works now. The problem is that users, who were invited between 1.6.2016 and 3.6.2016 won’t be able to login with the same e-mail even after this fix. It is caused by a side effect of a bug (DB inconsistency). Unfortunately we are not able find and fix the inconsistency. The workaround is to use a different e-mail. If case you need use the same email please contact our business support directly from https://support.business.avast.com and we will fix the entry in DB.