Merge pull request mendix#7487 from mendix/db-webhooks

Move Webhooks doc

Author: dbreseman

content/en/docs/apidocs-mxsdk/apidocs/webhooks-sprints.md

@@ -19,8 +19,10 @@ The subjects covered in the *General* section are as follows:
 * [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/)
 * [Secure Outgoing Connections from your Application](/developerportal/deploy/securing-outgoing-connections-from-your-application/)
 * [Two-Factor Authentication](/developerportal/deploy/two-factor-authentication/)
-* [Version Downgrade Prevented](/developerportal/deploy/version-downgrade-prevention/)
+* [Version Downgrade Protection](/developerportal/deploy/version-downgrade-prevention/)
 * [Iframes and Running Apps](/developerportal/deploy/running-in-iframe/)
+* [Deployment Location](/developerportal/deploy/deployment-location/)
+* [Webhooks](/developerportal/deploy/webhooks/)
 
 ## 2 Building Your Model
 

content/en/docs/developerportal/deploy/general/_index.md

@@ -3,8 +3,8 @@ title: "Webhooks"
 linktitle: "Webhooks"
 url: /developerportal/deploy/webhooks/
 weight: 75
-description: "Creating a webhook to trigger actions from Mendix Cloud"
-tags: ["Mendix Cloud", "Webhooks", "CI/CD", "Pipeline"]
+description: "Creating a webhook to trigger actions from Mendix Cloud and Mendix for Private Cloud."
+tags: ["Mendix Cloud", "Mendix for Private Cloud", "Webhooks", "CI/CD", "Pipeline"]
 ---
 
 ## 1 Introduction
@@ -21,8 +21,6 @@ The webhooks contain a retry mechanism if an error response is received from the
 
 {{% alert color="info" %}}
 Webhooks are only available for licensed Mendix apps that are deployed to Mendix Cloud or Mendix for Private Cloud.
