You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-1
Original file line number
Diff line number
Diff line change
@@ -499,10 +499,26 @@ As you might have discovered, the solution needs to implement an iteration over
499
499
picture below is the expected result omitting some details
500
500

501
501
502
-
We will not go into the details of the solution implementation [here](solution/logic), but there are definitely other alternatives for the json array transformation. Feel free to explore the solution and the workflow actions used there.
502
+
We will not go into the details of the solution implementation [here](solution/logic), but there are definitely other alternatives for the json array transformation. Feel free to explore the solution and the workflow actions used there.
503
+
1. Clone this repository
504
+
2. change the current directory to
505
+
json-transformation-logicapp/solution/logic
506
+
3. start VS Code with "code ."
507
+
4. start Azurite from the VS Code command palette
508
+
5. start the Logic App
509
+
6. select ECO2MBO folder and the workflow.json file there and call from the context menu "overview" and copy the workflow endpoint URL from there
510
+
7. create a test.http file as it was done above and provide the [ECO payload](eco-payload.json) and the endpoint URL for the POST request
511
+
8. run the http POST request and see the result
512
+
9. go to the "overview" context menu of the workflow, refresh the run history, select the latest run and navigate through the actions results to better understand the workflow logic
513
+
10. switch to the context "Open in Designer" from the workflow.json and have a look at the workflow design.
503
514
504
515

505
516
517
+
Since we gave each action a custom name and the symbols are looking similar, go to the "About" section of the actions to see the type of action. Here is an example:
518
+

519
+
520
+
521
+
506
522
---
507
523
**NOTE**
508
524
The real solution does not return the result as an HTTP response, but rather sends it to the MBO service
0 commit comments