Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

How to include flow report output settings in an update set

bonsai
Mega Sage

bonsai_0-1763541367665.png

 

I'm thinking of changing the report settings for each flow, while leaving the instance-wide flow report settings as they are.

Because there are a large number of affected flows, I would like to use update sets.

However, the report output settings were not recorded in the update set.

Do I have to configure these settings manually?

1 ACCEPTED SOLUTION

Brad Bowman
Kilo Patron
Kilo Patron

As you discovered, Flow Reporting settings thankfully are not captured in an update set.  The system property named com.snc.process_flow.reporting.level should be set to the value of BASIC so that one can view the Flow Context on a record and see the execution steps and result.  All new flows, and those promoted to other instances will then take on this setting.  As is written everywhere on this topic, you do not need or want to set this property to FULL in any instance, and should only change individual flows to this sparingly due to the amount of data that you'll be needlessly adding to your instances.  Flows should be tested in Flow Designer / Workflow Studio, which generates the full reporting/logging.  The setting can be changed per flow if you must test outside of Workflow Studio, but then there is no reason to have Full logging in non-development instances.  I was happy to learn that this is the case so that I do not have to monitor when my developers change the setting then forget to change it back before promoting the update set.

 

You can easily see and update the reporting level on all flows via Flow Administration > Settings in the left nav, which is the sys_flow_execution_setting table.  This value changes immediately when a Flow Reporting Setting is changed in Workflow Studio, and will get reset to the system property setting when a flow is promoted. 

View solution in original post

7 REPLIES 7

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @bonsai 

It looks like it might be a cache issue, because if you change anything in the flow and then publish it, it must capture an update set. Try the same with a new update set instead of the existing one and see if that works or not

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

I created a new update set and made some report changes, but they were not recorded.

Also, after making the report changes, I tried changing some actions and recording them in an update set, but when I applied it to another instance, the report settings were not reflected.

Brad Bowman
Kilo Patron
Kilo Patron

As you discovered, Flow Reporting settings thankfully are not captured in an update set.  The system property named com.snc.process_flow.reporting.level should be set to the value of BASIC so that one can view the Flow Context on a record and see the execution steps and result.  All new flows, and those promoted to other instances will then take on this setting.  As is written everywhere on this topic, you do not need or want to set this property to FULL in any instance, and should only change individual flows to this sparingly due to the amount of data that you'll be needlessly adding to your instances.  Flows should be tested in Flow Designer / Workflow Studio, which generates the full reporting/logging.  The setting can be changed per flow if you must test outside of Workflow Studio, but then there is no reason to have Full logging in non-development instances.  I was happy to learn that this is the case so that I do not have to monitor when my developers change the setting then forget to change it back before promoting the update set.

 

You can easily see and update the reporting level on all flows via Flow Administration > Settings in the left nav, which is the sys_flow_execution_setting table.  This value changes immediately when a Flow Reporting Setting is changed in Workflow Studio, and will get reset to the system property setting when a flow is promoted.