Logic Apps never cease to surprise us with new features, and it seems like things are moving at an increasingly faster pace when it comes to cool new updates.
You might have noticed this feature last year, but it didn’t stick around for long. Chances are, it disappeared due to a recent update.
What this feature can do is, can help you document your workflow and create a .md file out of it with the click of a button.
The feature I’m talking about is called Workflow Summary, and it’s a real game-changer. With just a click of a button, it uses AI to generate a .md file documenting your workflow. Sure, you might need to tweak or add a few things, but in terms of architecture documentation, this is a huge step forward. It helps developers work faster and deliver more value to companies.
So, how can you access this feature? I have two answers for you:
You can’t!
If you’re looking for it in your current Designer, it’s probably not there. But don’t worry—if you stumble upon this post a few months (or even days) from now, there’s a chance this feature might be re-enabled in the designer. Keep an eye out!
And yes, you can!
You can access it by following this link: aka.ms/emastaging
Once you open your Logic App Standard in the designer, you’ll find the Workflow Summary feature in the top menu.
Be sure to use it with caution and always review the content once it’s generated.
Here’s an example of what a Logic App document looks like once created with this feature:
**The following content is AI generated and might contain incorrect information. Before you use this content, make sure to review for inaccuracies.**
# Summary
The purpose of this workflow is to make a GET request to an Azure API Management API endpoint and retrieve a list of continents by their name. The workflow is triggered when a HTTP request is received and the response from the API is returned with a status code of 200.
||Workflow Properties|Value|
|-----|-----|-----|
|1|Connector type - In App|3|
|2|Connector type - Shared|0|
|3|Connector type - Custom|0|
|4|API Connections|0|
# Workflow Steps
## How the workflow starts (Triggers)
- **When_a_HTTP_request_is_received**
- **Type:** In App
- **Description:** This trigger starts the workflow when a HTTP request is received. The method used for the request is `GET`.
- **Trigger Input:** The trigger input for this step is the HTTP request with the method `GET`.
- **Trigger Output:** There is no output for this trigger.
## How the workflow continues (Actions)
- **Call_an_Azure_API_Management_API**
- **Type:** In App
- **Description:** This action calls an Azure API Management API. The operation ID used is `xxxxxx` and the connection used is `apiManagementOperation`. The method used for the API call is `get` and the path template is `/ListOfContinentsByName`.
- **Action Input:** The action input for this step includes the API management settings with the operation ID `xxxxxx` and connection `apiManagementOperation`. The method used is `get` and the path template is `/ListOfContinentsByName`.
- **Action Output:** There is no output for this action.
- **Response**
- **Type:** In App
- **Description:** This action sends a response with a status code of 200 and a body based on the result of the previous action. The body is taken from the output of the action `Call_an_Azure_API_Management_API` under the JSON path `listOfContinentsByNameResponse.listOfContinentsByNameResult`.
- **Action Input:** The action input for this step includes the status code `200` and the body taken from the output of the action `Call_an_Azure_API_Management_API` under the JSON path `listOfContinentsByNameResponse.listOfContinentsByNameResult`.
- **Action Output:** There is no output for this action.
This feature works for more complex workflows, producing high-quality documentation that can easily be adjusted and used later in a DevOps Wiki.
To lazy to read? We’ve got you covered! Check out our video version of this content!
Hope you find this helpful! If you enjoyed the content or found it useful and wish to support our efforts to create more, you can contribute towards purchasing a Star Wars Lego for Sandro’s son!
