{"id":8734,"date":"2022-11-17T11:32:09","date_gmt":"2022-11-17T06:02:09","guid":{"rendered":"https:\/\/integrtr.com\/?p=8734"},"modified":"2022-11-17T11:39:45","modified_gmt":"2022-11-17T06:09:45","slug":"verstehen-dienstleistungen-jetzt-teil-3","status":"publish","type":"post","link":"https:\/\/integrtr.com\/de\/understanding-servicenow-part-3\/","title":{"rendered":"Verst\u00e4ndnis von ServiceNow Teil 3: Let it SNow"},"content":{"rendered":"\n

Hello and welcome back to the third part of the Understanding ServiceNow<\/strong><\/em> blog series. We are well into Now-ember and it is time to cover up in the cold and embrace the new season of the year. In the previous part<\/a> of the blog series, we covered a few basics of ServiceNow including how one can get started and navigate across the Now Platform<\/em>.<\/p>\n\n\n\n

In this part, we will be looking at a specific application in ServiceNow called the Integration Hub<\/strong>.<\/p>\n\n\n\n

<\/div>\n\n\n\n

What is the Integration Hub<\/h1>\n\n\n\n

The Integration Hub is used to automate tasks and processes in ServiceNow. This can be done using the Flow Designer<\/strong> or by creating custom integrations. These integrations are reusable and act as units of no-code transformation logic that can be applied anywhere, to any application\/table, present in the Now Platform. These integrations can also be with third party systems that can be called from Integration Hub with the help of external APIs. These APIs can be custom designed using the Action Designer<\/strong> Step in Integration Hub.<\/p>\n\n\n\n

The volume of data is also controlled using Data Stream actions<\/strong> which are actions but allow data greater than 10MB to be parsed. With listener events that have pagination abilities, the inbound as well as outbound activity to-and-fro ServiceNow offers a variety of customizations.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Flow Designer Components<\/h1>\n\n\n\n
<\/div>\n\n\n\n

With the help of the flow designer you can automate processes in a particular instance.<\/p>\n\n\n\n

A flow<\/strong><\/em> in ServiceNow is a set of actions that are executed sequentially. A flow would consist of actions and triggers.<\/p>\n\n\n\n

A Subflow<\/strong><\/em> is like a reusable flow that is triggered from another flow, script or another subflow. These help with modularity when the flow is very complex. In this way, a piece of logic can be independently managed and treated with more customization when adding automation logic. This added customization comes with the ability to add specific inputs or outputs during a transformation process in relation with the parent flow.<\/p>\n\n\n\n

A Trigger<\/strong><\/em> in a flow is what defines when<\/em> a flow is put into execution. These triggers could be of different types. You could have a record trigger, for instance every time a record is updated, the flow would start getting executed. Alternatively, you could also have a date trigger or an application trigger.<\/p>\n\n\n\n

Actions<\/strong><\/em> define the work performed by a flow. These actions could be built-in or custom designed. When the flow is running, the initial actions generate output values that eventually become input data for the actions that come later in the flow.<\/p>\n\n\n\n

\"\"
Navigation on the Flow Designer<\/figcaption><\/figure>\n\n\n\n

Licensing for the Integration Hub<\/h1>\n\n\n\n
<\/div>\n\n\n\n

Integration Hub licensing is done subscription-wise in ServiceNow.<\/p>\n\n\n\n

The free subscription to the Integration Hub is the Integration Hub Starter.<\/em> To get access to the data stream actions you would require the ServiceNow Integration Hub Enterprise Pack Installer.<\/em> These installers are plug-ins that can be requested through the ServiceNow Marketplace.<\/p>\n\n\n\n

Let\u2019s Build a simple Flow<\/h1>\n\n\n\n
<\/div>\n\n\n\n

We will be creating a flow using the Flow Designer to get an approval on an issue.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Pre-requisites<\/h2>\n\n\n\n

To exercise our flow on a table, we will need to create a table. You can create it anywhere – on the App Engine Studio<\/em> or on the System Applications Studio<\/em>. The table that we will be using is named as Access Monitor<\/strong><\/em>.<\/p>\n\n\n\n

The fields required for the table are as follows:<\/p>\n\n\n\n

Column Label<\/td>Type <\/td>More Details<\/td><\/tr>
Category<\/td>Choice<\/td>Choice List Specification:<\/strong><\/em> Dropdown without \u2014 (must specify a default value)<\/kbd>
————
Choice Label: Choice Value<\/strong><\/em><\/kbd>
Big : big
Small : small
————<\/td><\/tr>
Due Date <\/td>Date<\/td><\/td><\/tr>
Location<\/td>Reference<\/td>Reference: <\/strong><\/em><\/kbd><\/kbd><\/strong><\/em><\/kbd><\/kbd> Location [cmn_location]<\/kbd><\/td><\/tr>
Opened By<\/td>Reference<\/td>Reference: <\/strong><\/em><\/kbd>User [sys_user]<\/kbd><\/td><\/tr>
Priority<\/td>Choice<\/td>Choice List Specification:<\/strong><\/em> Dropdown without \u2014None\u2014 (must specify a default value) <\/kbd>
————
Choice Label: Choice Value<\/strong><\/em><\/kbd>
Critical: critical
Moderate: moderate
Low: low
————<\/td><\/tr>
Short Description<\/td>String<\/td>Max length:<\/strong><\/em> 40<\/kbd><\/td><\/tr>
State<\/td>Choice<\/td>Choice List Specification:<\/strong><\/em> Dropdown without \u2014None\u2014 (must specify a default value) <\/kbd>
————
Choice Label: Choice Value<\/strong><\/em><\/kbd>
Approval: approval
Completed: completed
New: new
Under Progress: under progress
————<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/div>\n\n\n\n
<\/div>\n\n\n\n
<\/div>\n\n\n\n

Your table should look something like this in list view:<\/em><\/p>\n\n\n\n

\"\"
Access Monitor<\/em> table columns and fields<\/figcaption><\/figure>\n\n\n\n

Step 1: Creating a new Flow<\/h2>\n\n\n\n
\n
\n
\n

💡 The roles required to operate the flow designer are admin<\/strong>, flow_designer<\/strong> or delegated_developer<\/strong> with granted access to Flow designer in the developer permissions for the created app. Make sure you have one of these roles.<\/p>\n<\/div>\n<\/div>\n<\/div><\/div>\n\n\n\n

<\/div>\n\n\n\n

First we will navigate to the Flow designer. Go to Application Navigator> Flow Designer<\/em><\/strong>.<\/p>\n\n\n\n

On the Flow Designer, create a new flow. Next, you will be prompted to enter the flow designer properties as shown below.<\/p>\n\n\n\n

\"\"
Configure the Flow properties here<\/figcaption><\/figure>\n\n\n\n

Flow name :<\/strong><\/em> Issue Approvals<\/p>\n\n\n\n

<\/div>\n\n\n\n

Description :<\/strong><\/em> This flow will be used to update the states based on approvals for the Access Monitor.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Protection :<\/strong><\/em> (optional)<\/p>\n\n\n\n

<\/div>\n\n\n\n

Run as<\/strong><\/em> : System User<\/p>\n\n\n\n

<\/div>\n\n\n\n

Click on submit.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Step 2: Setting a trigger<\/h2>\n\n\n\n

We want to run this flow whenever a record is updated on the Access Monitor<\/em> Table on the condition that the State for the newly updated record is in Approval.<\/p>\n\n\n\n

For configuring the trigger, we start by selecting the Updated <\/em>option as shown in the image below.<\/p>\n\n\n\n

\"\"
Update <\/em>record trigger<\/figcaption><\/figure>\n\n\n\n

Next, we will be selecting our table from the dropdown and adding in our condition under Advanced Options<\/em>. Your trigger should look something like this:<\/p>\n\n\n\n

\"\"
Trigger Configuration<\/figcaption><\/figure>\n\n\n\n

The criteria for the flow to be triggered may not always be met. Sometimes, it may also get rejected if the state is not in approval. For this reason, we set the value of the Run Trigger<\/strong><\/em> as Only if not currently running<\/em>.<\/p>\n\n\n\n

Click Done after configuring.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Step 3: Observe Data pills<\/h2>\n\n\n\n

If you look at the Data panel of our flow now, you will notice that some values are present under the Trigger header. These values are called data pills<\/strong>. They act as dynamic data that will be utilized by our actions.<\/p>\n\n\n\n

\"\"
Reusable data pills that can be used from our trigger<\/figcaption><\/figure>\n\n\n\n

Step 4: Configuring an action<\/h2>\n\n\n\n

After configuring the trigger for the flow, we will be adding some actions which will be carried out if the condition of the trigger is met. The first action that we add is a request for approval. The person who is responsible for opening the issue (maintained in the Opened By<\/em> field in the Access Monitor table<\/em>) will have to approve\/reject the issue.<\/p>\n\n\n\n

To implement this, we click on the plus button for Action. Go into ServiceNow core<\/strong><\/em> and select Ask for Approval<\/strong><\/em>.<\/p>\n\n\n\n

\"\"
Ask For Approval<\/em> action in ServiceNow Core<\/figcaption><\/figure>\n\n\n\n

On selecting this, a form should appear on your screen for configuring the action. Drag and drop the Access Monitor record data pill into the Record field in the form. We will also configure our rules for this action with the help of the data pill picker<\/strong><\/em> as shown below.<\/p>\n\n\n\n