Release Notes

February 23, 2017

Portal

  • Portal Exception message was unclear when a user without ‘ticket add’ and ‘ticket view’ permissions tried to create an upgrade order. New change accurately indicates that the user must have these two permissions in order to create an upgrade order.

API

  • None

Backend

  • Fixed two separate bugs in Endurance and Performance Storage provisioning where provisions were stalling due to API call timeout.

February 16, 2017

Portal

  • Resolved an issue that was preventing punny code domains from being added using the ‘Add Bulk Domains’ tool in the customer portal.

API

  • None

Backend

  • Added some backend code to help automation issues related to sending automated password reset emails.

February 8, 2017

Portal

  • Added a customerWaitTime field on the ticket search page in the customer portal. The customerWaitTime is the time the customer has been waiting for a response on a ticket. Multiple updates by the customer have no effect on this field and a reply by an employee resets the timer to zero.
  • Pushed fix that tests that only numbers, letters, and spaces are allowed for all of the titles for contacts when trying to order an SSL certificate. The Symantec API does not accept any special characters in the ‘title’ field for contact information and this was causing orders to fail.

API

  • None

Backend

  • Resolved a bug preventing OS reloads from having partitions if reloading from a Customer Supplied OS (NO OS System).

January 25, 2017

Portal

  • Fixed an issue where the “Add to Order” button overlaps dropdown list content when the list is too long

API

Backend

  • Resolved an issue that was causing Virtual Guests to fail reboot when residing on a host that has been marked as disabled for new instances.
  • Fixed an issue that caused

January 12, 2017

Portal

  • Pushed code to display the correct validation error when a number greater than 999 is used in the % field of Auto-Scaling policy actions. Previously a generic error message was displayed.

API

  • None

Backend

  • Updatd our Microsoft Proxy to handle new TLS requirements by .NET. A recent update to .NET for windows 2012 r2 added a much more strict TLS validation for powershell which in turn caused Post Install Scripts to fail during download.