Power Automate Custom Connector¶
Follow these steps to install & use the custom connector for Power Automte
Installation¶
Before performing these steps, you will need the OpenAPI specification for docCentrum available here:
https://cdn.mercuryintranet.com/modern-mercury-apps/doccentrum/doccentrum.minimal.openapi.json
You may then want to this file as the icon:
https://cdn.mercuryintranet.com/modern-mercury-apps/doccentrum/DcLogo.png
Note
If you are performing an upgrade of a connector, you may find it easier to use this YAML file:
https://cdn.mercuryintranet.com/modern-mercury-apps/doccentrum/doccentrum.minimal.openapi.yaml
Then, you will need to create an App Registration for authenticating to docCentrum. Follow the steps on this page, keeping note of the following parameters:
- Tenant ID
- Client ID
- Client Secret
Access Power Automate
- From the
Datamenu item, select `Custom Connectors - Click
+ New custom connectorfrom the top right - Choose
Import an OpenAPI fileoption - Give the connector the name
docCentrum API - Click Import then choose the Open API specification file you downloaded from the URL above
- Click
Continue - On the
Securitypage, enter the Authentication details as described on the API access page. - Click
Update connectorfrom the top of the screen
The connector is now available to use.
It will present a ReplyURL that you must add as a Web Platform Reply URL to the app registration that you created in the previous sections.
Usage¶
The connector is added to a Power Automate flow like any other, but it will be shown in the Custom tab when choosing a flow action.
When you first use the connector, you will have to create a connection, the interface will guide you, and normally your currently logged in session should suffice for access to be able to create a connection for the connector to use.
Actions¶
Create a new Simple Document Read Request¶
This action creates a document read request. The following fields are available
| Field Name | Description |
|---|---|
| itemPath | The URL that the user will be navigated to when opening the task |
| itemTitle | The Item's Title |
| description | The Item's description |
| groupId | The GUID identifier of a Microsoft 365 Group. This task will be issued to each member |
| priority | Set to High, Medium or Low |
| dueDate | The date that the task must be completed. Enter an ISO8601 date and time string here, complete with zulu time component |
| quizId | The ID of a quiz to associate with this task |
| isMandatory | Set to Yes or No to make the task a mandatory or a recommended task |
| itemType | Set's the item type. Used primarily to drive the icon shown in user interfaces |
| assignedBy | This is the UPN of the user who will show as the one that assigned the task |
| templateGroup | The name of the template group to use for the notifications |
| assignmentId | Optional. A GUID that identifies this batch of requests. Useful when creating tasks as part for a ForEach |
| taskGroupName | Optional. A free-text string that identifies this batch of requests. |
| source | Optional. The application or programme that created this task. |
| upn | The user principal name of the user who will recieve this task. Add multiple recipients by separating them with a semicolon. |
Create Tasks from Package¶
This action will use an existing Task Package to create a collection of tasks for a given selection of users
| Field Name | Description |
|---|---|
| packageId | The GUID of the task package, taken from the Admin center |
| users | A collection of User Principal Names (UPNs) to issue the tasks to |