Skip to main content

ServiceNow Flow Designer Sys Properties

 ServiceNow Flow Designer Sys Properties

see https://docs.servicenow.com/bundle/utah-build-workflows/page/administer/flow-designer/reference/flow-designer-system-properties.html



property com.snc.process_flow.reporting.level




Level of reporting data generated by the flow engine.

com.snc.process_flow.reporting.level

Specify when Flow Designer generates execution details and what information the details include. Options include:
Off
Reporting is deactivated. The system only generates execution details when you run a test.
Note: Testing an action or flow generates execution details at the Developer Trace level.
Flows Only
Reporting is activated for all flows and subflows. Execution details show the status and duration of each flow and subflow run. You can see the configuration and runtime values of flow triggers and subflow inputs.
Flows and Actions
Reporting is activated for all flows, subflows, and actions. Execution details show the status and duration of each flow, subflow, and action run. You can see the configuration and runtime values of flow triggers and the inputs and output values of subflows and actions.
Flows Actions and Steps
Reporting is activated for all flows, subflows, actions, and the steps of custom actions. Execution details show the status and duration of each flow, subflow, action, and the steps of custom actions run. You can see the configuration and runtime values of flow triggers and the inputs and output values of subflows, actions, and the steps of custom actions.
Developer Trace
Reporting is activated for all flows, subflows, actions, and steps (custom and base system). Execution details show the status and duration of each flow, subflow, action, step run. You can see the configuration and runtime values of flow triggers and the inputs and output values of subflows, actions, and steps.
Note: Testing an action or flow generates execution details at the Developer Trace level.
The reporting level determines what if any flow execution details are generated. If a flow runs while reporting is off, execution details are never available for the flow, even if the reporting level later changes. If a flow runs while reporting is activated, execution details are always available for that flow execution, even if the reporting level later changes.
Labels:

Comments

Post a Comment

Popular posts from this blog

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){...
Post a Comment
Read more

Code a pause/wait - gs.sleep or gs.wait alternative, pause script for specified seconds (timer)

Code a pause/wait - gs.sleep / gs.wait alternative, pause script for specified seconds (timer)  e.g. 10 seconds: do_sleep ( 10000 ); function do_sleep ( milliseconds ) { var start = new Date (). getTime (); for ( var i = 0 ; i < 1e7 ; i ++) { if (( new Date (). getTime () - start ) > milliseconds ){ gs . print ( 'waking up!' ); break ; } } }
Post a Comment
Read more