Configure how the system processes flows.

These properties are available for Workflow Studio.

To set Workflow Studio system properties, select Process Automation > Properties or navigate to the System Properties [sys_properties] table.

Table 1. Properties for Workflow Studio
Property Description
The maximum number of records to return when fetching data

sn_flow_designer.action_picker_limit

 Specify the maximum number of records a look up action or step can return. Workflow Studio ignores records that exceed this limit.
  • Type: integer
  • Default value: 1000
  • Location: Process Automation > Properties
  • More information: Architecture Overview

Specify the level of messages generated by the Flow Designer execution engine to write to sys_flow_log table. These messages are generated by running flow actions and flow logic. For example, a message generated by running the Create record action. The system only writes log entries of the specified level or higher

com.glide.hub.flow_engine.log_level

 Specify the level of messages generated by the Flow Designer execution engine to write to the sys_flow_log table. These messages are generated when the flow engine runs the actions and flow logic of a flow. For example, a message generated by running the Create record action. The system only writes log entries of the specified level or higher. Choices include:
DEBUG
The system logs all messages, which include information messages, warnings, and errors, produced by the flow engine. This option is the lowest log level.
INFO
The system logs information messages, warnings, and errors produced by the flow engine.
WARN
The system logs both warnings and errors produced by the flow engine.
ERROR
The system only logs errors produced by the flow engine. This option is the highest log level.

The log level determines what if any log messages are added to the sys_flow_log table.

  • Type: choice
  • Default value: WARN
  • Location: Process Automation > Properties
  • More information: Flow execution details
Specify the log level of system log entries to replicate to the flow log. The system only replicates log entries of the specified level or higher.

com.glide.hub.flow_engine.listener_trace.threshold

 Specify the threshold required for Workflow Studio to replicate a system log entry to the flow log. These messages are generated by the ServiceNow AI Platform in response to flow execution outputs. For example, a message generated by a business rule that was triggered by a flow record operation. The system only replicates log entries of the specified level or higher. Choices include:
None
The system doesn't replicate system log entries to the flow log.
DEBUG
The system replicates all messages, which include information messages, warnings, and errors, produced by the ServiceNow AI Platform. This option is the lowest log level.
INFO
The system replicates information messages, warnings, and error messages produced by the ServiceNow AI Platform.
WARN
The system replicates both warnings and errors produced by the ServiceNow AI Platform.
ERROR
The system only replicates errors produced by the ServiceNow AI Platform. This option is the highest log level.
  • Type: choice
  • Default value: ERROR
  • Location: Process Automation > Properties

Level of logging detail from the Flow Designer approval action.

com.glide.hub.flow.approval.logging

 Specify the level of messages generated by the Ask for Approval action. The system only writes log entries of the specified level or higher. Choices include:
DEBUG
The system logs all messages, which include information messages, warnings, and errors, produced by the flow engine. This option is the lowest log level.
INFO
The system logs information messages, warnings, and errors produced by the flow engine.
WARN
The system logs both warnings and errors produced by the flow engine.
ERROR
The system only logs errors produced by the flow engine. This option is the highest log level.

The log level determines what if any log messages are added to the sys_flow_log table.
The maximum number of iterations that a loop will run in Workflow Studio.

sn_flow_designer.max_iterations

 Specify the maximum number of times that a loop can run before being stopped. A loop stops running when it iterates beyond this value, preventing infinite loops. This property only applies to Do the following until and Go back to flow logic.
  • Type: integer
  • Default value: 1000
  • Location: Process Automation > Properties
  • More information: Architecture Overview
Note: Changing this value doesn’t apply to flows that are already running.
The maximum number of records to return when fetching data

sn_flow_designer.trigger_picker_limit

 Specify the maximum number of records a look up triggers query can return. Workflow Studio ignores triggers that exceed this limit.
Allow the option for select users to write a script to populate the value of an input on Flow and Action Designers.

sn_flow_designer.input_scripts_enabled

 Control permission to write inline scripts to compute input values.
  • Type: true | false
  • Default value: true
  • Location: Process Automation > Properties
  • More information: Inline scripts
Set to True to show duration in the stage column

com.glide.hub.flow_engine.stage_display.show_duration

 Specify whether flows with stages display a duration.
  • Type: true | false
  • Default value: true
  • Location: Process Automation > Properties
  • More information: Flow and subflow stages
Number of times that a flow or subflow can be indirectly triggered during a transaction

