Power Platform connector

With the Power Platform connector, you can use Power Automate, Power Apps, or Azure Logic Apps to automate actions in Alvao or to integrate Alvao with other applications.

Installation

1. Decide which authentication mode the connector will use: OAuth 2.0 (recommended) or Basic authentication.
2. For OAuth 2.0, in your Microsoft Entra choose an existing app or register a new app for the connector.
3. In Alvao, create an application account representing Power Platform and grant needed permissions to it.
   1. In Administration - Users, use the New user command. Fill in the following fields:
      • Name and Surname, e.g., Power Platform
      • User name, e.g., Power Platform
      • In Application account, for OAuth 2.0 check the Microsoft Entra application option. For basic authentication check the Other applications option.
   2. In the case of basic authentication, select the created user in the table and use the ... - Change password command to set the user password.
   3. Assign roles to the account with the Edit - Service team roles command. Use the Reader role or Manager role to grant read or update permission respectively.
4. To install the connector in Power Automate, use the following procedure. For Power Apps and Azure Logic Apps, the procedure is similar.
   1. Download and unzip the archive ALVAO.PowerPlatform.CustomConnector.zip.
   2. Log in to your Power Automate.
   3. Click on the More - Discover all button.
   4. Use the Data - Custom connectors - New Custom Connector - Import an OpenAPI file command.
      1. Set the Custom connector title, e.g. ALVAO.
      2. Select the ALVAO.PowerPlatform.CustomConnector.swagger.yaml file from the downloaded archive and click Continue.
      3. On the General tab:
         • Upload ALVAO.PowerPlatform.CustomConnector.icon.png as the icon.
         • Set the Icon background color to #FFFFFF.
         • Set the Host and Base URL to your Alvao REST API url.
         Note:

         If you don't have your REST API exposed to the internet, you need to connect via an on-premises data gateway. For setting up the gateway, see Install an on-premises data gateway.
      4. On the Security tab, select the authentication mode chosen above.
      5. When using OAuth 2.0:
         • Select Identity Provider as Azure Active Directory (Microsoft Entra ID).
         • Set the Client ID to your Entra ID registered app.
         • Set the Resource URL to your Alvao Application ID URI.
         • After the creation of the custom connector, add the generated Redirect URL to the list of URLs in the registered application in MS Entra.
      6. Click on the Create connector button. For more information, see Create a custom connector from an OpenAPI definition.
      7. On the Test page:
         1. Select New connection:
            • Select the authentication method and provide access credentials if needed.
            • Click on the Create connection button.
         2. As an operation select GetTicket.
         3. Enter the ticket ID of an existing ticket.
         4. Click on the Test operation button.
         5. Status code 200 should be returned.
      8. Now, when adding an operation to your flow, you can see the ALVAO connector on the Custom tab in the designer.

Actions

For more details, see the interface specification.

Custom fields

The connector also supports reading and writing values from/to ticket custom fields. Custom fields can't be described in the general connector definition, so you need to use the following techniques for processing them.

To read the value of a ticket custom field, use expressions in the Get ticket action. E.g., to read the value of the TicketCategory field, use the expression:
outputs('Get_ticket')?['body/customItems/TicketCategory/value']

To write a value in a ticket custom field, use the Update ticket action with a custom JSON specification. E.g., to write the "monitor failure" value in the TicketCategory field, use this specification in the Custom Items field:

{
  "TicketCategory": {
    "@@odata.type": "#Alvao.Rest.Api.Models.SD.CustomItem",
    "name": "TicketCategory",
    "value": "monitor failure"
  }
}

Triggers

The following triggers supported by the connector are available in Power Automate flows.

Extended triggers

Apart from the triggers supported by the connector, with the ALVAO Asset Management Custom Apps module, or ALVAO Service Desk Custom Apps module, you can also trigger a Power Automate flow directly from the code of any Alvao application.

Example:

1. Log in to your Power Automate and import the package ALVAO.PowerPlatform.FlowTemplate.zip, which is part of the connector package.
2. In Alvao - Administration - Applications, use the Import command to import the ALVAO.Application.RunFlowOnTicketStateChange.xml file.
3. In Administration - Custom fields create a new custom field of the ticket status entity:

   Name	Type	Length	Table	Column
   Run flow (URL)	nvarchar	2048	TicketStateCust	RunFlowUrl

4. In Power Automate, copy the HTTP POST URL from the "When an HTTP request is received" trigger of the flow.
5. In Alvao - Administration - Processes, select the process for which tickets you want to be triggering the flow. Use the Edit - Solving process command, select the particular status, click the Modify status icon, and in the Other section, paste the trigger URL to the field Run flow (URL).
6. In Administration - Applications, enable the sample application.

The application triggers the flow whenever a ticket transits to a ticket status with the trigger URL in the Run flow (URL) field.
After that, the application logs a record "Flow was triggered" in the detailed log of the ticket.

Did not find what you were looking for? Ask our technical support team.