Currently there is ability to use workflow and flow designer ex service catalog. What future of worflow? Does FD is replacement for WF? which is recommended to use?
The graphical workflow engine will continue to live on in the platform. There is no announcement to remove it. However, it will not be receiving any further updates or enhancements. The strategic direction for creating workflows is Flow Designer. Depending on your experience and investment, you may wish to continue maintaining existing workflows or assess the ability to migrate them (manually) to Flow Designer. The biggest mental hurdle I had was to stop thinking of Flow Designer as a replacement to Workflow. It is, sort of. Think of it more like Business Rules, scriptless scheduled jobs, and inbound notifications on super steroids.There's a trigger then a series of actions. I've seen customers with some pretty monolithic workflows (in the graphical workflow engine) that have a lot of script, loop all around and pretty much run until the record is closed. Flows can be more prescriptve, and thus easier to write and maintain, thus you can run then at specific points in your process flow. I recommend creating any new flows in Flow Designer.
We just released a BMC Remedy spoke for IntegrationHub on the store. store.servicenow.com/sn_appstore_store.do#!/store/application/677a7b2ddb024010ea4494d9db9619f5/1.0.1?referer=%2Fstore%2Fsearch%3Fq%3Dremedy%26apptype%3Dallintegrations&sl=sh
You can save a JSON response as a string field which will give you the string representation. If you want to parse it, then JSON.parse(your_response_body_here) will allow you to access the individual elements of the payload.
Very Helpful session! Thanks a lot kreg,chuck,stacey!👍
#keeplearning#keepexploring#keepsharing
Chuck is a legend :)
Really great video with step by step explanation! Thank you
Thanks
Currently there is ability to use workflow and flow designer ex service catalog. What future of worflow? Does FD is replacement for WF? which is recommended to use?
The graphical workflow engine will continue to live on in the platform. There is no announcement to remove it. However, it will not be receiving any further updates or enhancements. The strategic direction for creating workflows is Flow Designer. Depending on your experience and investment, you may wish to continue maintaining existing workflows or assess the ability to migrate them (manually) to Flow Designer. The biggest mental hurdle I had was to stop thinking of Flow Designer as a replacement to Workflow. It is, sort of. Think of it more like Business Rules, scriptless scheduled jobs, and inbound notifications on super steroids.There's a trigger then a series of actions. I've seen customers with some pretty monolithic workflows (in the graphical workflow engine) that have a lot of script, loop all around and pretty much run until the record is closed. Flows can be more prescriptve, and thus easier to write and maintain, thus you can run then at specific points in your process flow. I recommend creating any new flows in Flow Designer.
Can we use standard package to integrate with Remedy
We just released a BMC Remedy spoke for IntegrationHub on the store. store.servicenow.com/sn_appstore_store.do#!/store/application/677a7b2ddb024010ea4494d9db9619f5/1.0.1?referer=%2Fstore%2Fsearch%3Fq%3Dremedy%26apptype%3Dallintegrations&sl=sh
if I want to save the json response to a snow table, how to do that
You can save a JSON response as a string field which will give you the string representation. If you want to parse it, then JSON.parse(your_response_body_here) will allow you to access the individual elements of the payload.