Flow Designer Flashcards
The flow designer roles are as follows:
___: create and edit flows
___: view flow execution details, dashboards, and logs
___: create and edit custom actions
flow_designer: create and edit flows
flow_operator: view flow execution details, dashboards, and logs
action_designer: create and edit custom actions
Interactive sessions
1. Only Run for Non-Interactive Session:
2. Only Run for User Interactive Session:
3. Run for Both Interactive and Non-Interactive Sessions:
Interactive sessions
* Only Run for Non-Interactive Session: Execute the flow when the record is created or updated from an API. See the ServiceNow docs site for more information on Non-interactive sessions.
* Only Run for User Interactive Session: Execute the flow when a logged in user creates or updates a record.
* Run for Both Interactive and Non-Interactive Sessions: Execute the flow regardless of how the record is created or updated.
Users
Do not run if triggered by the following users:
Only Run if triggered by the following users:
Run for any user:
Users
1. Do not run if triggered by the following users: Specify a list of users who cannot execute the flow.
2. Only Run if triggered by the following users: Specify a list of users who can execute the flow.
3. Run for any user: Execute the flow for any user.
Tables
Run only on current table:
Run on current and extended tables:
Tables
Run only on current table: Execute the flow only when records are created or updated on the selected table.
Run on current and extended tables: Execute the flow when records are created or updated on the selected table or any table that extends the selected table.
Configure where to run the flow:
Run flow in background (default):
Run flow in foreground:
Configure where to run the flow:
Run flow in background (default): Execute the flow asynchronously. Use this option for flows that do not require immediate updates and to allow other system processes to run at the same time.
Run flow in foreground: Execute the flow synchronously to provide immediate updates to the user. Running a flow in foreground may block the current session thread and prevent user input until the flow finishes.
When the trigger is set to ___ or ___ or ___, the trigger includes a Changed Fields array to access any changed field data in the flow. To simulate changed information in a test, the Test Flow dialog includes a Changed Fields section to add data to the array for use in testing the flow.
When the trigger is set to Updated or Created or Updated, the trigger includes a Changed Fields array to access any changed field data in the flow. To simulate changed information in a test, the Test Flow dialog includes a Changed Fields section to add data to the array for use in testing the flow.
When testing the changed fields array includes what fields, and how are the values captured?
All values in the array are strings.
Field Name: The Name of the changed field, not the label.
Previous Value: The field value before the update.
Current Value: The field value after the update.
Previous Display Value: The field display value before the update.
Current Display Value: The field display value after the update.
Flows with a ___ trigger do not require a record to test the flow. Click the Run Test button to execute the test.
Flows with a Date trigger do not require a record to test the flow. Click the Run Test button to execute the test.
Flows with an ___ trigger require an Email Record to test the flow. Select the record to use for the test in the Test Flow dialog.
Flows with an Inbound Email trigger require an Email Record to test the flow. Select the record to use for the test in the Test Flow dialog.
Flows with a ___ trigger require a Requested Item Record to test the flow. Select the record to use for the test in the Test Flow dialog.
Flows with a Service Catalog trigger require a Requested Item Record to test the flow. Select the record to use for the test in the Test Flow dialog.
Open flow execution details from:
___: Click the Your test has finished running. View the flow execution details. link.
___: Click the Executions button on a flow to see a list of executions associated with that flow.
___: Click the landing page’s Executions tab to see all flow executions.
___: Open Process Automation > Flow Administration > ___ ___ in the All menu to see executions run today.
___: Open Process Automation > Flow Administration > ___ ___ in the All menu to see currently executing flows.
Open flow execution details from:
The Test Flow dialog: Click the Your test has finished running. View the flow execution details. link.
Flow-specific executions list: Click the Executions button on a flow to see a list of executions associated with that flow.
Flow Designer landing page: Click the landing page’s Executions tab to see all flow executions.
Today’s Executions: Open Process Automation > Flow Administration > Today’s Executions in the All menu to see executions run today.
Active Flows: Open Process Automation > Flow Administration > Active Flows in the All menu to see currently executing flows.
The Flow Statistics section shows:
The Flow Statistics section shows who executed the flow, what the flow execution state is, when the flow began execution, and how long the flow took to run.
Are flows logged?
Active flows are not logged by default. Set the Level of reporting data generated by the flow engine. Flow Designer property to see flow execution details for active flows executed from the trigger. Use the All menu to open Process Automation > Flow Administration > Properties
By default a flow runs as who? Why is this the case?
By default, a flow executes as the user who triggers the flow. When a flow runs as a user, the user needs permissions to run the actions executed by the flow. For example, if a user initiates a flow that creates a record, but the user does not have permissions to create the record, the flow stops execution with an error.
Flows can run as the:
User who initiates session: ___
System User: ___
Flows can run as the:
User who initiates session: The flow runs as the user who triggered the flow. For example, if a flow executes when a record is created, the flow runs as the user who created the record.
System User: The flow runs as the System User. The System User is not a user record from the User table. System is a service account that is not restricted by access controls.