com.glide.hub.flow_engine.indirect_recursion_limit

 Specify the maximum number of times a flow or subflow permits indirect recursion. Workflow Studio ignores all further calls or trigger condition matches from indirect recursion after the limit has been reached. Set the value to any integer equal to or greater than one. The system ignores any property value less than one and instead uses a limit of one. Set the value to one to prevent all indirect recursion.
  • Type: integer
  • Default value: 3
  • Location: Process Automation > Properties
  • More information: Architecture Overview
The maximum number of actions allowed on a flow.

sn_flow_designer.max_actions

 Specify the maximum number of actions a flow or subflow can contain. Workflow Studio prevents you from adding further actions after the maximum number of actions has been reached. Consider the performance impact raising the maximum number of actions may have. For example, running more actions may conflict with the default transaction quota rule that prevents flows from running longer than an hour.
  • Type: integer
  • Default value: 50
  • Location: Process Automation > Properties
  • More information: Architecture Overview
The maximum number of allowed steps on an action.

sn_flow_designer.max_action_steps

 Specify the maximum number of steps that an action can contain. Workflow Studio prevents you from adding further steps after the maximum number of steps has been reached. Consider the performance impact raising the maximum number of steps may have. For example, running more steps may conflict with the default transaction quota rule that prevents flows from running longer than an hour.
  • Type: integer
  • Default value: 20
  • Location: Process Automation > Properties
  • More information: Architecture Overview
Level of reporting data generated by the flow engine.

com.snc.process_flow.reporting.level

 Specify when Workflow Studio generates execution details and what information the details include. Options include:
Off
The system doesn't generate flow execution details. The system only generates execution details when you run a test.
Note: Testing an action or flow generates execution details at the Trace level.
Basic: Runtime states and durations only
The system generates runtime execution details for each flow, subflow, and action run. You can see the runtime state and duration for these basic items. You can also see configuration and runtime values for flow triggers, subflow inputs, and subflow outputs.
Full: Action configuration and runtime values (for debugging only)
The system generates configuration and runtime execution details for each flow, subflow, and action run. You can see the runtime state, duration, input values, and output values for all items. For custom actions, you can also see the runtime state, duration, input values, and output values of its steps. You can also see the configuration values for flow triggers, subflows, actions, and steps that are part of a custom action.
Important: Only users with the fd_read_operations_all role can see configuration and runtime information such as record values in the flow execution details. Users without this role will only see basic details about the state and duration.
Trace: All values (for testing and Support only)
The system generates configuration and runtime execution details for each flow, subflow, action, and step run. You can see the runtime state, duration, input values, and output values for all items. You can also see the configuration values for flow triggers, subflows, actions, and steps.
Important: Only users with the fd_read_operations_all role can see configuration and runtime information such as record values in the flow execution details. Users without this role will only see basic details about the state and duration. Testing an action or flow generates execution details at the 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.
  • Type: choice
  • Default value: Off
  • Location: Process Automation > Properties
  • More information: Flow execution details

Replace previous autosave history with latest as long as it was within the last "X" minutes and by the same user.

sn_flow_designer.autosave_version_interval

 Specify the number of minutes to overwrite autosave history entries that are generated by the same user. All autosave history entries generated by the same user during this interval are saved as one history entry. During this interval, the most recent autosave history entry overwrites the previous autosave history entry. Consider the performance impact that changing the autosave history interval may have. For example, setting the autosave interval to its minimum value of 1 minute may result in generating so many history records that you hit the history limit, and start overwriting older history records.

Maximum number of flow history records (Limit: 200).

sn_flow_designer.maximum_flow_history_records_per_flow

 Specify the maximum number of flow history entries to store per flow or subflow. This property has a minimum value of 30 and a maximum value of 200. When the number of flow history records exceeds the limit, then the newest flow history entry overwrites the oldest flow history record. Consider the performance impact that changing the number of flow history records may have. For example, setting the limit to its maximum value of 200 may produce a delay in rendering flow history records.

Truncate runtime values in the flow execution details step configuration

com.snc.process_flow.reporting.serialized.val_size_limit

 Specify the number of bytes the system has to write runtime values to the flow execution details. To prevent truncation of runtime values, set the value to an integer equal to or less than zero. Preventing truncation of runtime values requires additional system resources and may impact system performance.
  • Type: integer
  • Default value: 16384
  • Location: System Properties [sys_properties] table
  • More information: Flow execution details

Maximum inputs per action

