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

URL link in addInfoMessage

var ga=new GlideAjax('gld_HR_ajax'); ga.addParam('sysparm_name', 'checkEmployeeNumber_hrProfile'); ga.addParam('sysparm_hrprofilenumber', g_form.getValue('number')); ga.addParam('sysparm_employeenumber', newValue); ga.getXMLAnswer(function(answer) { if (answer!='undefined' && answer!=''){ var navURL="<a style='text-decoration:underline;color:blue' href=hr_profile.do?sysparm_query=number=" + answer + ">" + answer + "</a><img width='3' src='images/s.gif'/>"; var sMsg='The employee number entered already exists on another HR Profile ' + navURL; //alert(sMsg); g_form.showErrorBox('employee_number', 'error - please check'); g_form.addInfoMessage(sMsg); } });
1 comment
Read more

GlideRecord setValue

setValue(String name, Object value) Sets the specified field to the specified value. Normally a script would do a direct assignment, for example,  gr.category = value . However, if in a script the element name is a variable, then  gr.setValue(elementName, value)  can be used. When setting a value, ensure the data type of the field matches the data type of the value you enter. This method cannot be used on journal fields. If the value parameter is null, the record is not updated, and an error is not thrown https://developer.servicenow.com/app.do#!/api_doc?v=madrid&id=r_GlideRecord-setValue_String_Object
2 comments
Read more