Microsoft Flow and PowerApps

In this example, we will create a flow which sends an email containing a parameter from a document in the email body once the flow is triggered from within WorkPoint.

In order to set up a flow, follow these steps:

1. On your WorkPoint solution, access the Office settings by clicking the dotted square icon in the top left of the solution.
2. Click the “Flow” button from the Apps menu.

3. From the Flow side menu, click the “My Flows”-button

4. From the list of Flows, click the “New”-button and choose how to create a new flow. In the following example the “Instant – from blank” will be shown.

5. In this example, the “Build an instant flow”-window is skipped as shown above. In case a custom name for the flow is preferred over the automatically generated one provided by Microsoft when this step is skipped, a name for the flow can be provided in the "Flow name"-field. In that case, "From Microsoft Flow" should be selected in the "Choose how to trigger this flow"-selection menu. Then click "Create".

6. In the following window, use the search field to search for “http”.
7. Select “when a HTTP request is received.

8. After the “When a HTTP request is received” step is created, add an additional step by clicking the “New step”-button. This is the step that makes possible the integration with WorkPoint.

9. In this example, the “Send me an email notification”-step is selected.

10. A text for the Subject has been typed in.
11. As an alternative to typing in the subject and body of the email to b e sent, dynamic content can be inserted by clicking the parameter from the right-most panel.

Once these steps have been set up, click the “Save”-button.

12. In the list of available Flows, which can be accessed from the “My Flows”-button in the left-most panel, the created Flow can be found. The name is auto-generated by the system, as we did not specify one before Step 5 in the “Flow name”-field.
13. Action relating to the Flow can be accessed through the “More commands”-menu.

14. IMPORTANT: When editing the created Flow and selecting the “When a HTTP request is received”-step, a HTTP POST URL is displayed. This URL is a requirement when setting up a Microsoft Flow in WorkPoint. It is therefore important to know how to acquire this URL. It is also important to note that this URL is only generated after the entire Flow including all steps have been saved.

In order to configure a Flow in WorkPoint 365, follow these steps:

1. In the WorkPoint 365 Administration, click the header of the business module for which you wish to set up the Microsoft Flow and PowerApps integration.
2. Click the “Microsoft Flow and PowerApps integration”-button from the drop-down menu.

3. Click the “New Flow”-button to add a new flow to the configuration.
4. Click the “New PowerApp” to add a new PowerApp to the configuration.

5. Tick on or off the “enable” checker to enable or disable this flow.
6. The flow can be given a title by filling in the “Title” field.
7. One or more translations for the title can be provided by selecting a language from the drop-down menu, and filling in the text field. Add more translations by clicking the "+" button.
8. The flow can also be given a flow description by filling in the “Description” field.
9. One or more translations for the flow description can be provided by selecting a language from the drop-down menu, and filling in the text field. Add more translations by clicking the "+" button.
10. Insert the Http Post URL for the flow you wish to run. This step presupposes that a flow has been set up, which generates a Http Post URL. Steps to locate the Http Post URL are outlined in section 3.1.
11. The “List” field determines the list from where it should be possible to run this flow.
12. Check the "Multiple documents selection support" if this flow should be executable while having multiple documents/files selected.
13. In the “Parameters” field, add the fields you wish to include in the flow. These can be from both the entity or document. To add a parameter, click "Add Parameter". The following interface opens for adding a parameter:

For "Type", the following options are available:

• Document Field (used for parameters which pulls data from a field on a document)
• Entity Field(used for parameters which pulls data from a field on an entity)

The "Source Field" options depend on the Type selected. Source fields are fields in WorkPoint from which data can be pulled.

The Parameter Name can be set in the "Parameter Name" field.

Click the "Add Parameter" button once the parameter is configured to add it to the list of parameters.

13. The “Permission” field determines which level of access to the document a user must have in order to be able to start the flow.

Once the configuration is finished, click the “Save”-button. Alternatively, cancel the configuration by clicking the “Cancel”-button.

Please note that the “Send to” button from which Flows and PowerApps are run will not appear before the WorkPoint 365 Browser Cache is cleared. This can be done by following these steps:

