Awhile back I announced that there would be a “resource kit” for Service Manager which would include a bunch of things that we already had put out on the blogs like…
and some new things…
We’ve decided that instead of packaging up all of this stuff as one downloadable “resource kit” package we would create a Tools/Downloads page on TechNet. Then we can add to it whenever we want and point to all kinds of locations like CodePlex, third party software vendors, blogs with tools attached, and microsoft.com/downloads to get releases from Microsoft. It will be one convenient place to get all the tools and solutions available for Service Manager and we can update it continuously without the overhead of a release.
While it will take just a couple more weeks to set up the Tools page on TechNet….
I’m pleased today to announce the release to microsoft.com/downloads the Exchange Connector and the Send Email solution! You can get it from here:
Note: allow up to 30 minutes from the posting of this blog post for worldwide replication on the microsoft.com/downloads site.
It’s taken awhile to build these solutions because I had them thoroughly tested by about 15-20 customers. These customers found bugs and submitted feature requests that I went ahead and implemented to expand the scope of the Exchange connector to include a lot of additional capabilities beyond the scope defined originally. The Exchange Connector now features the following capabilities:
The Send Email solution is a separate solution that I’ve packaged with the Exchange Connector for convenience, but it can be deployed with or without the Exchange connector technically. When you have both of them deployed and configured correctly you can enable the end-to-end lifecycle for emails around incident management. For example, an analyst can be looking at a ticket and click a ‘Send Email’ task to request additional information from the affected user. When the user replies to that email with the additional information, the incident is automatically updated.
Lastly a big, huge thank you to all the community testers that made this possible. You know who you are. I really appreciate the effort you put in to test these solutions, provide feedback, and report bugs! Thank You!
Update: Chris Ross put together a nice demo video of installing, configuring, and testing the Exchange connector . Thanks Chris!
Did you modify the SendEmail MP XML to support the new list item?
I wasn't sure if I needed to copy and paste all the xml code again. do I need to add the xml code for each list item?
***Do I add this again?
** Do I need to add this at the beginning as well?
at the begining and Outer <Expression><Or>…. </Or></Expression?
I am going to add some additional details. First I have no problems with just one List type message. I am confused on the directions of how to add a second. Do I go through each of the steps again. Here is what I do: I create a list. Then create the template. Then I create the workflow item. After its all done, I export the MP. Then do I edit it just the same exact way that the directions say? so I simply copy and paste the same code from the previous message list I created?
I notice when I export that it seems to lose the previous xml code I copied previously. Does this info get lost during the export? I also notice when I import the code back in, one of my rules of the workflow is missing. I had 2 rules: 1. send when message type is "equal" to sendmail. 2.when message type is "not empty". the second rule doesn't show anymore. Is this something others are seeing?
Yes, that's the idea. Add a new list item & notification template and then follow the instructions to add another rule.
I had another customer tell me about what appears to be the same issue - the XML gets modified on export. So - you might need to keep your original around and use that as the starting point rather than an export.
Thanks we got both of our Work flows working properly now.
Would you be able to ZIP and email me a copy of the Exchange Connector version 2.0 that you customized to make work with Office 365?
SCSM 2012 and EC 3.0 would also be a solution but connector 3.0 is not readily available, so I'd be happy to work with modified EC2.0 that reads credentials from registry.
Email address: colmcorcoran @ gmail dot com