Sandbox During migration, users will be temporarily unable to create, recreate, validate, or deploy the sandbox. |
Enhancements
Setup
Space Module Enhancements
Room Booking Settings
Administrators can configure settings to schedule and manage room bookings from the Room Booking tab introduced under Setup > Customization > Space Management:
Configure settings to limit the room booking duration, set the advance booking period, and specify the interval time between bookings.
Select approvers and decide if requesters can book rooms.
Choose to log service requests when a booking is created. You can select the template to be used and choose a time to create the service request.
Space Management Customization Enhancements:
Administrators can configure default values for fields added to campus type, structure type, and floor room types.
Room Booking Section:
Booking section is introduced under the Spaces module. Technicians can create bookings using the booking form and track the details from this section.
The Availability Calendar in the Booking section helps technicians track various bookings visually from a digital calendar.
Room bookings can also be created from the Quick Actions menu.
Space Module Enhancements:
While adding or editing bookings, the Booking section is introduced to collect booking related details.
The Associations tab in space details page now lists associated incident and service requests under individual tables.
The History tab for Rooms & Spaces lists booking history under a sub-tab.
Room Booking Widget:
Administrator can configure a room booking widgets in the Self-Service Portal from Setup > General Settings > Requester Portal > Requester Portal Customization. This widget will allow requesters to create room bookings instantly from the Home page of their Self-Service Portal.
Space Module Enhancements in Requests Module:
In incident requests, technicians can attach and detach room bookings from the right pane of details page.
In service requests, technicians can create, attach, and detach room bookings from the right pane of the details page.
Problem Enhancements
Problem Template:
Problem templates can now be limited to specific technician groups from the Additional Settings tab is introduced in problem templates. This restriction will not apply to SDAdmins.
If no group is selected, the problem template will be accessible to all technician groups.
The accessibility changes are applicable only for newly created problem requests. Existing problems will be accessible to all problem technicians. However, technicians cannot copy existing problems whose template is limited to selected technician groups if they are not a part of the technician groups.
Administrators can select up to 25 technician groups while limiting the problem template accessibility. To increase the limit to 50, customers can contact our support team.
Additional Settings tab will not be available in the default problem template.
Problem Triggers:
Administrators can configure problem trigger criteria based on the Resend notifications for Email responses sub-entity.
Problem Life Cycle:
The $CurrentUser variable is introduced in transition criteria for problem life cycles. Administrators can select this variable to configure problem life cycle transitions based on whether the current logged-in user is assigned as the technician, requester, or in any user lookup additional fields of the problem template.
Problem Users scope is introduced for before transition.
The Problem Owner and Group Members sub-entities under Group scope are now moved to Problem Users scope.
Problem Closure Rules:
Problem Details Page:
Asset icon is displayed for associated assets in the problem details page. Technicians can dissociate assets instantly using the
icon.
The asset icon will not be displayed, and assets will be listed as comma-separated values in the following scenarios:
Problems where the logged in user does not have edit permissions
The logged in user does not have access to the Assets module
Trashed problems
Note: The above changes are now introduced in release details page as well.
The color coding for Status and Priority field values is now displayed on the problem details page in addition to the right pane.
Problem History:
Problem history now records the type of conversation operation performed and its details.
Detailed history will be reflected only on upcoming problem conversation history entries.
Row Color Settings:
Define color codes for the maintenance list view or template view using the % icon. The row color is applied based on Status, Priority, and Category.
UI Enhancements:
The color indicator for Problem Users is changed from purple to dark green across the Problems module for easier recognition.
Generate Solutions via ChatGPT Integration
Deluge Editor Interface Enhancement
The Code Generator button used to generate code for custom functions using ChatGPT is now repositioned above the Deluge editor interface.
Release Template Enhancements
Customize the layout of the Release details page under the Details tab of a Release template.
Add sections and additional fields to different stages of the Release. Changes made in the Release template will be reflected in the Release Details tab.
New closure rule (Details) is introduced for Release custom stages and Closure stage.
Click against an additional field to move it to another section within any of the Release stages.
Click Move Section displayed on the Release template to move a section containing only additional fields to other stages.
Click Preview on the Edit Release Template form to view the layout of the release form.
Orgrole Multiple User Association
You can now assign multiple users to organization roles. To do this, enable Associate Multiple Users in the Add or Edit form for organization role. Note that you cannot associate multiple users with the Reporting Manager and Department Head roles.
View organization roles associated with the user under Setup > Users & Permissions > Users. Click the Gear icon beside the user and select View Org-Role Associations.
Generate custom reports for organization roles by using the Organization Role Associations option under Reports > New Custom Report. Please note that the queries used previously are no longer supported.
API Changes
Orgrole information in entities (such as site, region, etc) will now be stored in an array format instead of an object.
Recommended: Update existing custom scripts and custom functions to the array format.
Existing format: {"site" : {"id" : 9389244773993, "name" : Base Site , "orgroles" : {"udf_ref11" : {"id" : 3439849849898}}}}
New format: {"site" : {"id" : 9389244773993, "name" : Base Site , "orgroles" : {"mref_udf_ref11" : [{"id" : 3439849849898}]}}}
Note: udf_ref11/mref_udf_ref11 refers to orgroles.
Task Schedule End Reminder
Notify the task owner just before the task ends.
You can set up this reminder by adding the Notify Before Schedule End field to the task template.
Set the notification time from the add/edit task form or the task details page.
Notifications are sent only if the task is in the in-progress status.
A new notification template, Notify Before Schedule End is added under Setup > Automation > Notification Rules > Task.
Behaviour Change
The Notify me before schedule start field is renamed as Notify Before Schedule Start.
Request Enhancements
Automate Approval
Configure automatic approvals that are based on users. Currently, automatic approvals are applicable only when the requester is also the approver. Using this feature, you can enable auto approvals for various roles and specific users.
To do this, go to Setup > General Settings > Approval Settings and enable the Automatically approve if approver is option.
You can also use custom settings in approval actions for adding specific roles and users.
The notification rule Notify automated approval actions when the requester is configured as an approver is now modified to Notify user when automated approval criteria are matched. Approvers configured in the approval settings will be notified when their approvals are auto-approved.
Requests
Copy request properties (such as request ID, URL, and meta data) from the request details page. Meta data includes information such as Request ID, Subject, Requester Name, Created Date, and URL.
To do this, click the Copy icon beside Request ID and select the required action.
Request properties are categorized under Request in the Select columns to display section on the custom reports configuration page for request notes.
​Service level agreements (SLAs) can now be displayed in the request list view. To enable this, select SLA in the column chooser.
You can now configure subfields as criteria in Service Level Agreements, Life Cycles, Triggers, Trigger Sub-entities, Abort Timer under Custom Actions, Custom Menus, Survey Settings, and Survey Rules. Fields that support subfields are listed below:
Group | Category | Urgency |
Subcategory | Template | Impact |
Item | Level | Mode |
Service Category | Priority | Request Type |
Department | CIs | Status |
Life Cycle | Workflow | Site |
Custom Script for Releases
Use Custom Scripts to dynamically modify the release form based on user input.
A collection of sample custom scripts for release forms can be imported.
Form Rules enhancement
Use Form Rules to show or hide custom widgets in the right pane of a release add/edit form.Zoho Flow Action Integration
Use Zoho Flow actions, an easy to use, no code solution, to extend the capabilities of triggers and workflows in ServiceDesk Plus Cloud to perform various actions in other applications.
Custom Script for Problems
Use Custom Scripts to dynamically modify the problem form based on user input.
A collection of sample custom scripts for problem forms can be imported.
Form Rules enhancement
Use Form Rules to show or hide custom widgets in the right pane of a problem add/edit form.
Behaviour Changes
The Cancellation Requested field is removed from the Business Rules criteria.
Issue Fix
Timers that match the abort criteria are now associated with the request, change, or problem and aborted. These operations are recorded in history.
Note : All upgrades and feature releases, will be in-service and there won't be any downtime or service interruption.