2.2.0 Beta

Release Details

Important Notes

Please read Upgrading to 2.2 from 2.1 for important changes in this release, including necessary template updates.

Notable Changes

• Multi-language support
  • All dynamic content such as names, descriptions and other text fields can now be translated, and the correct version will be shown to the user based on their selected language.
  • Help desk URLs now contain the current language of the page, for example, https://www.supportpal.com/support/en, and this can be changed to show content in another language if it exists and is enabled in the system.
  • The multi-language options only show if you have multiple languages installed and enabled.
• Time tracking plugin - A new dedicated plugin to track time spent by operators has been included in this release. Once the plugin has been activated, a timer and timesheet tab are shown in the ticket view. These can be used to track time as work is being carried out or enter entries at a known date and time, with the option to mark if billable and add a description.
• API Changes:
  • Tickets can now be filtered by organisation ID. A comma delimited string can be entered to filter by multiple organisations.
  • To return results in a given language, add lang as parameter with the locale to the request, for example to return results in French, lang=fr.
  • On storing and updating items, it is possible to add translations where appropriate by including for example name:fr=Bonjour to the request where you want to add a translation for name in the French. By including translations on update, it will remove any translations that you have not included and are currently stored in the system. Please refer to our API documentation to see where this is possible.
• Plugin development - Several new options are now available when developing plugins:
  • Upgrade system - Plugins can now be cleanly upgraded through the system and run specific code that is targeted when upgrading from a given version to the current version. When an update is available and has been uploaded to the file system, the plugin is automatically disabled temporarily until it is updated in the operator panel.
  • Wider route options - Plugins can now register frontend (not requiring authentication to visit) and API routes to increase the coverage of what a plugin can achieve.
  • Permissions system - Plugins can now register their own permissions inside of the core permissions system that can used to limit its functionality based on the role of the operator.
  • Reports - Plugins can now register their own reports that show in the reports area only when the plugin is active.
• The 'from' email command - It is now possible to forward emails to the help desk as an operator as if it was sent directly by a user by prepending the email with a line such as {% from [email protected] %}. It can be used in conjunction with other email commands to apply actions on the ticket that is created.
• New actions and conditions - Several new actions and conditions are available to use in the feedback forms, filters, follow ups, macros & SLA plans. For example, tickets can now be deleted or a macro can be set up to direct email sent to a specific department email to a subdepartment.
• SimpleAuth logout option - SimpleAuth is our single sign-on solution which allows you to authenticate users with just their email address, and now we've added an option to log users out too. The idea being you don't want to keep them authenticated to the help desk when they've logged out the system that SimpleAuth is being used with.
• Performance improvements - There have been several performance improvements made that should mean the system is generally more responsive. Any improvements will vary based on how much data you have, how the system is set up and on your hardware.

Resource Changes

• Language file changes (from 2.1.2)
• Frontend template changes (from 2.1.2)
• Operator template changes (from 2.1.2)

Changelog