sn_flow_designer.max_action_vars

 Specify the maximum number of inputs that can be added to an action. Workflow Studio prevents you from adding further inputs after the maximum number of inputs has been reached. Consider the performance impact raising the maximum number of action inputs may have. For example, processing more action inputs may risk the action running for more than an hour and being stopped by the default transaction quota rule.
  • Type: integer
  • Default value: 20
  • Location: System Properties [sys_properties] table

Maximum script variables per Script step

sn_flow_designer.max_script_variables

 Specify the maximum number of input and output variables that can be added to a Script step. Workflow Studio prevents you from adding further script variables after the maximum number of variables has been reached. Consider the performance impact raising the maximum number of script variables may have. For example, processing more script variables may risk the Script step running for more than an hour and being stopped by the default transaction quota rule.
  • Type: integer
  • Default value: 20
  • Location: System Properties [sys_properties] table

Maximum number of branches allowed for the Make a decision flow logic

sn_flow_designer.max_decision_branches

 Specify the maximum number of branches to use when the Use Branches option is selected for the Make a decision flow logic.
  • Type: integer
  • Default value: 100
  • Location: System Properties [sys_properties] table

Option to enable users to create flow variables.

sn_flow_designer.flow_variables_enabled

 Specify whether users can create custom variables for their flow.
  • Type: true | false
  • Default value: true
  • Location: System Properties [sys_properties] table

Maximum number of popular actions

sn_flow_designer.action_picker.popular_actions.max_number

 Specify the maximum number of popular actions to display in the Action picker.
  • Type: integer
  • Default value: 10
  • Location: System Properties [sys_properties] table

Number of consecutive days used to generate popular actions

sn_flow_designer.action_picker.popular_actions.last_num_of_days

 Specify the number of consecutive days used to generate popular actions. For example, the default value of 7 generates popular actions based on action usage during the last week.
  • Type: integer
  • Default value: 7
  • Location: System Properties [sys_properties] table

com.glide.hub.flow.restricted_caller_access.track_flows_as_source

 Allow the system to generate restricted caller access privilege requests for flows and actions. The access privileges for flows and actions supersede any existing access privileges for script includes and business rules that call flows and actions. This property is inactive on instances upgraded from San Diego and earlier releases. Customers who want to continue using script-based access privileges for flows and actions shouldn’t enable this property. Enabling this property requires you to regenerate and approve access privileges for your flows and actions.
  • Type: true | false
  • Default value: true for Tokyo and later releases. False for San Diego and earlier releases.
  • Location: System Properties [sys_properties] table
  • More information: Restricted caller access privilege settings

com.glide.cs.fdih.interactive.timeout

 Specify the length of time, in seconds, before the Workflow Studio Integration Hub action workflow times out.

com.glide.hub.pause_low_priority_flows_enabled

 Enable or disable the pausing of low-priority flows when there are high-priority flows waiting to run.
  • Type: true | false
  • Default value: true
  • Location: System Properties [sys_properties] table
  • More information: Flow priority

com.glide.hub.flow_engine.stage_display.show_approvers

 Show or hide the list of approvers assigned to a stage from a stage field. Set the value to true to show the list of approvers assigned to a stage. Set the value to false to hide the list of approvers assigned to a stage.
  • Type: true | false
  • Default value: true
  • Location: Add to the System Properties [sys_properties] table
  • More information: Flow and subflow stages
com.glide.hub.flow_engine.stage_display.show_approvers_limit Specify the maximum number of approvers to display in a stage field as an integer value. Setting this value above 10 risks causing rendering errors in a list view. The stage field for one record can become so big that the list cannot display additional records in the list.
  • Type: integer
  • Default value: 5
  • Location: Add to the System Properties [sys_properties] table
  • More information: Flow and subflow stages
com.glide.hub.flow.current_stage_status_on_cancel
Specify the status to apply to the currently running stage when the flow is cancelled. Options include:
  • cancelled
  • complete

Any remaining stages after the current stage are set to the cancelled status. For example, suppose that a flow has three stages, and that the flow is currently running the first stage. Cancelling the flow sets that status of stage one to complete. Stages two and three are set to the cancelled status.

  • Type: string
  • Default value: complete
  • Location: Add to the System Properties [sys_properties] table
  • More information: Flow and subflow stages
com.glide.hub.flow.approval.allow_inactive_entity
Specify which types of inactive entities to create approval records for. Options include:
  • INDIVIDUAL
  • GROUP
  • INDIVIDUAL,GROUP
  • null

Use the INDIVIDUAL option to create user approval records for inactive users who are not members of a group. This option doesn't create group approval records for inactive groups, nor does it create user approval records for group members.

