-
Notifications
You must be signed in to change notification settings - Fork 287
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
426d997
commit 63005af
Showing
8 changed files
with
67 additions
and
95 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
--- | ||
title: Understand the different action screens when integrating SAP with Power Platform. | ||
title: Understand the different action screens when integrating SAP with Power Platform (preview) | ||
description: Learn about the different action screens, and the configuration parameters for the available action screens when integrating SAP with Power Platform. | ||
services: '' | ||
suite: flow | ||
|
@@ -26,51 +26,17 @@ contributors: | |
- tapanm-msft | ||
--- | ||
|
||
**Cloud Flows – New Action for Complex APIs** | ||
# Understand the different action screens when integrating SAP with Power Platform (preview) | ||
|
||
|
||
|
||
**ADO IDs: **[Epic 13029270](https://dev.azure.com/msazure/One/_workitems/edit/13029270) | ||
|
||
**Owner:** [Jon Gilman](mailto:[email protected]), [David Galitsky](mailto:[email protected]) | ||
|
||
**Design, Research & XR Timelines:** Not applicable. | ||
|
||
|
||
|
||
**Why?** | ||
[This article is pre-release documentation and is subject to change.] | ||
|
||
Enterprise software systems like SAP and Oracle EBS have very complex APIs, often with 30-50 arguments and several hundred fields per argument. In some cases, an API can have 2,000 – 4,000 fields in the definition. The current flow maker throws an exception for such APIs and the maker then needs to manually research and fill the arguments in raw JSON. The goal of this enhancement is to dramatically improve this user experience. | ||
|
||
**Who?** | ||
|
||
We are targeting makers of PA flows at large enterprises. | ||
|
||
**Pre-Requisites** | ||
|
||
13029271 - New Data Sources Page | ||
|
||
**What?** | ||
|
||
The following screens are in scope for this enhancement: | ||
|
||
[Add Action Screen 2](add-action-screen.md) | ||
|
||
[Function Detail – Blank Screen 2](#_Toc1440640701) | ||
|
||
[Function Detail – Select System 2](#function-detail-–-select-system) | ||
|
||
[Function Detail – Select API 3](#function-detail-–-select-api) | ||
|
||
[Function Detail – Load API 3](#function-detail-–-load-api) | ||
|
||
[Function Detail – Select Parameter 5](#function-detail-–-select-parameter) | ||
|
||
[Function Detail – Enter Value 6](#function-detail-–-enter-value) | ||
|
||
[Function Detail – Completed State 7](#function-detail-–-completed-state) | ||
> [!IMPORTANT] | ||
> - This is a preview feature. | ||
> - [!INCLUDE[cc_preview_features_definition](../includes/cc-preview-features-definition.md)] | ||
# Add Action Screen | ||
## Add Action Screen | ||
|
||
For the initial rollout of the Complex API screen, we would like it to be launched when the maker clicks Add Action and selects one of the following: | ||
|
||
|
@@ -94,13 +60,13 @@ The new function detail screen will initially be blank with 4 main areas of user | |
|
||
![](media/action-screen/image2.png) | ||
|
||
# Function Detail – Select System | ||
## Function Detail – Select System | ||
|
||
When selecting the System, show a drop down containing the systems that have been configured on the Systems page per [13029271 - New Systems Page](https://microsoft.sharepoint.com/:w:/r/teams/prosipart/_layouts/15/Doc.aspx?sourcedoc=%7BCD9ACC94-CB5D-400F-B11C-DF766A5479FF%7D&file=13029271%20-%20New%20Systems%20Page.docx&action=default&mobileredirect=true&cid=ed822f63-007e-486a-a905-409ad5c202a0): | ||
|
||
![](media/action-screen/image3.png) | ||
|
||
# Function Detail – Select API | ||
## Function Detail – Select API | ||
|
||
Similar to the way Call SAP Function works today, display a list of APIs matching the user's text input after they have entered at least 3 characters. Depending on the system of record, use the following logic: | ||
|
||
|
@@ -110,7 +76,7 @@ Similar to the way Call SAP Function works today, display a list of APIs matchin | |
|
||
![](media/action-screen/image4.png) | ||
|
||
# Function Detail – Load API | ||
## Function Detail – Load API | ||
|
||
Once the user has selected the API, the definition of the API should be queried and the required Input and Output parameters should be loaded by default, as shown in the screen mockup below. Depending on the system of record, use the following logic: | ||
|
||
|
@@ -178,7 +144,7 @@ Value | |
|
||
![](media/action-screen/image5.png) | ||
|
||
# Function Detail – Select Parameter | ||
## Function Detail – Select Parameter | ||
|
||
When the user clicks into the Add New Parameter… drop down, display a list of valid parameters for the API, filtering out parameters that have already been added to the table. Depending on the system of record, use the following logic: | ||
|
||
|
@@ -188,7 +154,7 @@ When the user clicks into the Add New Parameter… drop down, display a list of | |
|
||
![](media/action-screen/image6.png) | ||
|
||
# Function Detail – Enter Value | ||
## Function Detail – Enter Value | ||
|
||
Within the Value column, the user needs to have the ability to use expressions, static values, dynamic values, and the following data operations: | ||
|
||
|
@@ -200,7 +166,7 @@ Within the Value column, the user needs to have the ability to use expressions, | |
|
||
![](media/action-screen/image7.png) | ||
|
||
# Function Detail – Completed State | ||
## Function Detail – Completed State | ||
|
||
The following example shows a state where a user has selected all the parameters needed to invoke the complex API: | ||
|
||
|
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
--- | ||
title: Understand the Data sources pane in Power Automate for SAP integration | ||
title: Understand the Data sources pane in Power Automate for SAP integration (preview) | ||
description: Learn about the Data sources pane in Power Automate to configure SAP integration | ||
services: '' | ||
suite: flow | ||
|
@@ -22,47 +22,25 @@ search.audienceType: | |
- enduser | ||
--- | ||
|
||
**New Data Sources Page** | ||
[This article is pre-release documentation and is subject to change.] | ||
|
||
|
||
|
||
**ADO IDs: **[Epic 13029271](https://dev.azure.com/msazure/One/_workitems/edit/13029271) | ||
|
||
**Owner:** [Jon Gilman](mailto:[email protected]), [David Galitsky](mailto:[email protected]) | ||
|
||
**Design, Research & XR Timelines:** Not applicable. | ||
|
||
|
||
|
||
**Why?** | ||
# Understand the Data sources pane in Power Automate for SAP integration (preview) | ||
|
||
Currently, connections in Power Automate are attached to specific users and cannot be shared across Flow makers. This makes it difficult for large organizations who have several Flow makers accessing the same enterprise systems. Additionally, when adding a new SAP data connection, many of the key connection parameters are missing for enterprise customers. In order to support Single Sign On and load balanced connections, some changes will need to be made. We are proposing a new page called Data Sources that allows IT admins to configure connection attributes as environment variables that can be shared across many Flow makers. | ||
|
||
**Who?** | ||
|
||
We are targeting makers of PA flows at large enterprises. | ||
|
||
**What?** | ||
|
||
3 pages within the Data menu of Power Apps and Power Automate: | ||
|
||
[Navigation Menu 2](navigation-menu.md) | ||
|
||
[Data Sources Page 2](#data-sources-page) | ||
|
||
[Data Source Detail Page 3](#data-source-detail-page) | ||
|
||
[Merging Connection Parameters at Run-Time 4](#merging-connection-parameters-at-run-time) | ||
> [!IMPORTANT] | ||
> - This is a preview feature. | ||
> - [!INCLUDE[cc_preview_features_definition](../includes/cc-preview-features-definition.md)] | ||
# Navigation Menu | ||
## Navigation Menu | ||
|
||
Add a sub-menu item beneath the Data menu item called Data Sources. On click of the menu item, the user should be navigated to the Data Sources page, where environment variables matching the following conditions will be displayed: | ||
|
||
- Type is JSON | ||
|
||
![](media/data-sources-pane/image1.png) | ||
|
||
# Data Sources Page | ||
## Data Sources Page | ||
|
||
Create a new Data Sources page that mirrors the layout of the Connections page, but with some key differences: | ||
|
||
|
@@ -82,7 +60,7 @@ Create a new Data Sources page that mirrors the layout of the Connections page, | |
|
||
![](media/data-sources-pane/image2.png) | ||
|
||
# Data Source Detail Page | ||
## Data Source Detail Page | ||
|
||
Copy the Connection Detail page but add some additional features: | ||
|
||
|
@@ -96,7 +74,7 @@ Copy the Connection Detail page but add some additional features: | |
|
||
When the user clicks Create or Save, the data from the System Detail Page should be saved to a JSON-type environment variable. | ||
|
||
# Merging Connection Parameters at Run-Time | ||
## Merging Connection Parameters at Run-Time | ||
|
||
Depending on the type of authentication used by an SAP customer, there will be session variables passed from Power Apps that need to be merged with the server-side connection parameters at run-time: | ||
|
||
|
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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