NetSPI Resolve - End User Experience

Hey, Cody and Ryan, I just wanted to put together a video to show you the front end of what Trey could look like for your end users.

I think, you know, it's really important to highlight that for your end users, it's going to be a much more seamless type of experience.

So, again, as we talked about before, within the net spy application there will, there could be a tab that is specifically for integrations.

I think you already have that today since you already have the Jira integration built out. So, you know, we can essentially sit alongside the Jira integration that you've already built.

You know, you can have your front end engineering team design it to look however you need, but the idea is that it'll look really embedded within your application, and you can white label and stylize it however you'd like.

Now, as we mentioned before you know, you could populate this with a GraphQL call, and you'll see here that the Service Now solution that you've been working on can be displayed.

Here, you know, they might see a connect button. Your user in this case has already connected. So here you're gonna see potentially the ability to enable an integration and have the workflows start running.

The ability to edit or delete, that's something that you can certainly configure and build into your cards. Once a user clicks connect or edit, I'm just gonna expand this page here.

They might see a modal. You can also have it as an eye frame as well within your application. That's up to you.

But the idea is that they would provide their ServiceNow credentials. I already have my ServiceNow credentials made here. And then they can do the other configuration points that are required for the integration to run.

So that can mean field mappings where your mapping one property from, resolve to another property in ServiceNow and identify what that looks like per customer.

And again, you know, your, your end user would actually be doing this as well as the statuses. So here you're gonna see that we're mapping Resolve fields and statuses.

So you can have these pre-populated or you know, in this case, what you can do is also populate these dropdowns dynamically.

So, you know, you're actually pulling in states or whatever fields via an API called directly from the ServiceNow environment. So here, what I might say is that user resolved that status and resolve is actually equivalent to closed in my Service Now's environment.

Just going through the screens here, you'll see That these, these screens all configurable within a drag and drop type of environment.

We also support the ability to write custom JavaScript within the Solution Wizard as well, so that you can customize this.

Another point I will mention here is that your users likely wouldn't see this resolve configuration where they might provide host name or API key.

This can be data that are, is imported into tray so that your users don't have to see this. And, you know, within your application, it provides a more seamless experience as well.

So really in this case, you know, they might see two screens, or again, as many as they, it, it is required to set up that integration.

And here you can provide, you know, details about how to register a web hook within ServiceNow. Even provide the link to get there, they can copy this url.

And again, I wanna point out that this can all be white labeled. So this can say, you know, sub domain, net spy dot integration hook, as well as the URL here for the web hook trigger can also be white labeled to integration hook so that it doesn't have to say Tray app.io.

So again, as your user completes these very you know, user-friendly experience and, and Wizard here this can either update the existing instance or create a new solution instance if there one hasn't already been created.

So you can create solutions for Azure, DevOps other ticketing systems and really expand on your integrations and that exist within your marketplace.

You know, I think one thing to point out here is that with Trey, you're building these integrations in a low code, drag and drop environment.

You know, one of the things you mentioned here was being able to you know, configure these very easily. And I think you guys did a great job in the POC with that.

You know, the, the importing of the API definitions for connectors that aren't in our library. I did wanna touch on the ability to import the curl requests in here, and Trey would essentially interpret them into the HTTP client.

So that could be something that is used to easily import the API definitions. But as mentioned you know, what Trey would do is build a net spy connector.

So in within our connector library and Under our services list there would be a connector that would live called Net Spy Resolve, or whatever you'd like to call it with those five operations.

And, you know, something to point out here is with us building the connector it's, it's gonna be not not only available to you to easily build out integrations, but also it's gonna be available to our other customers if you'd like it to be.

So that if you do have clients that are using Resolve and would like to further extend their automations and create their own automations this connector would essentially live within our list.

You know, also the other benefit of that is that if there's any sort of dropdowns or DDLs that you'd like your users to be able to select from you know, maybe pull in directly the statuses from your the authenticated environments.

If there's logic or, you know, ease of use for that connector that you'd like for us to incorporate, that's certainly something that our PS team can do as we build out that connector.

So you know, long term that's gonna be very easy for your end users to be able to build automations within Tray if they have a tray environment as well.

So hopefully that covers the, the ease of use in terms of the end user experience. And if you do have any questions, please feel free to email me@eliseattray.io.