Release Notes 2.26 – MSPbots.ai

Release date - January 6, 2025

What's in this release:

View Detailed Error Information for Failed Schedules in Schedules
Option to hide the footer for bot messages sent via Slack
View the Number of Items in the Dataset
View Original Name of Renamed Dataset and Improved Clone Functionality in the New Widget Builder Mode
Optimized Data Range Slicer Options and Slicer Settings in Scheduled Reports
Deprecation of the Old Client Mapping
Verification Code for Email Registration
Peer Group Question Added to the Survey Form
Onboarding Welcome App Available
Multiple Filters Logic in Next Ticket

View Detailed Error Information for Failed Schedules in Schedules

Now, when you view the Sent History in the Schedules, if there are any failed schedules, you can check the detailed error information for the failed schedules here.

When you click the schedule name, you can view the details of the schedule settings and the sending history, including the successful and failed sending history, as well as detailed error information.

Required permissions

Only admins can see the Schedules entrance and access the Schedules page.

Related article

How to Manage Schedules

Option to hide the footer for bot messages sent via Slack

You can now hide the footer in bot messages sent to Slack Chat and the Slack Channel. To do this, select the Hide the message footer option when configuring the bot alert.

Required permissions

Only admins can create and modify bots and bot alerts.

Related article
How to Send Messages to Slack Chat

Demo
Enable hide footer for bot messages in Slack

View the Number of Items in the Dataset

Now, you can check how many items are in the current dataset on the Data tab of the dataset, such as Total: 677 rows. This way, you can get more details about the current dataset on the page and easily filter the data.

Required permissions

MSPbots users

Related articles

View Original Name of Renamed Dataset and Improved Clone Functionality in the New Widget Builder Mode

View Original Name of Renamed Dataset

When you edit the widget using the new widget builder mode, hovering over the dataset displays the original name of the dataset.
If you have renamed the dataset, hovering over it displays both the original name and the name you renamed it to.

Improved Clone Functionality

Now you can click the options below to clone the widget to where you need it.
- Clone to "My Widgets"
- Clone to Existing Dashboard
- Clone to New Dashboard

Required permissions

Only admins can edit widgets.

Related articles

Optimized Data Range Slicer Options and Slicer Settings in Scheduled Reports

Optimized Data Range Slicer Options

To enhance your experience with the Data Range slicer, we have optimized its options. The available selections now include:

Today
Yesterday
Last 7/30/90/120 Days
Last 7/30/90/120
Business Days
Month-to-Date
Week-to-Date
Last Week
This Month
Last Month
Last 12 Months
This Quarter
Last QuarterThis Year
Last Year
Custom Range
Specific years (e.g., 2025, 2024)

Enhanced Slicer Settings in Scheduled Reports

We have optimized the setting of slicers in Scheduled Report. When editing a scheduled report in the dashboard or report, if it contains a slicer (excluding the company slicer), the "Save Slicer" switch will appear.
- Turning on the Save Slicer switch allows users receiving the scheduled report to use the slicer to filter data. For example, the data range slicer.
  - The slicer value you set will automatically display in the dashboard or report, and the dashboard or report will display the data filtered by this slicer.
  - When the scheduled report is sent, the slicer value you set in the scheduled report will be displayed by default, and the dashboard or report will display the data filtered by this slicer.
- If the Save Slicer switch is turned off, users receiving the scheduled report will not be able to use the slicer.

Required permissions

Only admins can edit the Data Range slicer and scheduled reports.

Related articles

Deprecation of the Old Client Mapping

The new version of Client Mapping, capable of reading names across integrations and automatically generating mappings, was released on January 16, 2025. The data from the old version has been successfully migrated to the new version.

Key Changes:

Deprecation of the Old Client Mapping: The old version is now deprecated and has been switched to read-only mode. A transition period is available for users to migrate their assets. Dashboards and Slicers associated with the old version will continue to operate until further notice.
Data Synchronization: Updates you make to names in the new version will automatically sync to the old version and be reflected in the old assets.

Migration Report

You can check the migration report and handle any failures in the Migration Report.

Successfully migrated names from the old version will be available in the new version and in assets built for the new version.
Names that failed to migrate can be reviewed and handled manually in the migration report.

Access the Old Client Mapping

If you want to access the Old Client Mapping, you can find the entry in the new version of Client Mapping.

Open Old Version.jpg

Required permissions

Only admins can edit the client mapping.

Related articles

Verification code for email registration

An additional step during MSPbots registration has been rolled out to enhance security. After registration, a verification code will be sent to the user's registered email address along with instructions on using the code.

Below is a sample verification email.

Entering the correct code completes the registration. If the code is incorrect, the system detects the invalid input and asks the user to re-enter the code or request a new one.

The verification code is valid for 10 minutes only but will be available for resending after one (1) minute.

Required permission

All new users who sign up with MSPbots will get the verification email.

Peer group question added to the Survey Form

Users can now indicate their peer groups when answering the Survey Form. This information will add their groups to the Peer Groups list in the MSPbots app.

This information is optional, however, you may still be prompted to provide this info. You can ignore this question if you are not a peer group member.

Required permission

All new users who sign up with MSPbots will see the questions in the Survey Form.

Onboarding Welcome App Available

The Get Started form is replaced by the Onboarding Welcome App that guides users through an 8-step process to ensure your configurations are complete and the MSPbots app will work. The homepage has an overview of where you are in the onboarding process.

The Onboarding Welcome App is accessible from Settings by users with the admin role.

Required permission

All users who signed up with MSPbots can access the Onboarding Welcome app. However, only those with the admin role in MSPbots can set and modify the configurations.

Related article

The MSPbots Onboarding Welcome App

Multiple filters logic in Next Ticket

Starting Release 2.26, Next Ticket's Multiple Filter Logic can be configured to use either the default Round Robin method or the new Most Points option.

Selecting Round Robin will rotate ticket prioritization among the assigned filters (from top to bottom) and return the highest priority ticket based on the active filter. Most Points, on the other hand, evaluates all tickets across all filters and returns the ticket with the most points. Because this method runs tickets through all active filters, it will make more API calls to the user's PSA and significantly increase the time required for prioritizing tickets.

Users with the admin role can modify this setting.

Required Permission

Only admins can modify the Multiple Filters Logic and other Next Ticket settings.

Related article

Next Ticket for Connectise Manage