[Doc Improvement][Message extension config response][4332605]

msteams-platform/messaging-extensions/how-to/action-commands/respond-to-task-module-submit.md

@@ -23,7 +23,7 @@ You have the following options to respond:
 * [Card response](#respond-with-a-card-inserted-into-the-compose-message-area): You can respond with a card that the user can interact with or insert into a message.
 * [Adaptive Card from bot](#bot-response-with-adaptive-card): Insert an Adaptive Card directly into the conversation.
 * [Request the user to authenticate](/microsoftteams/platform/messaging-extensions/how-to/add-authentication).
-* [Request the user to provide additional configuration](../search-commands/respond-to-search.md#configuration-response).
+* [Request the user to provide additional configuration](../search-commands/respond-to-search.md#config-response).
 
 If the app doesn't respond within five seconds, the Teams client retries the request twice before it sends an error message **Unable to reach the app**. If the bot replies after the timeout, the response is ignored.
 

msteams-platform/messaging-extensions/how-to/search-commands/respond-to-search.md

@@ -93,88 +93,68 @@ Your service must respond with the results matching the user query. The response
 |`composeExtension.suggestedActions`|Suggested actions. Used for responses of type `auth` or `config`. |
 |`composeExtension.text`|Message to display. Used for responses of type `message`. |
 
-### Configuration response
+### config response
 
-Configuration response is the data returned by the server or application to configure and enable the message extension within the messaging platform. The following code is an example for message extension configuration:
+The `config` response is the data returned by the server or the app to configure and enable the message extension within the messaging platform. When a user configures the message extension for the first time, a `config` response is used to prompt the user to set up the message extension and provide any necessary configuration.
 
-```json
-{
-    "name": "composeExtension/submitAction",
-    "type": "invoke",
-    "timestamp": "2024-03-08T14:10:47.575Z",
-    "localTimestamp": "2024-03-08T19:40:47.575+05:30",
-    "id": "f:7dfe18de-94e3-9f38-5d44-adeb31cd8243",
-    "channelId": "msteams",
-    "serviceUrl": "https://smba.trafficmanager.net/amer/",
-    "from": {
-        "id": "29:1PBlnIsEROUYzpFjULDVodMHrnpujmfhBdQAf0pcO1EkaDkhI0_Pj_ql-jZUYOGdSc3_KcqaIIjzbleraVJ2Z3g",
-        "name": "MOD Administrator",
-        "aadObjectId": "ce9def33-d7fc-444c-8728-be1f95e6b6f2"
-    },
-    "conversation": {
-        "isGroup": true,
-        "conversationType": "groupChat",
-        "tenantId": "4ad59956-0f88-4b88-a9d0-570b6eb4e66b",
-        "id": "19:1dd50ba7-e5bd-46ea-b34e-80a415148de7_ce9def33-d7fc-444c-8728-be1f95e6b6f2@unq.gbl.spaces"
-    },
-    "recipient": {
-        "id": "28:9a2b01fc-88c1-40e1-bf87-5079c8e35626",
-        "name": "PSDAzureBot"
-    },
-    "entities": [
-        {
-            "locale": "en-GB",
-            "country": "GB",
-            "platform": "Web",
-            "timezone": "Asia/Calcutta",
-            "type": "clientInfo"
-        }
-    ],
-    "channelData": {
-        "tenant": {
-            "id": "4ad59956-0f88-4b88-a9d0-570b6eb4e66b"
-        },
-        "source": {
-            "name": "compose"
-        }
-    },
-    "value": {
-        "commandId": "razorView",
-        "commandContext": "compose",
-        "data": {
-            "Title": "Welcome to RazorView!",
-            "DisplayData": " Today's date is 8-3-2024, Friday"
-        },
-        "context": {
-            "theme": "default"
-        }
-    },
-    "locale": "en-GB",
-    "localTimezone": "Asia/Calcutta"
-}
-```
-
-The following response is the configuration response that appears when the user interacts with the compose extension:
+The following code sample shows `config` response that appears when the user interacts with the compose extension:
 
 ```json
 {
     "composeExtension": {
-        "type": "config",
         "suggestedActions": {
             "actions": [
                 {
                     "type": "openUrl",
-                    "value": "https://7a03-2405-201-a00c-7191-b472-ff64-112d-f806.ngrok-free.app"
+                    "title": "Open url",
+                    "value": "https://ct3h34ng-7130.inc1.devtunnels.ms/searchSettings.html?settings="
                 }
             ]
-        }
-    }
+        },
+        "type": "config"
+    },
+    "responseType": "composeExtension"
 }
 ```
 
+The `config` response includes:
+
+* The `value` property contains a URL that opens a configuration page in a Teams dialog, which allows users to input necessary details and submit the configuration. Few examples of the `value` property are `https://<your-subdomain>.ngrok-free.app/searchSettings.html` and `https://<your-subdomain>.devtunnels.ms/searchSettings.html`.
+* The `type` field within `composeExtension` is set to `config`, indicating the nature of this response as a configuration. 
+* The `responseType` identifies that this response is for the `composeExtension` of the app.
+
 :::image type="content" source="../../../assets/images/configuration-response-me.png" alt-text="The screenshot shows the configuration response for message extension.":::
 
-### Response card types and previews
+Initialize the Teams SDK on the configuration page and use `authentication.notifySuccess()` to send the collected configuration data back to Teams. `submitConfig()` function demonstrates how to structure and return configuration values after the user completes the setup process.
+
+To complete the messaging extension configuration flow:
+
+1. The URL provided in the `value` property must host a webpage that opens the URL as a Teams dialog when the messaging extension configuration is triggered.
+2. If authentication is required, the page must use Teams authentication and call `authentication.notifySuccess()` upon successful login.
+3. After collecting user input, the page must notify Teams of the successful setup by calling:
+
+      ```javascript
+        microsoftTeams.app.initialize();
+
+        function submitConfig() {
+            const configData = {
+                setting1: "User-selected value",
+                setting2: "Another value"
+            };
+
+            microsoftTeams.authentication.notifySuccess(configData);
+        }
+      ```
+
+4. Calling `notifySuccess(configData)` sends the configuration values back to Teams.
+5. Once `notifySuccess()` is executed, the configuration window automatically closes and the messaging extension is successfully set up.
+
+### `result` response type
+
+The result list is displayed in the Microsoft Teams UI with a preview of each item. The preview is generated in one of the two ways:
+
+* Using the `preview` property within the `attachment` object. The `preview` attachment can only be a Hero or a Thumbnail card.
+* Extracting from the basic `title`, `text`, and `image` properties of the `attachment` object. The basic properties are used only if the `preview` property isn't specified.
 
 > [!NOTE]
 > Message extension search results don't support padding.
@@ -186,22 +166,13 @@ Teams supports the following card types:
 * [Connector card for Microsoft 365 Groups](~/task-modules-and-cards/cards/cards-reference.md#connector-card-for-microsoft-365-groups)
 * [Adaptive Card](~/task-modules-and-cards/cards/cards-reference.md#adaptive-card)
 
-To have a better understanding and overview on cards, see [what are cards](~/task-modules-and-cards/what-are-cards.md).
-
-To learn how to use the thumbnail and hero card types, see [add cards and card actions](~/task-modules-and-cards/cards/cards-actions.md).
-
-For more information about the connector card for Microsoft 365 Groups, see [Using connector cards for Microsoft 365 Groups](~/task-modules-and-cards/cards/cards-reference.md#connector-card-for-microsoft-365-groups).
-
-The result list is displayed in the Microsoft Teams UI with a preview of each item. The preview is generated in one of the two ways:
-
-* Using the `preview` property within the `attachment` object. The `preview` attachment can only be a Hero or a Thumbnail card.
-* Extracting from the basic `title`, `text`, and `image` properties of the `attachment` object. The basic properties are used only if the `preview` property isn't specified.
+**Hero or Thumbnail card**
 
-For Hero or Thumbnail card, except the invoke action other actions such as button and tap aren't supported in the preview card.
+For the hero or thumbnail card, except for the invoke action, other actions such as button and tap aren't supported in the preview card. For hero and thumbnail cards, you don't need to specify a preview property, a preview is generated by default. To know about cards and learn how to use the thumbnail and hero card types, see [what are cards](~/task-modules-and-cards/what-are-cards.md) and [add cards and card actions](~/task-modules-and-cards/cards/cards-actions.md).
 
-To send an Adaptive Card or connector card for Microsoft 365 Groups, you must include a preview. The `preview` property must be a Hero or Thumbnail card. If you don't specify the preview property in the `attachment` object, a preview isn't generated.
+**Adaptive Card or connector card**
 
-For Hero and Thumbnail cards, you don't need to specify a preview property, a preview is generated by default.
+To send an Adaptive Card or connector card for Microsoft 365 Groups, you must include a preview. The `preview` property must be a hero or thumbnail card and the respective card is generated as preview. If a `preview` property isn't specified in the `attachment` object, a preview isn't generated. For more information, see [using connector cards for Microsoft 365 Groups](~/task-modules-and-cards/cards/cards-reference.md#connector-card-for-microsoft-365-groups).
 
 ### Response example