The most recent content from our members.
Hi, I have been given a new role, and part of that is doing more automation within Solarwinds. I have a very crude knowledge of RegEx and have gotten some automations working, but I am wondering if anyone has any good learning modules for RegEx in general, and more specifically for how Solarwinds handles it. I want to make…
For ESM, We are interested in separating providers for the benefits that the separate databases provide, but we are not really interested in complicating the user experience to report an issue. The general idea is: A user gets a fairly generic menu of things to report, for instance “IT Service Issue,” “IT Development…
I'm trying to devise a way to trigger a process integration when a new approved solution is created within the service desk. I've accomplished this on changes by having the process integration fire off in the change process in our change catalog items, but I don't see a way to have a process integration trigger…
When creating an automated rule, it's not possible to send an email to a commenter. This is necessary, for example, when someone adds a comment to a closed or resolved ticket and needs to be informed that their comment may remain unread.
We have catalogue items that can cover multiple categories depending on how our Users log the request. I attempted to get Automation rules to automatically change the default category depending on certain fields but since the fields only exist in a catalogue item and not a Incident or a form, They were inaccessible. I've…
I've done some digging in the forum and I've seen a few folks prompting the ability to create/update/etc tasks via automation rules. This would be super nifty to be able to do, unless there is something I'm missing. Still new to the platform, so I wouldn't be surprised if I've skimmed over something.
There is currently a hard limitation that prevents automation rules from using custom date fields as conditions. It would be great if SWSD could support using a custom date field as part of its conditions.
This could be a little risky, but it would be nice to allow the merge function in automation rule actions.
When an end user adds comments to a closed ticket which it reopens the ticket. They can setup an automation rule to have the end user open a new ticket. Is there a way to disable the comment section so the end user is not able to add comments to a close ticket? They are aware they can choose to toggle off the "reopen…
Allow automation rules to run only when a ticket is resolved by an agent or requester. Or allow to run based on Resolved by or Resolution code fields.
It looks like you're new here. Sign in or register to get started.