1. On the WorkPoint solution, click the “Home”-button.
2. In the bottom of the menu, click the “Need help?”-button.
3. Click “Clear WorkPoint browser cache”.

After having configured both a Microsoft Flow and the integration with WorkPoint in sections 3.1 and 3.2, a test can be performed to see if the integration was successful. To do this, follow these steps:

1. Click the header of the business module for which the integration has been set up.
2. Click the “Microsoft Flow and PowerApp integration”-button.

3. Click the “Edit”-button for the Flow you have created. The following edit window should open:

Now, in a separate internet browser tab, perform the following steps:

3. In the Microsoft Flow page (www.flow.microsoft.com), navigate to the “My flows”-page.
4. Click the “Edit”-button for the flow that was configured earlier. The following edit page should appear:

5. In the editing page shown in the image, click the header of the “When a HTTP request is received.
6. Make sure that the URL in the HTTP Post url field matches the link that was put inside the Flow configuration in WorkPoint (7)

8. After validating that the two URLs match, click the “Test”-button in the top right of the Flow editing page.

9. Check “I’ll perform the trigger action”.
10. Click the “Test”-button.

The Flow edit page will turn blank with a turning-wheel spinning, awaiting some trigger. Now back in the edit page for the WorkPoint Flow configuration, follow these steps:

11. Click the “Test”-button from the WorkPoint Flow configuration page.

12. If there is no text inside the JSON Sample box, try clicking the “Reset”-button (13).

14. Click the “Test”-button to perform the test.

The test should now run, and on a successful test, the following page should appear in the Microsoft Flow edit page:

Note the yellow bar in the top with the text saying “Your flow ran successfully”. If the configuration of the Microsoft Flow was performed as shown in section 3.1, you should also receive an email containing the body of the JSON Sample.

WorkPoint has developed an action called a "Notify WorkPoint365 Web Hooks". This action can be added to a WorkPoint Trigger. When this action is triggered in WorkPoint, it will also trigger the execution of a Microsoft Power Automate flow if the Power Automate flow trigger "Triggers when a WorkPoint event occurs" is used.

In practice, one would create an action of type "Notify WorkPoint365 Web Hooks" in WorkPoint 365 like so:

1. In the Action Management page in the WorkPoint Administration, select the "Notify WorkPoint365 Web Hooks" action in the drop down menu.
2. Click the "Add button".

3. Provide a title for the action.
4. Set the action to "Active".
5. Click the "Save" button.

6. Add the "Notify WorkPoint 365 Web Hooks" action to a trigger. In this case, we add the action to an already existing trigger, which also locks an entity.
7. Click the "Update" (or "Save") button.

In a Power Automate flow, we can use the "Triggers when a WorkPoint event occurs" trigger, to execute based on the trigger in WorkPoint 365:

8. In the Power Automate flow, we provide the "Triggers when a WorkPoint event occurs" trigger with the URL of the solution in question.
9. We select the business module for which the trigger is set up.
10. We select the trigger which contains the "Notify WorkPoint 365 Web Hooks" action.
11. Optionally, we can add a description for the trigger.
12. Now we can add more steps to the Power Automate flow to create functionality. This flow now triggers when the WorkPoint trigger is used to lock an entity on the "Projects" module.

In order to create a Microsoft PowerApp, follow these steps:

1. On your WorkPoint solution, access the Office settings by clicking the dotted square icon in the top left of the solution. If present, click the “Power Apps”-button.
2. If the “Power Apps”-button is not present in the list of apps, click the “All apps”-button and search for “Power Apps”. Click the “Power Apps”-button.

3. From the Microsoft Power Apps page, click the “Create”-button in the left-most panel.
4. Select the “Canvas app from blank”-button

5. Give the app some name. This name should be easily identifiable for later use.
6. Select the format for the Power App. In this example, the "Phone" format is selected. In "Phone" format, the Power App is displayed in a portrait format. A Tablet layout will make the Power App display is a landscape format.

