Our AI writing assistant, WriteUp, can assist you in easily writing any text. Click here to experience its capabilities.

Flow Designer

View Original View Raw

Summary

This blog provides an overview of Flow Designer, a new feature in ServiceNow that allows users to configure process flows without code. Flow Designer is useful for automating daily processes and reducing development costs. It consists of triggers, actions, and flow logic. Actions include ServiceNow core, global, connect, customer service, ITSM, and Visual Task Board actions. Flow Designer also has an IntegrationHub component for integrating with other systems. The blog also provides a best practice for configuring and automating existing processes and an example of configuring a simple flow involving an incident.

Q&As

What is Flow Designer and what is its purpose?
Flow Designer is a new feature introduced in Kingston to configure the process flow without any code involved. Its purpose is to automate daily processes.

What are the usage and benefits of Flow Designer?
The usage and benefits of Flow Designer are that it is used to automate daily processes, it is very useful and user friendly for all ServiceNow users, even for non-technical users and management people, and it reduces development cost in business.

What roles are necessary for Flow Designer configuration?
The roles necessary for Flow Designer configuration are flow_designer (full access to flow designer), flow_operator (view access), and action_designer (only to create and edit actions).

What components does Flow Designer consist of?
Flow Designer consists of triggers, actions, flow logic, and visual task boards.

What are the best practices for Flow Designer?
The best practices for Flow Designer are to deactivate the original process if configuring/automating an existing process in ServiceNow, to run tests only on Dev and QA and not on production, and to add an else condition and send an email to the caller of the incident if the approval is rejected.

AI Comments

👍 This article is well-written and provides an in-depth overview of the Flow Designer feature in ServiceNow. It is concise and clearly explains the benefits, roles, and best practices of Flow Designer.

👎 This article doesn't provide any examples or illustrations to make it easier to understand the concept of Flow Designer. Additionally, it doesn't discuss any possible drawbacks or limitations of using Flow Designer.

AI Discussion

Me: It's about Flow Designer, a new feature introduced in ServiceNow that allows users to configure process flows without any code involved. It's a great tool for non-technical users and management people, and it can automate certain daily processes, like employee onboarding and offboarding, password reset and expiration management, task management, and simple business logic.

Friend: Wow, that sounds really useful. What are the roles associated with Flow Designer configuration?

Me: Right. So, there are three roles associated with Flow Designer configuration - flow_designer (full access to Flow Designer), flow_operator (view access), and action_designer (only to create and edit actions). It also consists of triggers, actions, and flow logic. With triggers, you can initiate the flow on record creation/update or you can schedule it. Actions are pre-defined and include ServiceNow Core (create/update/delete/look up record, create task, approval, email, log and wait for condition), Global (custom actions created by the user), Connect (add group, user, and message to a task), Customer Service (add comment/work note to a task or assign/create/update/escalate task), ITSM (create change, incident and problem in different scenarios or add comments or do assignments), and Visual Task Board (manage boards, lanes, cards, board members, and assignees in VTB). Flow logic provides conditions to the flow, like applying an action on each record it gets or applying an if/else logic.

Friend: That's really interesting. What are some of the best practices for using Flow Designer?

Me: Yeah, so some of the best practices include deactivating the original process when configuring/automating an existing one, and only running tests on the Dev and QA environments and not on production, as it could affect existing data.

Action items

Research more about Flow Designer and its features.
Try to create a simple flow using Flow Designer.
Explore the different roles and actions available in Flow Designer.

Technical terms

Flow Designer: A new feature introduced in ServiceNow Kingston to configure the process flow without any code involved.
Trigger: The point to initiate the flow.
Action: Pre-defined actions to be performed which are useable unit.
Flow Logic: The logic of process where condition and if/else is included.
ServiceNow Core: Core actions of ServiceNow like create/update/delete/look up record, create task, approval, email, log and wait for condition.
Global: Custom actions created by the user.
Connect: Action which can add group, user, and message to a task.
Customer service: Actions which operate on customer service management.
ITSM: Actions which operate on ITSM modules like incident/problem/change/request.
Visual Task board: Actions to manage the boards, lanes, cards, board members, and assignees in VTB.
IntegrationHub: Used to for integration with other system which required IntegrationHub plugin.