We’ve published a new release of TimeXtender Portal with the following changes:

New

• New organization type: Subscription. The new pricing is now reflected in the Portal by the inclusion of a new organization type, subscription, and the four subscription packages.
• New organization type: Sandbox. Another addition coming from the new pricing is the new sandbox organization type. It allows TimeXtender and partners to provide a sandbox environment for customers on the Premium and Enterprise subscriptions where this is included. Sandbox organizations have a time limit, similar to trials, and can only add one of each instance.
• TimeXtender ❤ Exmon: You can now unlock and access the Exmon features right from the Home page of the Portal. 

Changed

• It is no longer possible to add Free or Premium customers.
• "Premium" has been renamed "Legacy Premium"
• The search bar on tables is now disabled when loading
• We’ve added a search bar to the Users list under Admin > Users
• We’ve added a sidebar to the TimeXtender REST data source connection form.

Fixed

• Long data source names were not fully visible in the transfer instance modal
• Edit preferred support would sometimes fail with an unhandled exception
• Fixed values appearing twice under data source connection details
• "Move" user on a Premium customer would throw a "customer manager permission required"
• The tooltip on the environment description was clickable despite being empty
• Fixed tooltip placement for missing mapping in environments
• Fixed spacing on the TimeXtender REST data source connection form
• Instance names are now truncated if they are too long in the transfer instance modal
• Fixed an issue where mapping a data source connection would result in an error
• Fixed an issue in the add/edit semantic model instance form where certain fields in the CSV endpoint wouldn't be correctly disabled
• The user/customers tables are now refreshed when a new user or customer is added
• Fixed an issue where the environments page would return an error if no instance had been created
• Creating a static firewall rule now also creates a connection that can be reused