Launch a

[@robertthedukefedoruk5607]

If you're working with ServiceNow Catalog Items you should watch this next. All about ServiceNow Variables.: kzbin.info/www/bejne/pJyccmmqd7apiaM Want more ServiceNow deep dives? Here's my ServiceNow Toolbox playlist: kzbin.info/aero/PLkQDoKoP0MAP0gwpL2OEMZJzmm7t872th

[@FransOmmen]

Very very very nice! I was looking for a solution for a while now... You solved it! I don't know why ServiceNow did not implement this if they want us to move from Flow Editor to Flow Designer... I would be interested in cracking another issue. How to create a Flow Designer flow which can be used form a Catalog Items as a Process Engine and use variables from the RITM in the flow

[@robertthedukefedoruk5607]

Try this: kzbin.info/www/bejne/qYPXn4ihi5WIiJY

[@ajconnolly4338]

Hi Robert does this still work in Washington? I'm having issues and I have ran into the issue the action is not returning any email variables I'm getting the following message in the logs *** Script: Cannot read property "1" from null am i missing some configuration on the action?

[@yasdnil01]

Seesm like there was an update to the action and it calls for a Default value, a Name and a Value? Why Value? I'm trying to pull the value from the email2. And as a Function/Utility why is there the option to add multiple key value pairs for a singel varible you are trying to set?

[@misterspiffy2008]

Thanks Robert for this -- very helpful, although I am still running into an issue with resolving the name-value pairs. The HTML in the received email contains an HTML table with two columns, name on the left and value on the right. The parser is unable to pull data from it. Have you heard of this issue?

[@robertthedukefedoruk5607]

I don't believe the parser is built to do that. It interprets name value pairs as being strings on separate lines.. Name1:Value1 Name2:Value2 Its not parsing through HTML.

[@saivineeth9360]

Perfect Content, thank you..! Robert Small question here can we do the same for creating incident record through the inbound mail

[@robertthedukefedoruk5607]

My pleasure. LinkedIn shares really spread the word!

[@robertthedukefedoruk5607]

Yes. Trigger is the same (inbound email) and use the same email parser to get the name:value pairs. From there you can do WHATEVER YOU WANT in the flow. The custom Flow Action just gives you a way to extract "fields" from the email.

[@tommylmiles]

getting an error when trying to parse the email - Script: Cannot convert null to an object. any idea what i might be doing wrong

[@petr5363]

Is there way to change regex to create value (for name:value pairs) of email which is stored after : within characters?

[@petr5363]

Input data that I have in body_text field is in this format From: FirstName FirstName

[@khushbookabra1354]

Hello Robert, I am facing issue to populate the reference field and Date/Time field through Email variable (Name/Value). Any help would be appreciated!

[@robertthedukefedoruk5607]

You haven't described the problem. I suspect its this. The DateTime is probably being picky about format. The Reference field is looking for a sys_id, which the email isn't sending, so you may have to do a lookup based on the name that hte email sends you in order to find the sys_id.

[@toprow32]

This is great! But what if we want to add the attachment from the email to the RITM it creates?

[@robertthedukefedoruk5607]

Should happen by default.

[@toprow32]

@@robertthedukefedoruk5607 Hmmm I've followed each step precisely but can't get the attachment on the email to show up on the request

[@toprow32]

@@robertthedukefedoruk5607 hmm I've followed each step precisely but the attachment on the email still isn't showing on the request/RITM it's creating

[@robertthedukefedoruk5607]

@@toprow32 - ok, did some R&D. It looks like there's a flow action called "Move Email Attachments to Record" This will ask you for an email record (which should be your trigger) and a destination record (which will be the RITM you create). This must be below whatever Create Record mechanism creates the RITM. I very sincerely appreciate the question, since I was able to learn something today.

[@toprow32]

@@robertthedukefedoruk5607 Thank you so much!! This solves everything now :D

[@PeterQuill-oi8lu]

Thanks for this guide Robert! it was extremely easy to follow. Just a heads up that the "Parse Email Flow Action v2.2" seems to not work with Tokyo (and assuming San Diego as well). The name/value pairs show up in the "Email Variables" in the Parse Email Body Text global action but they do not populate in the Submit Catalog Item Request action.

[@robertthedukefedoruk5607]

Hey Peter, I just retested and it works fine on my Tokyo instance, though I might not be using Parse Email Flow Action v2.2. Maybe I'm using a prior version?

[@PeterQuill-oi8lu]

Thanks for confirming, Robert! I did use Parse Email Flow Action v2.2 on flows that were created in Rome, which still worked in Tokyo. But i believe when i created net-new flows in Tokyo (on v2.2) they were not passing the name:value variables. The fix that we did was to create separate output variables for each variable we were trying to pass. It's a bit tedious because we now need to create a separate parse email action per inbound e-mail flow. But i thought you might want to know. I might have to see if the previous version of the action works on Tokyo. Cheers, Pete

[@robertthedukefedoruk5607]

@@PeterQuill-oi8lu - sent a screenshot of this convo to the author of the custom action. He's going to take a look at it.

[@amylind1152]

@@robertthedukefedoruk5607 - I've scoured the web for a solution to this issue. Any updates? I'm working with v2.2 on Utah.

[@tommylmiles]

any examples of how you got this to work ?? pls

[@sachingk7724]

Upload more videos on catalog Robert😊

[@robertthedukefedoruk5607]

Sure. What other topics do you think I should cover? And the more this content is shared, the more content I'm going to make. If you could take my LinkedIn account and the #ServiceNow hashtag, that would help a TON

[@SiddhiSukhatankar]

Is it possible to bring the Choice fields through the 'Parse email Action' in the flow designer? .As when we go to add the data pill it shows that 'Name:Value Pair is not allowed here'. Can you help me out with it Thanks!

[@robertthedukefedoruk5607]

Choice fields really are just strings at some level, so as long as the email contains the VALUE and no the LABEL of the choice you should be ok.

[@kingjames7basketfantasy264]

Robert I am preparing for CIS-RC certification (new to Snow) any content or advice for me on passing it.

[@robertthedukefedoruk5607]

I'm not really deep on Risk & Compliance. GENERALLY though, get as much practice as you can ON THE PLATFORM. Reading is only ever going to get you so far. I'd also suggest calling it SN for short, or NOW. "Snow" is an asset management platform that often competes with ServiceNow.

[@jeyapriyar435]

How to parse the email body for choice field for inbound flows

[@robertthedukefedoruk5607]

You can't parse for a data type because emails don't have data types. You can only parse for a value. Hopefully the field you wish to contain that value allows it.