We are excited to announce our latest updates for SolarWinds Service Desk. This release adds more ways to work with multiple stakeholders in a single field, more flexibility for connecting Service Desk to SolarWinds Observability SaaS and Incident Response, and improvements to Process Integrations. It also includes several smaller updates to everyday workflows, from resolving related tickets to reading portal widget labels.
Work with multiple users in one custom field
Plan Type: All Plans | Status: General Availability
An access request may need to list several people who need access, while a service request may need approval from multiple users. With a User Multi Select custom field, teams can capture everyone in one field instead of adding extra fields or relying on text workarounds. That keeps forms cleaner and captures the information needed to move the request forward.
Teams can use the selected users or groups in supported workflows, approvals, and notifications. They can also filter supported indexes, reports, and dashboards by those selections to see which records are connected to each stakeholder. To learn more, visit Custom Fields.
Connect multiple SolarWinds Observability SaaS instances
Plan Type: All Plans | Status: Labs
Organizations with separate SolarWinds Observability SaaS environments for subsidiaries or business units can connect each one independently. Each connector's field mapping applies to alerts from its own environment, and admins can manage or revoke one connection without affecting the others. Because each connector uses its own org token, the integration no longer depends on one person's account remaining active.
Each connector has its own name, instance URL, requester, token, field mapping, and status. Existing user API token-based connections continue to work through a legacy connector, with their current field mapping preserved. No changes are required to keep those connections working. For more information, see SWO Saas Integration.
Connect multiple Incident Response instances
Plan Type: All Plans | Status: Labs
Organizations with separate Incident Response services can give each service its own connector, so alerts reach the right on-call team.Each connector has its own inbound and outbound configuration, and managing or revoking one connector does not affect the others. When adding an Incident Response action to an automation rule, admins select the connector for the service they want to use. Existing connections continue working through a legacy connector, including the automation rules that use them, with no setup changes. For more information, you can visit Alert Source in Incident Response.
Create and resolve Service Desk incidents from Incident Response
Plan Type: All Plans | Status: GA
Incidents created in Incident Response automatically create matching incidents in Service Desk. Resolving an incident in Incident Response also resolves it in Service Desk, keeping the on-call response in sync and Service Desk as the system of record.For more information, you can visit Create and resolve in Incident Response.
Add meeting links to Microsoft Teams actions
Plan Type: Advanced and Premier | Status: Labs
The Create Scheduled Meeting action now outputs the meeting Join URL, so you can get the Meeting ID with fewer process integration calls and use it for recording, transcript, and attendance actions. Integration listings now show the Teams icon. For more information, you can visit Microsoft Teams Client Integration.
Find and manage Process Integrations more easily
Plan Type: All Plans | Status: GA
A new Status filter lets you quickly find integrations that are enabled or disabled. Custom API has been renamed to Custom HTTP. For more information, you can visit Process Integrations.
Customize backup contents and date ranges
Plan Type: All Plans | Status: GA
If you need incident data for just one year, select that date range instead of handling a backup spanning several years. You can also choose which records to include or split data by year or month. This produces smaller, more manageable files and can reduce memory use. For more information, you can visit Backup.
Quick Wins
Big features aren’t the only thing we’re focused on. This release also includes several smaller, deliberate updates aimed at making the everyday parts of Service Desk feel a little easier. They may not be headline features on their own, but we intentionally included each one because it addresses a specific need. Here’s a quick rundown:
- Portal widget labels can now wrap beyond a single line, with the text aligned alongside the icon, making longer service names easier to read.
- Agents can look up incidents by entering a ticket number in the URL. Existing ID-based URLs continue to work.
- Agents can also choose eligible related records to resolve while resolving a primary incident or service catalog request, even when Resolution is required. This helps keep linked work moving together, while existing resolution and closure validations still apply.
For more detail on any of these, check out the full release notes.
Final Thoughts
We're excited for you to explore these new features. For a centralized guide on how to configure and use everything in this update, please check out the full release notes.
Office Hours Reminder: Do you have more questions about your Service Desk setup? You can join us for any of our upcoming office hours and get all your queries and questions answered.
To utilize office hours, first log into the customer portal. Then, navigate to the product trainers page and schedule time with Jelyn Perez or Rusty Durano where available.
If you have any questions, please leave a comment below. For more updates, visit our What We’re Working On (WWWO) post.
If you have any questions, please leave a comment below. Have a feature request? Upvote or submit your request here.