Hey all,
First time posting here on the forums but I've used you all many times to create wonderful things. A few years back I wrote a quick project to make searching much easier in our environment and though it hasn't been updated in ages and I've learned a ton since then, it still functions like a well oiled machine :)
In any event let me know if you have any thoughts or questions and I'll be happy to help and before we get into how, here are a few examples of what it looks like:
and after you search this is what the results look like
Instructions:
I've included the workflow package in this article, however there are a few items you need to change after loading it.
1) Change your properties to include your email domain name and an abbreviation for it. I did this so that each item in the search results took up slightly less space in the report. You will also need to input your SQL SERVER NAME into the SqlConnectionString Property see the red in the picture below.
2) This report includes links to the tickets, In the picture below is the decision model for each return on the report to create the link to open the ticket. For Non-Incidents, the "user has permission Rule" works perfectly as it checks to verify the logged on user has permission to the page, if not then goes to the simple link. If the Process is an incident however, the same permission rule didn't seem to function as well so I used a workaround. In our environment, only those within the CARB\ois.OIS.SACHQ OU in Active Directory have access to the advanced forms, so I was able to have the project check that security group first and then create the appropriate link. If your permissions in your environment are setup perhaps a little cleaner you may have an easier way of doing this. If you need help don't hesitate to respond to this link, i'll do my best to get back to you.