-
-They are set up and work independently of the deprecated [webhooks for Sprints and Stories](/developerportal/collaborate/general-settings/#webhooks).
 {{% /alert %}}
 
 ## 2 Configuring a Webhook{#setting-up}
@@ -58,7 +56,7 @@ If you select **Edit Webhook** from **More Options** ({{% icon name="three-dots-
 
 ## 3 Webhook Headers
 
-Every `POST`` payload contains the following delivery information as part of the header:
+Every `POST` payload contains the following delivery information as part of the header:
 
 * **connection** – `close`, indicating that there is no further information for the HTTP request
 * **content-length** – the size of the HTTP request in bytes (for example, `475`)

content/en/docs/developerportal/deploy/mendix-cloud-deploy/webhooks.md renamed to content/en/docs/developerportal/deploy/general/webhooks.md

@@ -17,7 +17,7 @@ aliases:
 
 The **Settings** page presents an overview of your app.
 
-On the top of page, you can see the image of the app, the app name, and the company that owns the app. You can also find the **Watch** / **Stop Watching** toggle which enables or disables notifications for this app.
+On the top of the page, you can see the image of the app, the app name, and the company that owns the app. You can also find the **Watch** / **Stop Watching** toggle, which enables or disables notifications for this app.
 
 {{< figure src="/attachments/developerportal/general/settings/general-information.png"  >}}
 
@@ -153,43 +153,7 @@ If you manage your projects in Jira, you can connect your apps in the Developer
 
 {{< figure src="/attachments/developerportal/general/settings/story-switcher.png" width="700"  >}}
 
-## 7 Webhooks {#webhooks}
-
-{{% alert color="warning" %}}
-This tab is for webhooks for stories and Sprints, and it is deprecated. This tab will be removed and these webhooks will be discontinued later in 2023. It is no longer possible to add new webhook configurations for stories and Sprints to your apps, but existing configurations will remain active and can still be edited. 
-{{% /alert %}}
-
-{{% alert color="info" %}}
-You can also set webhooks for your app to trigger endpoints when changes are made to deployment packages or models held in the Git Team Server. For details, see [Webhooks](/developerportal/deploy/webhooks/).
-{{% /alert %}}
-
-{{% alert color="info" %}}
-This tab is only visible if you already have webhooks for stories and Sprints created, you are a **Scrum Master**, and you have **Mendix Stories** turned on in the [Project Management](#project-management) tab.
-{{% /alert %}}
-
-Open the **Webhooks** tab to manage your app's webhooks for stories and Sprints. A webhook enables the Developer Portal to talk to another website and post updated Developer Portal content (for example, Sprint updates and new stories) to that website. For example, if you want to follow the changes in your app, you can create a service with a certain [URL](#url) that keeps track of the data, and then changes in the app in the Developer Portal are sent to that URL.
-
-{{< figure src="/attachments/developerportal/general/settings/webhooks-list.png" width="800"  >}}
-
-After clicking **New Webhook** to create a new webhook for stories and sprints, fill in the following details:
-
-* **Name** – the name of the webhook for stories and Sprints
-* <a id="url"></a>**URL** – the URL to which the webhook for stories and Sprints will connect 
-* **Secret** – the secret used by the Developer Portal to sign the data payload in order to identify the source of the data to the receiving URL (this appears when creating and editing a webhook for stories and Sprints, but it will not be displayed on the **Webhooks settings** page)
-* **Version** – the version of the webhooks feature to be used
-* **Events** – what types of data will be sent via the webhook for stories and Sprints (you must select at least one; this appears when creating and editing a webhook for stories and Sprints, but it will not be displayed on the **Webhooks settings** page)
-    * **Sprints**
-    * **Stories**
-
-To edit the above details for an existing webhook for stories and Sprints, click **Edit**.
-
-To delete an existing webhook for stories and Sprints, click **Delete**.
-
-{{% alert color="info" %}}
-For details on the technical configuration of webhooks for stories and sprints, see [Webhooks for Stories and Sprints](/apidocs-mxsdk/apidocs/webhooks-sprints/) in the *API Documentation*.
-{{% /alert %}}
-
-## 8 History {#history}
+## 7 History {#history}
 
 {{% alert color="info" %}}
 Only users with the **App Settings** permission can view the history.
@@ -201,7 +165,7 @@ The **History** tab presents the collaboration actions for the app. On this page
 
 When you select a history item and click **Show item**, the details of the story, Sprint, or [feedback item](/developerportal/app-insights/feedback/) will be presented.
 
-## 9 Story Archive {#story-archive}
+## 8 Story Archive {#story-archive}
 
 Once you have switched from Mendix Stories to Epics or Jira, Mendix archives any work you may have had in Mendix Stories. You can review your work on this tab, and download it if necessary.
 
@@ -211,7 +175,7 @@ Mendix will keep this data until October 1, 2024. Until then, you will be able t
 
 {{< figure src="/attachments/developerportal/general/settings/story-archive.png" width="700"  >}}
 
-## 10 Read More
+## 9 Read More
 
 * [Leave and Delete an App](/developerportal/general/leave-delete-app/)
 * [Manage Deep Links](/developerportal/general/manage-deeplinks/)

content/en/docs/developerportal/general/settings/_index.md

@@ -462,7 +462,7 @@ We have made the following improvements to the **Access Management** page in Por
 
 #### Deprecations
 
-* We have deprecated **General Settings** > **Webhooks** for stories and Sprints. For more information, see the deprecation note in the [Webhooks](/developerportal/collaborate/general-settings/#webhooks) section of *General Settings*. You can now set webhooks for building and deploying your app. These are described in [Webhooks](/developerportal/deploy/webhooks/).
+* We have deprecated **General Settings** > **Webhooks** for stories and Sprints. You can now set webhooks for building and deploying your app. These are described in [Webhooks](/developerportal/deploy/webhooks/).
 
 ### March 9, 2023