Use Case - Creating a Custom Settings Page for a Workflow

Automate the activation of a routing logic by service team members.

The Problem: Agents are only members in a service team and - as per default permissions - cannot change the service configuration.

In some cases you want them to activate or deactivate a routing logic. For instance a field technician discovers a defect that requires immediate global system maintenance and subsequent service outage. To react to this, the IT administrator enables an announcement to all customers in the hotline, informing about the planned outage. In this use case, we want to automate the activation of such an announcement.


For this Use Case you need:

  • Power Automate Premium subscription (for the "SharePoint" Element). 
  • The Team Owner to share a "flow configuration file" with the team which contains the different announcement tests. → More on this in the steps below.

Show Icon Legend

💡 = A hint to signal learnings, improvements or useful information in context. 🔍 = Info points out essential notes or related page in context.
☝ = Notifies you about fallacies and tricky parts that help avoid problems. 🤔 = Asks and answers common questions and troubleshooting points.
❌ = Warns you of actions with irreversible / data-destructive consequence. ✅ = Intructs you to perform a certain (prerequired) action to complete a related step.

Create and share the configuration file in MS Teams

✅ Within your teams channel:

1. Create a list in Sharepoint with the following columns: 

Title Name (for consistency this should be equal to the Custom Context Parameter name in Nimbus that we'll create in the next step)
Active Toggle for true/false
Text Description of the incident

2. Share the list in your Teams channel and instruct your administration team as follows:

  1. This list is a set of configuration parameters used in the workflow. It will act as your "incident notification settings" page. ☝ Everybody who has access to this list can influence the workflow. Please make your team aware of this when sharing this list.
  1. Technicians can set "IncidentAlert" to true in order activate it and play the announcement activity in your service's Workflow. When set to false the announcement is deactivated.

Create the workflow in Nimbus

✅ Use a custom configuration inside a workflow

  1. Create a Custom Context Parameter"IncidentAlert" and set it to "false" as per default.
  2. In the workflow, we need to check the parameter with the "Check Parameterworkflow activity.

💡 This performs our incident check, followed by an "Announcement" activity before calls enter the queue. 

Create a Flow to retrieve the announcement

✅ On each new call that enters the service line we check the value from the SharePoint list and update the call task in Nimbus with the current value.

Overview of the flow

  1. Start your flow with the a "GetOnNewTasks" Nimbus activity.
  2. Add a SharePoint "Get items" element to the flow and read out the list.
    1. Select the list location (e.g. placed in your Team)
    2. Set the query to Title eq 'IncidentAlert'. Make sure this column title is correct and stays unchanged.
    3. In this example we set Top Count to 1 because there is only one entry in the list.  

Update the Nimbus task

✅ Next we update Nimbus with the SharePoint data

  1. Add an Nimbus "UpdateTask" step to the flow
  2. Set the value of the CustomContextParameter with name "IncidentAlert" to the value from the SharePoint list.

💡 There you go, you can test your flow!

Test the flow

  1. Log-in on a mobile phone and open the shared list file.
  2. Change the value in the file and test your flow with a service call.
Mobile view of the SharePoint TAB
Edit view
Edit View

Table of Contents