May 18 Release for SolarWinds®︎ Service Desk: Customized Runbook Fields, Approval Reminder Notifications, and General Release of Broadened Search Scope for Generated Suggested Solutions

Customized Runbook Fields for Greater Accuracy and Efficiency 

We're excited to launch an enhancement to the runbooks feature in Service Desk that helps improve resolution and tracking accuracy by allowing customizable fields to be added during runbook creation. These fields will auto-populate with data from the incident if available. Additionally, the ability to mark fields as mandatory and use them as conditions within the runbook is now available. 

By requiring agents to input critical information before attaching the runbook, this ensures the correct actions are taken for each unique situation. Enhanced automation triggers processes based on these inputs, reducing manual effort and speeding up issue resolution. Furthermore, this availability of custom fields in runbooks enhances audit tracking, promoting greater consistency and accountability. Runbooks are available for customers on the Premier tier. For more information about using customized fields, see Runbooks. 

Example: You have a database server that is not responding, and each database server is unique in the way they need to be troubleshot. To make sure the agent is taking the correct steps, they will be required to input the server name and server IP address when attaching the runbook. With that additional information, the runbook will guide them to fix the issue with the appropriate process for their provided information. 

  

 

Accelerate Issue Resolution with Automated Approval Reminder Notifications 

A major derailer of issue resolution is the delay caused when high-priority requests remain in a pending state due to lack of action. The release of the automatic reminders for approval requests feature in Service Desk helps address this problem.  

Implementing this feature helps ensure timely responses and reduces delays in critical processes by allowing administrators to configure reminder intervals and customize email content. It works to improve efficiency, ensuring that critical tickets are addressed promptly, and supports better service delivery. Additionally, the audit trail for each reminder sent provides transparency and accountability. This feature is available on all pricing tiers. For more information, see Approval Reminders. 

 

 

 

General Release of Broadened Search Scope for Generated Suggested Solutions 

We are thrilled to announce that an enhancement to generative AI features which incorporates knowledge base articles into the suggested solution process is now generally available. Initially released in Labs, this enhancement now offers a powerful upgrade to incident resolution by incorporating knowledge base articles into the suggested solution process, making resolution faster, more accurate, and more efficient. 

Previously, the suggested solutions were based solely on insights from closed tickets, which represented a smaller portion of the available information. With the general release, the system now pulls from a wider array of resources, integrating knowledge base articles which are carefully created and reviewed by IT teams. This means agents gain access to a broader set of high-quality, approved solutions. 

Key details such as titles, descriptions, and public comments from knowledge base articles are now included, alongside links to related tickets and articles. This makes it easier to find the right information quickly, further reducing the time spent searching. At the same time, security and permission levels are maintained, ensuring sensitive data remains protected. 

By combining insights from both closed tickets and knowledge base articles, the AI now provides smarter, more accurate recommendations. This enhancement not only improves the quality of suggested solutions but also empowers agents and users to resolve incidents faster. With quicker access to the right information, users can address issues more efficiently, driving higher satisfaction and better operational performance. 

The feature is now available as part of the standard release, ready for use by Service Desk customers using the Premier tier. For more information, see Suggested solutions and draft responses. 

 

Office Hours Reminder: Do you have more questions about your Service Desk setup or anything regarding Enterprise Service Management (ESM)? You can join us for any of our upcoming office hours and get all your queries and questions answered. View and book your slot using one of the links below:  

 

Read the full release notes here 

If you have any questions, please leave a comment below. 
See what else we’re working on. 
Have a feature request? Upvote or submit your request here. 

  •  Hi  

    I appreciate the detailed and transparent feedback. I had already mentioned that we will support better granularity and more reminder options in the future. I nevertheless asked the question to see if there is anything unique to the way your organization wants to use reminders, that we should take into consideration.

    I of course agree that approval reminders should have been supported from the beginning. Since that wasn’t the case, we prioritized work on this ask, together with the many other customer asks. A primary consideration in deciding to start with the basic global reminder options was time to delivery. We wanted to provide a quick solution that would provide basic reminders support while we continued to work on adding more flexible options. It might seem like similar efforts are involved to deliver full flexibility but that is not the case.

    As to the comment about supporting dark mode (I understand that you were just using an example), the delay in prioritizing the work was a conscious and transparent decision. We explained our rationale on several of our quarterly updates (you’re welcome to join the next one, scheduled for June 11): We felt that while the dark mode ask had many votes, there were other asks higher in urgency and/or impact. FWIW, we’re very close to delivering support for dark mode.

    If you would like to discuss the above or anything else in terms of product requirements or functionality, please let us know and we will be happy to connect.

    Best,
    Daniel

  • I'm a little baffled by the need to provide specific use-cases. I would think it'd be self-evident why I would like to configure different intervals and different notifications on different requests. Frankly, I'm a little frustrated by the need to explain it at all.

    What I would like to do, and what every other decent ITSM system in SolarWinds' price range does, is send reminders every day until the request is approved or rejected. If the approver takes no action within a timeframe that I as the administrator define, which would be 30 days in most cases, then it is closed. However, different requests can have different needs or different degrees of urgency. Thus, some may require more or less aggressive reminder intervals and/or timeframes.

    However, with the way approval reminders are currently implemented in SolarWinds Service Desk, if I want to send a reminder every day, then I can only allow the approver to approve or reject the request for 10 days at the most. But what if the approver is on a two-week vacation? Now they will never get the opportunity to approve it. But if I want to extend the duration during which reminders are sent, the most frequently I can actually send reminders is every other day. 

    Thie way this is handled by other systems is both a very simple method and a very flexible one. I cannot conceive of a reason for the feature to have been implemented in its current state in SolarWinds Service Desk, as it just needlessly turns what should have been a very easy win for your team into something that barely moves the product forward at all. 

    Then again, I guess I should not be surprised, considering that this is the same product that implemented approvals without reminders at all, when I think pretty much every sane human being would agree that automated reminders are a core part of approvals...

    And the fact that approvals sat around for years without reminders being implemented gives me no faith in your claim that "diff" intervals will be implemented in the near future, or ever, for that matter. Why should I believe that this won't be treated the same as something like dark mode? I'm not clamoring for that specific feature, but it is something that should be very easy to develop and implement, yet it has been languishing on your "roadmap" for years.

  • Reminders are sent at intervals relative to the most recent notification sent, or the timestamp of the initial approval request creation.

  • Yes, we do intend to support diff intervals per approval request in the future, as well as full reminder flexibility via automation rules.

    Having written the above, could you please share the use case details behind wanting to use diff intervals per request for your organization? 

THWACK - Symbolize TM, R, and C