Send Email to Affected User RRS feed

  • General discussion

  • So we all know of the SendEmail connector that is out there that allows us to send an email to the affected user of a ticket.  But we also know that this solution is something that is very "ugly" and lacks a lot of functionality, especially the ability to send multiple messages.  We kind of took this theory and ran with it by importing the SendEmail connectors but left the workflows disabled.  Then we built a notification that would fire anytime an E-mail Sent action would be created in the Action log.  This allows you to send multiple messages from a ticket without needing to clear out the data properties.  

    Now as much as this issue is discussed by the community, it kind of throws a flag to me as to why this hasn't been suggested more often.  Maybe my search skills are that poor or is it just one of those things that slipped through without being mentioned or is there some type of catch that we are not thinking of?

    Wednesday, July 17, 2013 7:05 PM

All replies

  • Hello,

    you may back on System Center Orchestrator for more individual workflows and connectors

    Send mail to affected User.JPG



    www.sc-orchestrator.eu , Blog sc-orchestrator.eu

    Thursday, July 18, 2013 8:32 AM
  • Ryon,

    I don't know if I'm missing something but the SendMail functionality does allow you send send multiple emails from a single ticket out of the box providing you following the instructions? I don't see why you would need to disable the standard workflows?

    Thursday, July 18, 2013 8:32 AM
  • Hey

    If you are not happy you can extend the SendMail solution for your needs. The source code is available here:


    We have created our own SendMail tool and done some extensions for our customers. Check this post to see what's possible.



    Marcel Zehner // Blog --> http://marcelzehner.ch // Twitter --> @marcelzehner // Business --> http://www.itnetx.ch

    Thursday, July 18, 2013 11:39 AM
  • Its not that we are not happy with anything.  Just kind of surprising to me that the path we took to achieve this connector is not already listed out there.  That said, sparked my mind about ok maybe there is something I am missing here and just have not found it. 

    We were using Orchestrator to help out but our Helpdesk ended up using the feature so much that monitor's just weren't an option so we reverted to this idea until we have time to build something more solid.   We have used Orchestrator to build a notification system for the Problem class so we are thinking of just adjusting for incidents.
    Thursday, July 18, 2013 12:44 PM