Release Notes 2.02

Selecting Available Models in Your OpenAI Integration When Using OpenAI Bot Block 

Now, when you use the Open AI bot block in Bots, you have the option to select from the models available in your OpenAI integration. If your OpenAI integration supports the GPT-4 model, then you can also select the GPT-4 model.

If we cannot retrieve the available GPT model options from your OpenAI integration or if you haven't connected your OpenAI integration to MSPbots yet, there will be no model selection.

If you had previously configured the model for the Open AI bot block as GPT-3.5-turbo, then by default your GPT model will still be GPT-3.5-turbo.

In summary, you can choose the most suitable model based on your specific needs to enhance your personalized experience with Bots. MSPbots is always striving to provide multiple options in order to better meet your requirements.

Related article: OpenAI Ticket Sentiment Analysis Bot for ConnectWise Manage

Newly Added Role - Attendance Only 

Now, you can create default Attendance Only roles with different asset scopes for the Attendance Only menu scope in Role Management.

When you create an Attendance Only role and toggle the Attendance Only switch on:

• The menu scope will automatically be filled in as "Attendance Only" and cannot be modified. 
• In the asset scope, the assets belonging to attendance will be automatically added, and you only need to adjust the asset scope according to your actual needs.

The "Attendance Only" switch is similar to the "Dashboard Only" switch, and these two switches are mutually exclusive, meaning you can only select one at a time or not select either one. You can edit the "Dashboard Only" and "Attendance Only" switches when creating a new role, but they are disabled when editing existing roles.

By assigning different asset scopes to the "Attendance Only" role, you can precisely control the assets that each user can access based on their needs and permission levels. This ensures that each user can only view and handle attendance assets related to their work.

In summary, the "Attendance Only" feature provides you with greater flexibility, simplified management, improved security, and quick setup, ensuring that only authorized users can access attendance-related assets.

Related article: Role Management in MSPbots

Using Onsite as a Work Attendance Status to Enhance Accuracy in Utilization Rate Calculation

Now we consider ONSITE as a working status, similar to "in", so when you are working on-site, your attendance time will be counted as your working hours.

This change is applied to Teams messages, Attendance board buttons, and utilization calculation. This means that any messages or pages related to Attendance consider ONSITE as a working status, enhancing the accuracy of utilization calculation.

Additionally, your ONSITE status and duration are displayed on your personal card in the Attendance app, allowing other team members to have a clear understanding of your working status.

When you switch your Attendance status to ONSITE, you can only select lunch, break or out as the next attendance status. This prevents accidental switching to other incorrect attendance statuses.

Related article: Attendance Manager Dashboards

New Field in Advanced Priority Rules for NextTicket for ConnectWise Manage - Company Team Role

You can now select the newly added field in the advanced priority rules of NextTicket for ConnectWise Manage - Company Team Role. This new field can be found in the "Next Ticket Requestor" category.

This field is an option in the ConnectWise app and it has been added to retrieve the values of this option from the ConnectWise app.

This allows you to select values from a dropdown list and configure advanced rules specific to this field, helping you filter out top-priority tickets.

Related article: How to Create an Advanced Rule for NextTicket Manager

New Field in Advanced Priority Rules for NextTicket for Halo - Top Level

You can now select the newly added field in the advanced priority rules of NextTicket for Halo - Top Level. This new field can be found in the "Customer" category.

This field is a default field in the Halo app. The reason for adding this field is to fetch top levels from Halo so that you can select one or more top levels from the dropdown list to configure advanced rules related to this field and filter out tickets with your top priority.

External KB: How to Create an Advanced Rule for NextTicket Manager