Use the GROUP option to create a group approval records for inactive groups. This option also creates individual user approval records for group members who have active user records. This option doesn't create individual user approval records for group members who have inactive user records.

Use the INDIVIDUAL,GROUP option to create user approval records for inactive users and group approval records for inactive groups. This option also creates individual user approval records for group members who have active user records. Inactive group members don't receive user approval records.

Use a null or empty value to prevent creating group approval records for inactive groups, and also prevent creating user approval records for inactive users.

  • Type: string
  • Default value: INDIVIDUAL,GROUP
  • Location: Add to the System Properties [sys_properties] table
  • More information: Ask for Approval action
com.glide.hub.flow_api.default_execution_time Specify the default duration in milliseconds your Flow API calls can run. Use this property to give Flow API calls in spokes more time to run. The maximum value of this property is limited by REST transaction quotas, which by default the system stops after 60 seconds.
  • Type: integer
  • Default value: 30000 (30 seconds)
  • Location: System Properties [sys_properties] table
  • More information: Transaction quotas
com.glide.hub.flow.approval.show_approver_name_in_audit When true, the audit history generates a comment containing the name of the person who made an approval and the change made in the approval field. For example, an approval message might read, "Fred Luddy | Approval | Approved was Requested." When false, the audit history shows the name of the person who started the flow that ran the Ask for the approval action.
  • Type: true | false
  • Default value: true
  • Location: Add to the System Properties [sys_properties] table
  • More information: Ask for Approval action
com.glide.hub.flow.approval.show_higher_role_audit_comment When true, the audit history generates a comment containing the name of the person who made an approval and a note that the approval permission was granted by a role. For example, an approval message might read, "Fred Luddy approved, permission granted by role." A rejection message might read, "Fred Luddy rejected, permission granted by role." When false, no comment is generated.
  • Type: true | false
  • Default value: true
  • Location: Add to the System Properties [sys_properties] table
  • More information: Ask for Approval action
com.glide.hub.flow.approval.show_delegate_audit_comment When true, the audit history generates a comment containing the name of the person who made an approval and a note that the approval was made while acting as a delegate of another user. For example, an approval message might read, "Abraham Lincoln approved the task as delegate of Fred Luddy." A rejection message might read, "Abraham Lincoln rejected the task as delegate of Fred Luddy." When false, no comment is generated.
  • Type: true | false
  • Default value: true
  • Location: Add to the System Properties [sys_properties] table
  • More information: Ask for Approval action
com.glide.hub.flow.approval.show_impersonate_audit_comment When true, the audit history generates a comment containing the name of the person who made an approval and a note that the approval was made while impersonating another user. For example, an approval message might read, "System Administrator approved the task by impersonating Fred Luddy." A rejection message might read, "System Administrator rejected the task by impersonating Fred Luddy."
  • Type: true | false
  • Default value: true
  • Location: Add to the System Properties [sys_properties] table
  • More information: Ask for Approval action
com.glide.hub.flow.approval.default_approval_field When true, the Ask for Approval action uses a table's default approval field for the value of the Approval field input when no input value is provided. For example, the Request Item [sc_req_item] table uses the Approval field to display the approval state. Set this value to false when you want the Ask for Approval action to behave like classic Workflow approval activities.
  • Type: true | false
  • Default value: true
  • Location: Add to the System Properties [sys_properties] table
  • More information: Ask for Approval action
com.glide.hub.flow_engine.wait_for_email_reply_input_state
The comma-separated list of Type field values that an sys_email record must have in order for the Wait for Email Reply action to wait for the selected email record. Possible values include these send-related choices of the sys_email.type field.
  • sent
  • send-translation-ready
  • send-ready
By default, the Wait for Email Reply action includes the send-ready type. In general, email records only spend a brief time in the send-ready or send-translation-ready states. If your instance is slow to process email records in the send-ready state, you can either increase the timeout value or remove the send-ready state from this property.
com.glide.oneapi.fdih.async.quick.mode

The option to generate flow execution details when running skills. When false, flows, subflows, and actions that are run from a custom skill generate flow execution details. When true, the flow, subflow, or action runs in quick mode, which doesn't produce flow execution details.

Enable flow execution details when testing running a flow, subflow, or action from a custom skill. Since flow reporting is off by default, you must either turn flow reporting on for all flows, or create a flow execution settings record for a specific flow, subflow, or action. For more information about flow reporting options, see Activate flow reporting.
  • Type: true | false
  • Default value: true
  • Location: Add to the System Properties [sys_properties] table
  • More information: Activate flow reporting