Our iManage Work connector offers a couple of triggers to start a Power Automate flow. These triggers let users start a Power Automate flow on a document or documents using the Work Web context menu of a document. The following table describes each trigger.

Table: Trigger and use case

Get started with triggers

Both the For a selected document and For multiple selected documents triggers are available as part of the iManage Work connector for Power Automate. When it's ready for use, the Start a Workflow option must be added to the context menu in iManage Work. For more information about editing the context menu, refer to Context Menus in the iManage Control Center documentation.

Activation

After it’s added, the menu item is displayed to all users, but the permissions for a given workflow are configurable. If there are no available workflows for a given user or document, the “No workflows available for the selected item” message is displayed to users after they select Start a Workflow.

After activation in your environment:

• iManage Work users can use this trigger to create a workflow that is displayed only to them or in workspaces they own.

• Administrators (members of the NRTAdmin group) or support staff (users with Tier 1 or Tier 2 privileges) can use this trigger to create workflows for other users, groups, or workspaces. Workflow creators can limit a particular workflow's availability to certain Library IDs, Users, Groups, Workspaces, or Document Classes.

• After a workflow is made available to a given user, the overflow is available for the documents that they have Read/Write or Full Access to. This behavior prevents scenarios in which a flow can edit a document that a user doesn't have permission to edit because the flow runs under the credentials of the flow creator.

Build your flow

To create a workflow that uses the For a selected document or For multiple selected documents trigger:

1. Go to http://make.powerautomate.com and select +Create.

2. Create an Automated cloud flow.

3. To view all the available iManage Work triggers, search for iManage Work.

4. Select the For a selected document or For multiple selected documents trigger.

5. For the For a selected document or For multiple selected documents trigger, specify the following:

   1. Workflow name: Provide the name that users will select when they want to trigger the workflow.

   2. Description: Provide a detailed description of the workflow for users.

   3. Library ID: Select what library the workflow will apply to. You'll need to copy and publish the flow for multiple libraries if you wish to have the same flow run in multiple libraries.

   4. Form ID: Select a form you’ve built in iManage Workflow Manager, or select None.

   5. Return Folder ID:

      • Set to Yes if you need to use the folder ID as part of the logic for the rest of your flow. If there's potential ambiguity because the document is in multiple locations, the user is prompted to select the folder they intend to run the workflow from.

      • If your workflow doesn't use the Folder ID of the document, leave this field as No to provide faster response times for users.

   6. Available to Users, Available to Groups, Available In Workspaces, and Document Classes: Use these options to filter the kind of documents and users for whom workflow is displayed. Either of the Available to users or Groups filter is needed. Else, the workflow fails.

   7. Wait For Completion: This field lets you provide feedback on the actual Power Automate run status to the user:

      • If set to No, the user is quickly informed that the flow has started and that it won't wait for any status from the Workflow. Use this if the owner of the Power Automate flow is responsible for errors or issues reported by the flow. This should be used in most scenarios.

      • If set to Yes, you can provide actual workflow status to the user in various scenarios if it completes fast enough. You must use the Update workflow state action for all logical conclusions of your workflow.

        • If the flow takes longer than 60 seconds or you’re missing the Update workflow state action, then the user is informed that the flow is taking longer than expected. This should be used primarily in scenarios in which a known error can occur quickly and this feedback belongs with the user.

If the Start a Workflow menu is added to the context menu in your iManage Work environment, the workflow is made available to users as soon as you save the workflow in Power Automate.