MitchKiah · Enterprise Applications Manager · ✭✭✭✭✭

@"mulambo" You may have the best luck using Zapier rather than coding something from scratch. It's a low-code automation platform that has limited integration with SWSD. It would work for your case because it can trigger off of newly created Incidents in SWSD. This should be much simpler/time effective than coding it…

@"Stonelaughter" sent!

Hello! This is something I currently have working in our instance using the Process Integration action. If you can provide the JSON you're sending and a screenshot of the endpoint/headers I can take a look at why it's returning an error.

Every user has their own "group" that only they are part of. For some reason the API uses the group ID for GET requests on assignee. My guess is to make it easier to also search for Groups that can be assignees

It's not the best situation, but yeah that's how people discover them. It's been a common ask for improved API documentation so hopefully this is something that they can improve in the future. If you get stuck on any in particular, people in the forum are usually quick to help so let us know!

When you look at the URL, everything after the "?" and between the "&" symbols are parameters. Using the URL below as an example: <a…

They aren't documented currently. The best way to discover them is to build the filter using the website, and then inspect the URL afterwards to discover the parameters.

Hi kfix! I'd recommend reaching out to your support rep and asking them for a hand. If they aren't able to offer a solution within your timeframe though, I'd be willing to take a look after hours. Feel free to click on my profile and send me a private message if you need a hand:

I'm saying the service requests that were created from the catalog items, before 4/3, already have the request_variables array present. Happy to jump on a teams call and do a screen share if you need examples!

The request_variables array should still be there for service requests created prior to 4/3, just not new service requests. To keep backward compatibility for v2.1 of the API it would be better to keep all of the new fields in the custom fields variables array and add back a copy of them to the request_variables array.…

Hello! I'm not sure the Orion integration will do what you want. It looks like an Orion alert can generate an SWSD incident, but maybe not the other way around: From the documentation: The integration between Orion and SWSD is composed of two parts. Each part is mutually exclusive of the other. Although they can co-exist…

It looks like this is only happening in Service Requests and not standard incidents

This is a big issue when "required" fields are supposed to be hidden, since you can't submit without filling them out.

Update: Form Logic doesn't work in "Convert to Service Request" prompt The "Change Type" controls whether one of the three fields in the below form should be shown. This is a simple example form, but in this screenshot, we should only see the "Restore Access" text field.

RESOLVED: API Bug: Custom Fields now show up twice in the "custom_fields_values" JSON object The "custom_fields_values" array returns two of each custom_fields. So if your form has two custom fields, "Summary" and "Detailed Description", the returned json will look like: { ... "custom_fields_values": [{ "id": 123456789,…

Hi Joey, I appreciate your fast response on here. If there are any other known issues that customers are reporting in, it would be much appreciated if you or another rep could comment or link to them here to raise awareness. Thank you!

It's not too bad to update your code to support the custom fields since they're both formatted as Lists of Dictionaries. Just make sure to keep code in to support the "request_variables" as older tickets will still have these values. Another thing to note is that some of the field values from the API are in different…

Update: API Mapping of Request Variables is now broken. The "request_variables" array received from making a GET request on https://api.samanage.com/incidents.json?layout=long for Service Requests is now an empty array. All of the previous "request_variables" are now listed under the "custom_field_values" array. This is…

If you create a new "Incident" you can think of those as just "I have an issue with ____" requests. For the forms you created, you can Request the form by going to the Service Catalog. For Agents, the service catalog is available in the left side menu, and once you click on the form you want, you can Request it in the top…

I got an email yesterday from technical support that this issue was resolved.

Hi Kara, myself and at least a couple other people have reported the same issue to the support team. They should be aware of the issue, but it's probably best to open a support ticket so they know how widespread the issue is, and so you can get updates for a resolution.

The Process Integration authorization options are limited and don't support OAUTH or even json web tokens (aside from SWSD ones). I have an open feature request to improve this to support custom headers/bearer auth…

For that use case, you'll want to use something to fetch the file from the URL and save it to the local machine temporarily, then upload it as an attachment as the second step.

Hello! You'll want to create the incident (or comment) first, and then add the attachment to the existing record. Using ICJN's answer from this simlar forum post on how to do this in Powershell, the way to do it with CURL would be like this: Attach to an incident: curl -H 'X-Samanage-Authorization: Bearer TOKEN' -F…

Hello! Something similar was a feature they had listed in their "What We're Working On" section. It was supposed to be a scheduled CSV export, in the same way that you can schedule PDF reports from the Analytics section today. The idea was that you could create a filtered view, in your case a filter searching for incidents…

I had the same question. The answer I got was that there isn't a way to store the response from a GET request. I think you're correct that it's more just to support webhooks or outlier 3rd party APIs. I've requested the feature directly from our CSM in the past, but if you add it to the Feature Requests section in the…

As far as I can see there's no way to filter on the department description from the users endpoint. Filtering on sites and departments description isn't working for me either. So, you would need get a list of all the departments, then loop through all of them to find any that have that matching description, and then search…

Unfortunately, the email variables are not well documented. The variable list you found in the Setup > Service Desk > Notifications is the best reference we have. This is the email documentation as it is: Email Customization for Notifications (solarwinds.com) Notification Settings (solarwinds.com) A helpful related forum…

Additionally, if you just aren't receiving a particular type of email notification, you may want to check the settings in Setup > Service Desk > Notifications and Setup > Users & Groups > Groups > Group Name to make sure someone didn't accidentally disable email notifications

Hi @"amtiminie", I would recommend checking the email logs in Setup > Account > Email Logs to see if SolarWinds is having trouble delivering email to you. That should help you get a good idea of what might be happening. If you don't see anything there, or don't see anything you can fix on your own, you should reach out to…