Teams notification


We sent to a production instance a custom app where employees can inform webinars they attended, courses, ticket numbers that they solved recently, certifications, and so on.

Each semester managers evaluate that information in order to pay bonuses.

A manager with only one team can have five to twelve employees. And sometimes a manager can have two or more teams.

When each employee sends the form, his/her manager needs to validate it so the system calculates a number of points.

The problem:
Managers don't want to access the platform every day to see if there are submissions to validate. It would be better to receive a smartphone notification when there were pending records.

The solution:
To send notifications to their smartphones we created a Flow using App Engine Studio.
When a manager receives a notification, we make sure that there is an employee record to validate in the platform.

What are the steps to accomplish this integration?
  1. In Microsoft Teams we are going to create a webhook, which is a web address to be used in the next step;
  2. Using the App Engine Studio we will create a Flow that will be triggered when the employee saves the record. When the record is saved, we will send a message to the Teams channel.

1) Creating the webhook

1.1) A team can have many channels. In your corporate Microsoft Teams, choose a channel to be used, and in the top right corner click on the three points (more options) icon;
1.2) Click on Connectors.








1.3) In the "Incoming Webhook" connector, click on [Add].



















1.4) In the configuration screen, inform:
Any name for your webhook;
(Optional) You can click on [create] if you like to upload an image as an icon for your webhook. If you do that, every message will contain that image.


















1.5) This step is done! Copy the Webhook address because we will use it in step 2.


















2) Creating a Flow

Objective:
Every time an employee creates a record in your App table, you will send a Teams notification to his/her manager.
In the Automation of your Application, create a Flow.

2.1) The unique mandatory field is the Flow name. Click on [Submit]
2.2) For the trigger, select Record > Created
2.3) Select your Table and click [Done]
      Your Flow name;
      A description about what the flow does;
      Application: Select your app;
      Protection: -- None --
      Run As: User who initiates session
      Click on [Submit]

















2.4) For the Trigger, select Record > Created











2.5) Select your Table and click [Done]











2.6) In the ACTIONS section, choose [Post a Message]. The remaining parameters will be:
      Webhook URL: Use that copied in step 1.
      Title: Inform your notification title.
      Message: Type the message to send. You can use fields from the record being created.
      Click on [Test] to see what your notifications will look like.
      When you are happy with the look and feel of your message, click on [Activate] to activate your Flow.


Thank you.

Comments

Post a Comment

Popular posts from this blog

Hacktoberfest

Image
I just completed the #ServiceNowHacktoberfest by having 4 contributions accepted! - Service Portal is a single place for everyone to access information, services and different applications. For my first contribution   (1068)  I shared a use case to get a parameter from the URL and use it into an Ajax call, recovering information from the database to show within the User Interface. - For my second pull request   (1069) I talked about best practices, explaining how to safely update a record. If we're not cautious with this kind of programming we can accidentally insert records instead of updating them. - For my third contribution   (1085)  I explained how to validate a field provided within a Catalog Item/Record Producer so that the date can't be in the past.  - The last one   (1093) was about fixing a direct reference to the Choice table. This is an internal table and it is not best practice to reference that table directly when you are crea...
Read more

VIDEO How to fix a reference to the Choice [sys_choice] table

Image
        The Choice table is used internally by the platform and depending on the payload of an operation, for performance reasons the platform can decide that it is better to drop the table and insert all the values instead of perform updates on specific records.       When we insert a new record in a table, a new sys_id is generated. If we have the Choice table as a reference to provide choices for a particular field in our table, these choices will be lost every time the platform decides to recreate the Choice table.       A simple way to avoid this problem is to create a field of  type Choice  which indirectly uses the Choice table but it is the right way, or we can create our own table to maintain the Application choices.       Recently I received the mission to do exactly this: create a private choice table for an Application.    ...
Read more

How to hide a Related List

Do you know about the Related List that displays people who can approve or reject a document? Recently a scenario came up where the developer needed to prevent the employee who created a record from approving that document. It wasn't common because usually the operational level creates the document while a manager approves it. Leaving this question of personas aside and focusing on the problem, what would be a possible solution? The first workaround that came to my mind was to hide the Approval list if the user who registered was viewing his own record. A workaround is not the ultimate solution. Just a palliative fix while we find time to think about the ideal one. The action plan 1) Every record has a field called sys_created_by; 2) On the front-end (client side) we have access to an API called Glide User that has some information about the logged in user. Among them is the name in the userName property. What if we create a ...
Read more