Release Highlights: Automated ticket remediation is now possible with the ability to execute agent procedures during Service Desk workflow. Also, Quotes can now be completely customized.
Enhancements
VSA Integration
- VSA Agent Procedures can now be executed from workflow rules. For example, if VSA monitoring creates a ticket with "Disk space low" in the description, the workflow can automatically execute a VSA agent procedure to clear temp space. Leveraging the power of service desk workflow and agent procedures, the possibilities are unlimited. A record of the agent procedure execution will be recorded via ticket activity notes, and will also be shown in a new ticket audit log. You can also drill into the VSA agent procedure execution log directly from the ticket. A historical log shows a record of all agent procedures that were executed by workflow; this log includes the workflow name, agent procedure name, and ticket number.
Vorex Finance
- Want to get your quotes looking just the way you want them? You now have unparalleled flexibility to do just that. Similar to invoices, quote layouts and formats can now be completely customized leveraging the power and flexibility of the Ad Hoc reporting engine. There is no need to build custom quotes from scratch: the quote templates that were previously available have been reimagined as Ad Hoc templates which can be found under the 'System' folder in Ad Hoc reports. These templates can be used as-is, or they can be copied to the Public Reports folder where they can be customized. Using the Ad Hoc reporting tool you can tailor the quote templates to match your brand by formatting borders, fonts, text & background colors, bold, italic, and more. You can also configure quote templates to show just the data you want your clients to see by adding text and data fields to header, line-item, and footer areas.
Vorex Authanvil(Passly)
- The legacy AuthAnvil(Passly) authentication integration can no longer be activated. In those cases where it has been previously activated, the legacy integration will remain active; however, Kaseya recommends using SAML SSO to integrate with AuthAnvil(Passly).
Vorex Documentation
- The Vorex About page and Release Banner were updated to point to the New Release Notes page.
Vorex Email Engine
- Multiple replies to the same ticket notification will now be grouped in a single Conversation view in Outlook.
Vorex Reports
- Multiple Ad Hoc reporting objects have been refactored resulting in significant performance improvement.
Vorex Service Desk
- Hardware assets can now be filtered by description both on the hardware asset list, and also when assigning an asset to a ticket.
Bug Fixes
Vorex Email Parser
- Added more logic to Email Parser to prevent issues arisen.
Vorex CRM
- Fixed an issue where it was not possible to add m.network as a Domain Name in the CRM Account Domains.
- Fixed an issue where adding a line item and selecting on the "Period" section "Per Day" set the quote to "Quarterly" instead of "Per Day".
- Fixed an issue where the Fax number was not copied when importing accounts to Vorex.
Vorex Finance
- Fixed an issue when the contract had exclusions the time entries were set as zero value items.
- Added inner exception logging to catch errors in the case of Billing Automation failure.
- Fixed an issue where the invoice was generated based on the Original Template instead of the AD-HOC when it was marked as Fully Paid and sent to the customer.
Vorex Integration
- Fixed an issue where the log showed two Target URL records for the same action when alarms/ ticket were created and transferred to BMSi.
Vorex Project Management
- Fixed an issue when Cost Type was not being set when importing the tasks using the excel import template for the project.
Vorex QB Integration
- Fixed the wrong validation message when user was trying to connect to the account with a wrong URL for target server.
- Fixed an issue when Select All did not respect filtered results when exporting data.
Vorex RMM Integrations
- Fixed an issue when the Ticket Status Mapping tab was blank while configuring the Continuum RMM integration.