chore: PowerApps update for Batch Approval workflow and security roles #466
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SolomiiaSnihur
previously requested changes
Jun 3, 2024
| @@ -19,11 +19,15 @@ This feature allows you to sync CluedIn entity types, vocabularies, and vocabula | |||
|
|
|||
|  | |||
|
|
|||
| Another way to Enable this feature is to Navigate to **Management** > **Entity Types**, select the Entity Type you want to sync and Enable the Sync **CluedIn Entity Types to Dataverse Table** in the settings. | |||
There was a problem hiding this comment.
Suggested change
| Another way to Enable this feature is to Navigate to **Management** > **Entity Types**, select the Entity Type you want to sync and Enable the Sync **CluedIn Entity Types to Dataverse Table** in the settings. | |
| Another way to enable this feature is to navigate to **Management** > **Entity Types** and select the entity type that you want to sync. Then, select **Edit** and turn on the toggle for **Sync CluedIn Entity Types to Dataverse Table**. Finally, save changes. |
| @@ -4,40 +4,26 @@ nav_order: 30 | |||
| parent: Features | |||
| grand_parent: Power Apps Integration | |||
| permalink: /microsoft-integration/powerapps/features/create-workflow | |||
| title: Create Power Automate workflow | |||
| title: Create Ingestion Endpoint workflow | |||
There was a problem hiding this comment.
Suggested change
| title: Create Ingestion Endpoint workflow | |
| title: Create an ingestion endpoint workflow |
| tags: ["integration", "microsoft", "powerapps", "dataverse"] | ||
| last_modified: 2023-05-17 | ||
| --- | ||
|
|
||
| This feature allows you to automate the creation of Power Automate workflow that will send the data from Dataverse to CluedIn via ingestion endpoint. | ||
| This feature allows you to automate the creation of workflow that will send the data from Dataverse to CluedIn via Ingestion Endpoint. |
There was a problem hiding this comment.
Suggested change
| This feature allows you to automate the creation of workflow that will send the data from Dataverse to CluedIn via Ingestion Endpoint. | |
| This feature allows you to automate the creation of workflow that will send the data from Dataverse to CluedIn via ingestion endpoint. |
| last_modified: 2023-05-17 | ||
| --- | ||
|
|
||
| This feature enables you to automate the creation of the workflow for the batch approval process. If we process the data (regardless of the source) and the system identifies that the EntityType used has been tagged for the Approval Process, the data will be halted and the approval process will start and wait for the User/s approval before we continue the data processing. |
There was a problem hiding this comment.
Suggested change
| This feature enables you to automate the creation of the workflow for the batch approval process. If we process the data (regardless of the source) and the system identifies that the EntityType used has been tagged for the Approval Process, the data will be halted and the approval process will start and wait for the User/s approval before we continue the data processing. | |
| This feature enables you to automate the creation of the workflow for the batch approval process. If you process the data (regardless of the source) and the system identifies that the entity type used has been tagged for the approval process, the data will be halted, and the approval process will start and wait for the user's approval to continue the data processing. |
Comment on lines
16
to
17
| - Dataverse Connection | ||
| - Approval Connection |
There was a problem hiding this comment.
Suggested change
| - Dataverse Connection | |
| - Approval Connection | |
| - Dataverse connection | |
| - Approval connection |
| - The **CluedIn Approval Queue ID** is the Id of the Data that we are trying to approve in this process. _(A page to show this data in CluedIn is coming soon)_. | ||
|  | ||
|
|
||
| ### Workflow |
There was a problem hiding this comment.
Suggested change
| ### Workflow | |
| **Workflow** |
|
|
||
| ### Workflow | ||
|
|
||
| - The content of the approval workflow will be composed of events such as condition, Approval, variables and HTTP. A 60-second cycle will occur to check if there is data in **Approval Queue** table. Once we recieve a response in the Approval Process, we send the Approval details together with the CluedIn Approval Queue IDs to the CluedIn API via HTTP event. |
There was a problem hiding this comment.
Suggested change
| - The content of the approval workflow will be composed of events such as condition, Approval, variables and HTTP. A 60-second cycle will occur to check if there is data in **Approval Queue** table. Once we recieve a response in the Approval Process, we send the Approval details together with the CluedIn Approval Queue IDs to the CluedIn API via HTTP event. | |
| The content of the approval workflow will be composed of events such as condition, approval, variables, and HTTP. A 60-second cycle will occur to check if there is data in the **Approval Queue** table. Once we receive a response in the Approval Process, we send the Approval details together with the CluedIn Approval Queue IDs to the CluedIn API via an HTTP event. |
|
|
||
| - The content of the approval workflow will be composed of events such as condition, Approval, variables and HTTP. A 60-second cycle will occur to check if there is data in **Approval Queue** table. Once we recieve a response in the Approval Process, we send the Approval details together with the CluedIn Approval Queue IDs to the CluedIn API via HTTP event. | ||
|
|
||
|  |
There was a problem hiding this comment.
Suggested change
|  | |
|  |
Comment on lines
39
to
40
| ### Notifications | ||
| - Once the Automation has been done, you can expect a notification for creating the Approval Queue Table/Columns and the creation of the Batch Approval Workflow. |
There was a problem hiding this comment.
Suggested change
| ### Notifications | |
| - Once the Automation has been done, you can expect a notification for creating the Approval Queue Table/Columns and the creation of the Batch Approval Workflow. | |
| **Notifications** | |
| Once the Automation has been done, you can expect a notification for creating the Approval Queue Table/Columns and the creation of the Batch Approval Workflow. |
| tags: ["integration", "microsoft", "powerapps", "dataverse"] | ||
| last_modified: 2023-05-17 | ||
| --- | ||
|
|
There was a problem hiding this comment.
Suggested change
| ## On this page | |
| {: .no_toc .text-delta } | |
| 1. TOC | |
| {:toc} | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Work Item ID: No associated PBI
How has it been tested?
Visual Studio Code - View Mode