Chuck, thank you for this. How about being able to script the inbound flow to use a user's secondary email device to process the inbound flow and populate a caller or requester in a Task based record. Currently, if using the user record to populate the requester, the flow will only process the inbound email if the from address matches primary email in the User's User record. I looked but couldn't find an existing data pill to use a secondary email device.
@@ChuckTomasi, thanks for the response. When I was Googling for ideas, I had run across this video, so thought I'd pose the question here first. However, I'll certainly post in Community.
Hi Chuck, good video. But to bad ServiceNow does not support the use of the body variables in Flow Designer. That would really make Flow Designer much more powerful
@@ChuckTomasi I'm not that good with coding but I do believe you are right. But if ServiceNow want us all to switch to Flow Designer it should have those base functions and actions OOTB which you want us to stop using. Flow Designer has potential, but If I need to write many actions myself it's not low-code anymore.
More complicated than what? Script. To that I say false. Far less learning curve, far less technical debt. (and this is from a guy who's been enjoying coding for 40 years.)
Chuck, thank you for this. How about being able to script the inbound flow to use a user's secondary email device to process the inbound flow and populate a caller or requester in a Task based record. Currently, if using the user record to populate the requester, the flow will only process the inbound email if the from address matches primary email in the User's User record. I looked but couldn't find an existing data pill to use a secondary email device.
Hi Paul, I don't have an instance answer to that one. Sounds like a great discussion to explore with the community. Have you tried posting there?
@@ChuckTomasi, thanks for the response. When I was Googling for ideas, I had run across this video, so thought I'd pose the question here first. However, I'll certainly post in Community.
Hi Chuck, good video. But to bad ServiceNow does not support the use of the body variables in Flow Designer.
That would really make Flow Designer much more powerful
It wouldn't take much to write a simple action to do that kind of processing. Return an array of objects with name/value pairs.
@@ChuckTomasi I'm not that good with coding but I do believe you are right.
But if ServiceNow want us all to switch to Flow Designer it should have those base functions and actions OOTB which you want us to stop using. Flow Designer has potential, but If I need to write many actions myself it's not low-code anymore.
Flow Designer often seems like a far more complicated way of doing things despite its low-code label
More complicated than what? Script. To that I say false. Far less learning curve, far less technical debt. (and this is from a guy who's been enjoying coding for 40 years.)