A downside of this is that it's not very "citizen developer" friendly. They generally don't understand events nor know what specific event name or parameters to pass. A newer way to do this would be to trigger your notification by a flow and then use the Send Notification action instead of Send Email. That allows you to manage your notifications in the same place (the notifications table) rather than being buried individually around numerous flows.
Thanks for your comment. Its hard to make everything as citizen developer friendly in ServiceNow when it comes to dynamic apps. App Engine Studio is not purchased by every company and I don't think we should only focus on the concept of Citizen Developer. Moreover, Email was just an example for showing how custom action can be used. We get most questions on actual development not just Citizen Development and I think we need to work around what developer needs at ground level, not what ServiceNow thinks what developer should do.
@@SAASWithServiceNow Thanks for the response. Don't over rotate on citizen development. My point was towards all coders - Send Notification is a preferred way to send a message from a flow because of better management. BTW, it's a standard Flow Designer capability not an app engine only feature. I agree with you that building custom actions is powerful stuff. My most common use case is with integrations.
Not rotating but just trying to make my point. I want to make sure community understands both of our points. If I am not wrong Citizen Development is shown via App Engine only so i don't use that word for core developers. I know we can use that in flow as well without app engine. Workflow has Create Event Activity however Flow does not so I think it is a logical use case and I am sure developers must be using it in different engagements. I will try with integration as well. Thanks for recommending that.
@@ChuckTomasi Send Notification seems to only be available with the Next Experience UI versus 16/15. And, configuring a Notification is so complex that if you set it up to work, it'd take a genius to modify it without breaking the functionality.
I've watched this one a few times. Too much jumping around. You tried to ad-lib instead of having a prepared session. No explanation for why a custom action needs event queue. A practical example will help -- the one you chose is too I don't know what. Maybe you need to explain what an event queue item is with something practical rather than using names like parameter1 and parameter2. What you show is possible with Flow Designer logic and thus a custom action seems overly complex.
Here are some reasons why a custom action may need to register an item in the Event Queue table: o Asynchronous processing: If the custom action needs to perform a time-consuming operation that may cause a delay in the flow execution, it can register an item in the Event Queue table to execute the operation asynchronously. This allows the flow to continue executing without waiting for the operation to complete, improving performance and reducing the risk of timeouts. o Delayed execution: If the custom action needs to be executed at a specific time or date, it can register an item in the Event Queue table with a scheduled execution time. o Handling large volumes of data: If the custom action needs to process large volumes of data, it can register an item in the Event Queue table to handle the data in smaller batches, improving performance and reducing the risk of timeouts. o Recovering from failures: If the custom action encounters a failure during execution, it can register an item in the Event Queue table to retry the action at a later time. By registering an item in the Event Queue table, a custom action can take advantage of the built-in queuing and scheduling functionality provided by ServiceNow, improving performance, reliability, and scalability.
A downside of this is that it's not very "citizen developer" friendly. They generally don't understand events nor know what specific event name or parameters to pass. A newer way to do this would be to trigger your notification by a flow and then use the Send Notification action instead of Send Email. That allows you to manage your notifications in the same place (the notifications table) rather than being buried individually around numerous flows.
Thanks for your comment. Its hard to make everything as citizen developer friendly in ServiceNow when it comes to dynamic apps. App Engine Studio is not purchased by every company and I don't think we should only focus on the concept of Citizen Developer. Moreover, Email was just an example for showing how custom action can be used. We get most questions on actual development not just Citizen Development and I think we need to work around what developer needs at ground level, not what ServiceNow thinks what developer should do.
@@SAASWithServiceNow Thanks for the response. Don't over rotate on citizen development. My point was towards all coders - Send Notification is a preferred way to send a message from a flow because of better management. BTW, it's a standard Flow Designer capability not an app engine only feature. I agree with you that building custom actions is powerful stuff. My most common use case is with integrations.
Not rotating but just trying to make my point. I want to make sure community understands both of our points. If I am not wrong Citizen Development is shown via App Engine only so i don't use that word for core developers. I know we can use that in flow as well without app engine. Workflow has Create Event Activity however Flow does not so I think it is a logical use case and I am sure developers must be using it in different engagements. I will try with integration as well. Thanks for recommending that.
@@ChuckTomasi Send Notification seems to only be available with the Next Experience UI versus 16/15. And, configuring a Notification is so complex that if you set it up to work, it'd take a genius to modify it without breaking the functionality.
Could you please let me know how to update assignment group & approval in otb flow designer.
Hi Sir what is servicenow platform management, what topics will comes under
Hai sir .Do you have idea about Field Service Management(FSM).
Could you please upload video on ITOM please..
How to create sourcing request in flow designer
For Hardware asset refresh order
I've watched this one a few times. Too much jumping around. You tried to ad-lib instead of having a prepared session. No explanation for why a custom action needs event queue. A practical example will help -- the one you chose is too I don't know what. Maybe you need to explain what an event queue item is with something practical rather than using names like parameter1 and parameter2. What you show is possible with Flow Designer logic and thus a custom action seems overly complex.
Here are some reasons why a custom action may need to register an item in the Event Queue table:
o Asynchronous processing: If the custom action needs to perform a time-consuming operation that may cause a delay in the flow execution, it can register an item in the Event Queue table to execute the operation asynchronously. This allows the flow to continue executing without waiting for the operation to complete, improving performance and reducing the risk of timeouts.
o Delayed execution: If the custom action needs to be executed at a specific time or date, it can register an item in the Event Queue table with a scheduled execution time.
o Handling large volumes of data: If the custom action needs to process large volumes of data, it can register an item in the Event Queue table to handle the data in smaller batches, improving performance and reducing the risk of timeouts.
o Recovering from failures: If the custom action encounters a failure during execution, it can register an item in the Event Queue table to retry the action at a later time.
By registering an item in the Event Queue table, a custom action can take advantage of the built-in queuing and scheduling functionality provided by ServiceNow, improving performance, reliability, and scalability.