I would love to see how you complete e-mail processing of messages sent in for the termination of users from a specific e-mail address with certain criteria in the subject, and the data to be pulled into the catalog item from the body of an e-mail. Wonderful videos by the way!
Thanks for the comment and sorry for the tardyness :) ou thats a good one..maybe another video. That would perhaps be a action to parse the email body and pass them into variables on the item. Have done that a few times via old school inbound action to strip from the email body or take from an attached spreadsheet (another gd vid idea :))..I'm always wary of doing anything like this via email though as relies heavily on the other end upholding their end of the formatting bargin!..that said..doesn't stop being wanting it as a tactical solution. And by tactical..I mean one that never gets looked again and is there until the end of time :) :)
Nice video. I thought this was a pretty straightforward flow when I was given this task. I am updating legacy IAs with new flows. I found your video after not getting a new incident to trigger off my flow. And you did it the same way I did! ahhh what am I missing?! Could a highly customized list of IAs (we have 120 of them) be preventing my incidents? Thanks
A tricky one without seeing..however be aware of the order of things running I guess and output logs where ever you can to see what progress the flows are making. You'll be able to pinpoint the failure point then.
Arghh missed this! sorry. Thats a good question, and one which I may have to play with..but would think you can do this in the flow with copy attachments action and just move if from the inbound email record to the created record. Let me know how you get/got on with that one as its an interesting use case.
This is great! Am I correct that at the moment, you cannot parse the body text to then try and set variables? (eg scan message body for userID to set requestor - as it comes from a generic mailbox)
You can parse the body..without looking (it’s Sunday) you can create an action to parse the body to get at key:value pairs but that requires an email body that’s agreed between the sender and receiver. I.e trouble with emails is they are v flexible unless sending from a “system”.
Hey thanks for the comment. No i don’t im afraid..great suggestion though! Robert Fedoruk may well have done one. That wld possibly be some flow action creation that uses the catalog api. That API is well documented…can think of a view options here and wil absolutely add it to the list..love that challenge!
I sincerely appreciate your quick respond. It makes an enormous difference for end users whose really need help. I have subscribed and also like your channel. Thank you so much.
@@ServiceNerd . I went to sys_properties.list try to find "glide.hub.flow.inbound_email_trigger.show_advanced" to enable it, but I could not find it. We are Rome release. Could you please help? Thank you
I would love to see how you complete e-mail processing of messages sent in for the termination of users from a specific e-mail address with certain criteria in the subject, and the data to be pulled into the catalog item from the body of an e-mail. Wonderful videos by the way!
Thanks for the comment and sorry for the tardyness :) ou thats a good one..maybe another video. That would perhaps be a action to parse the email body and pass them into variables on the item. Have done that a few times via old school inbound action to strip from the email body or take from an attached spreadsheet (another gd vid idea :))..I'm always wary of doing anything like this via email though as relies heavily on the other end upholding their end of the formatting bargin!..that said..doesn't stop being wanting it as a tactical solution. And by tactical..I mean one that never gets looked again and is there until the end of time :) :)
Nice one matey, that’s a real gotcha there 👍🏻 cheers
Ahh too kind & thanks for the comment 😘. Hope all is well and your staying sane! 😀
Im liking this. Thanks.
ServiceNerd merch coming soon! 🤣
Nice video. I thought this was a pretty straightforward flow when I was given this task. I am updating legacy IAs with new flows. I found your video after not getting a new incident to trigger off my flow. And you did it the same way I did! ahhh what am I missing?! Could a highly customized list of IAs (we have 120 of them) be preventing my incidents? Thanks
A tricky one without seeing..however be aware of the order of things running I guess and output logs where ever you can to see what progress the flows are making. You'll be able to pinpoint the failure point then.
any idea on how can i attach the attachments from the email that was sent to the incident that will be created ? for inbound actions
Arghh missed this! sorry. Thats a good question, and one which I may have to play with..but would think you can do this in the flow with copy attachments action and just move if from the inbound email record to the created record. Let me know how you get/got on with that one as its an interesting use case.
Do i need special role on service now? Can't find inboud email option
You will need admin but no special role.
Thank you share the sys property 👍
Awesome!..thanks for the comment.
@@ServiceNerd Agree with @Ahmed Ahmed's comment about the system property. One of those little non-obvious gems out there
This is great!
Am I correct that at the moment, you cannot parse the body text to then try and set variables? (eg scan message body for userID to set requestor - as it comes from a generic mailbox)
Apologies on the delay…thanks for the comment, always appreciated
You can parse the body..without looking (it’s Sunday) you can create an action to parse the body to get at key:value pairs but that requires an email body that’s agreed between the sender and receiver. I.e trouble with emails is they are v flexible unless sending from a “system”.
Hope that makes sense 😀
Hello Sir, Could you please let us know if you have videos on how to create Request and Service Request from Inbound Email using Flow Designer?
Hey thanks for the comment. No i don’t im afraid..great suggestion though! Robert Fedoruk may well have done one. That wld possibly be some flow action creation that uses the catalog api. That API is well documented…can think of a view options here and wil absolutely add it to the list..love that challenge!
I sincerely appreciate your quick respond. It makes an enormous difference for end users whose really need help. I have subscribed and also like your channel. Thank you so much.
Awww thanks..those comments are the best ones 😊 much appreciated
@@ServiceNerd . I went to sys_properties.list try to find "glide.hub.flow.inbound_email_trigger.show_advanced" to enable it, but I could not find it. We are Rome release. Could you please help? Thank you
Hey..you can add the property:
docs.servicenow.com/bundle/rome-servicenow-platform/page/administer/notification/task/deactivate-stop-processing.html