7. From the PowerApps welcome message window, select “Create a form”.

8. Select each pre-existing element in the form and delete them. Then add a Text input to the form

9. The Text input field is created in the form.
10. In the properties panel in the right-side panel, the advanced tab allows for different parameters and elements of the Text input field can be assigned.
11. In the “Data”-section, the “Default”-field default value has been substituted with “Param(“Document_DocName")". This indicates that we eventually want to insert data from a parameter titled “Document_DocName” from the WorkPoint solution from which we want to run this PowerApp.

12. Navigate to the “File”-menu.
13. Click the “Save as”-button from the menu.
14. Give the PowerApp a title.
15. Click the “Save”-button.

16. Now access the Office 365 settings by clicking the dotted square icon.
17. Click the “All apps”-button.

18. Click the “PowerApps”-button.

19. Note that the newly created PowerApp exists in the list of apps. In order to view the detail of this app, first select it.
20. Click the “More commands”-button.
21. Click the “Details”-button from the menu.

22. IMPORTANT: In the Details page, the App ID is shown. This App ID is a requirement when setting up a Microsoft PowerApp in WorkPoint. It is therefore important to know how to acquire this App ID.

In order to configure a PowerApp in WorkPoint 365, follow these steps:

1. In the WorkPoint 365 Administration, click the header of the business module for which you wish to set up the Microsoft Flow and PowerApps integration.
2. Click the “Microsoft Flow and PowerApps integration”-button from the drop-down menu.

3. Click the “New Flow”-button to add a new flow to the configuration.
4. Click the “New PowerApp” to add a new PowerApp to the configuration.

5. Tick on or off the “enable” checker to enable or disable this PowerApp.
6. A title for the PowerApp can be provided in the text field
7. One or more translations for the PowerApp title can be provided by selecting a language from the drop-down menu, and filling in the text field. Add more translations by clicking the "+" button.
8. The PowerApp can also be given a description by filling in the “Description” field.
9. One or more translations for the PowerApp description can be provided by selecting a language from the drop-down menu, and filling in the text field. Add more translations by clicking the "+" button.
10. Insert the App ID of the PowerApp that you wish to run. The details on how to acquire the App ID are detailed in section 3.3.
11. The “List” field determines the list from where it should be possible to run this PowerApp
12. In the “Parameters” field, add the fields you wish to include in the PowerApp. These can be from both the entity or document. To add a parameter, click "Add Parameter". The following interface opens for adding a parameter:

For "Type", the following options are available:

• Document Field (used for parameters which pulls data from a field on a document)
• Entity Field (used for parameters which pulls data from a field on an entity)

The "Source Field" options depend on the Type selected. Source fields are fields in WorkPoint from which data can be pulled.

The Parameter Name can be set in the "Parameter Name" field.

Click the "Add Parameter" button once the parameter is configured to add it to the list of parameters.

13. The “Permission” field determines which level of access to the document a user must have in order to be able to start the PowerApp.

Once the configuration is finished, click the "Save" button.

Please note that the “Send to” button from which Flows and PowerApps are run will not appear before the WorkPoint 365 Browser Cache is cleared. This can be done by following these steps:

1. On the WorkPoint solution, click the “Home”-button.
2. In the bottom of the menu, click the “Need help?”-button.
3. Click “Clear WorkPoint browser cache”.

After having configured both a Microsoft PowerApp and the integration with WorkPoint, you can perform a test to see if the integration was successful. To do this, follow these steps:

1. In a documents library on the business module for which Microsoft PowerApps integration has been performed, select a document.
2. Click the “Send to”-button from the commands-panel.

3. Select the PowerApp that was configured.

4. WorkPoint displays a side panel which displays the PowerApp in the configuration which was created from within the Microsoft PowerApps interface.

WorkPoint supports integration with various aspects of the Microsoft Power platform. There may, however, also be certain aspects of this platform which are not yet supported by WorkPoint.

The purpose of this white list is to provide information about which aspects of the Microsoft Power platform are supported by WorkPoint - "supported" meaning that these a tested and verified to work with WorkPoint.