Update links

Author: quinntracy

content/en/docs/developerportal/digital-execution/implement-mendix/launch-app.md

@@ -58,7 +58,7 @@ Things you can customize for your apps in Mendix Cloud include:
 * [HTTP headers](/howto/security/best-practices-security/#adding-http-header)
 * [Path-based access restrictions](/developerportal/deploy/access-restrictions/)
 * [Environment variables](/developerportal/deploy/environments-details/#custom-environment-variables)
-* [Services](/developerportal/deploy/environments-details/#services), such as [the Event Broker service](/appstore/services/business-events/#mendix-event-broker)
+* [Services](/developerportal/deploy/environments-details/#services), such as [the Event Broker service](/appstore/services/event-broker/)
 
 #### Deploying the App
 

content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-configuration.md

@@ -46,21 +46,21 @@ In your defining app, you can create a new service by doing the following:
 
 The business event service document is open in Studio Pro:
 
-{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/new-business-event-service.png" class="no-border" >}}
+{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/business-events-config/new-business-event-service.png" class="no-border" >}}
 
 ### Adding Event Definitions {#add-be-definitions}
 
 To define what information is included in your events and what the service will implement, click **Add** in the open service document:
 
-{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/add-event-definition.png" class="no-border" >}}
+{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/business-events-config/add-event-definition.png" class="no-border" >}}
 
 1. Define what information is included in this event.
 
     * In the **General** field, provide the **Event name** and **Description** to let others know what the service is about.
     * In the **Attributes** field, click **Add** to define attributes. 
         * Changes you make here later could lead to breaking changes if the entity the attribute belongs to is consumed. Related entities will be updated automatically.
 
-    {{< figure src="/attachments/appstore/platform-supported-content/services/business-events/wizard-step-1.png" class="no-border" width="400" >}}
+    {{< figure src="/attachments/appstore/platform-supported-content/services/business-events/business-events-config/wizard-step-1.png" class="no-border" width="400" >}}
 
 2. Decide what other apps can do and what service this will implement.
 

content/en/docs/marketplace/platform-supported-content/services/business-events/business-events-deployment.md

@@ -20,7 +20,7 @@ The base values for your entity are taken from the **PublishedBusinessEvent**, a
 
 The text with the blue background above the entity tells you it is a specialized entity based on the **PublishedBusinessEvent** entity in the **BusinessEvents** service:
 
-{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/specialized-entity.png" class="no-border" width="200" >}}
+{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/deploy-a-business-event/specialized-entity.png" class="no-border" width="200" >}}
 
 ### Using the Publish Business Event Activity
 
@@ -48,7 +48,7 @@ The **Publish Business Event** activity will commit all event objects at the sta
 
 The **PublishedBusinessEvent** and **ConsumedBusinessEvent** entities are necessary to include in your domain model to publish business events. The **DeadLetterQueue** and **Outbox** are part of the Mendix Business Events service.
 
-{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/four-entities-in-domain-model.png" class="no-border" >}}
+{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/deploy-a-business-event/four-entities-in-domain-model.png" class="no-border" >}}
 
 * **PublishedBusinessEvent** – This non-persistable entity has the fields settings that every published event will include. Every published business event will inherit from this entity. The three fields can be set from the Java Action. This is used to define what your published business events look like.
 * **ConsumedBusinessEvent** – This entity has the fields that every consumed event will include. Every consumed business event will inherit from this entity. These fields will be set from the service, as will any additional fields that match with the payload of the event. This defines what you want to receive from the business events you subscribe to.
@@ -184,7 +184,7 @@ Start your docker cluster using the command `docker-compose up`. This will downl
 
 You can configure the app running in Studio Pro to use the Postgres database created using Docker. Remember to use a different database name for every app.
 
-{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/postgres.png" class="no-border" >}}
+{{< figure src="/attachments/appstore/platform-supported-content/services/business-events/deploy-a-business-event/postgres.png" class="no-border" >}}
 
 Below is an example of a Postgres service that you can add to your `docker-compose.yml` file.
 

content/en/docs/refguide/modeling/integration/use-platform-supported-content/business-event-services.md

@@ -29,12 +29,12 @@ To create a new business service, right-click on a module in your app and go to
 
 {{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/business-event-services/new-business-event-service.png" class="no-border" width="700" >}}
 
-See the [Creating a New Business Event Service](/appstore/services/business-events/#two-way-be-create) section of *Mendix Business Events* for more information.
+See the [Creating a New Business Event Service](/appstore/services/business-events-configuration/#two-way-be-create) section of *Mendix Business Events* for more information.
 
 ##### Using an Existing Business Event Service {#use-existing}
 
 To create a new business service, right-click on a module in your app and go to **Add other** > **Business event service** > **Use an existing business event service**. After importing the YAML file, the business event service document is open in Studio Pro:
 
 {{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/business-event-services/existing-business-event-service.png" class="no-border" width="700" >}}
 
-See the [Using an Existing Business Event Service](/appstore/services/business-events/#two-way-be-existing) section of *Mendix Business Events* for more information.
+See the [Using an Existing Business Event Service](/appstore/services/business-events-configuration/#two-way-be-existing) section of *Mendix Business Events* for more information.

content/en/docs/refguide/modeling/menus/view-menu/integration-pane.md

@@ -30,7 +30,7 @@ When you do not enter search text in the Integration pane, then the **Used in th
 
 {{< figure src="/attachments/refguide/modeling/menus/view-menu/integration-pane/used-in-your-app.png" alt="User in Your App Section" class="no-border" width="300" >}}
 
-For more information on how to add entities and actions to your app, see [Adding an External Entity to an App](/refguide/external-entities/#adding-external-entities) section in *External Entities* or [Call external action](/refguide/call-external-action/). For working with business events, see [Using Business Events](/appstore/services/business-events/#two-way-be).
+For more information on how to add entities and actions to your app, see [Adding an External Entity to an App](/refguide/external-entities/#adding-external-entities) section in *External Entities* or [Call external action](/refguide/call-external-action/). For working with business events, see [Using Business Events](/appstore/services/business-events-configuration/#two-way-be).
 
 ## Searching Catalog Sources {#search}
 
@@ -153,5 +153,5 @@ A business event can be **Pub**lished or **Sub**scribed to, or both.
 * [External Entities](/refguide/external-entities/)
 * [Consumed OData Service](/refguide/consumed-odata-service/)
 * [Business Event Services](/refguide/business-event-services/)
-* [Using Business Events](/appstore/services/business-events/#two-way-be)
+* [Using Business Events](/appstore/services/business-events-configuration/#two-way-be)
 * [How to Consume Registered Assets](/catalog/consume/)

content/en/docs/refguide10/modeling/integration/use-platform-supported-content/business-event-services.md

@@ -29,12 +29,12 @@ To create a new business service, right-click on a module in your app and go to
 
 {{< figure src="/attachments/refguide10/modeling/integration/use-platform-supported-content/business-event-services/new-business-event-service.png" class="no-border" width="700" >}}
 
-See the [Creating a New Business Event Service](/appstore/services/business-events/#two-way-be-create) section of *Mendix Business Events* for more information.
+See the [Creating a New Business Event Service](/appstore/services/business-events-configuration/#two-way-be-create) section of *Mendix Business Events* for more information.
 
 ##### Using an Existing Business Event Service {#use-existing}
 
 To create a new business service, right-click on a module in your app and go to **Add other** > **Business event service** > **Use an existing business event service**. After importing the YAML file, the business event service document is open in Studio Pro:
 
 {{< figure src="/attachments/refguide10/modeling/integration/use-platform-supported-content/business-event-services/existing-business-event-service.png" class="no-border" width="700" >}}
 
-See the [Using an Existing Business Event Service](/appstore/services/business-events/#two-way-be-existing) section of *Mendix Business Events* for more information.
+See the [Using an Existing Business Event Service](/appstore/services/business-events-configuration/#two-way-be-existing) section of *Mendix Business Events* for more information.

content/en/docs/refguide10/modeling/menus/view-menu/integration-pane.md

@@ -34,7 +34,7 @@ When you do not enter search text in the Integration pane, then the **Used in th
 
 {{< figure src="/attachments/refguide10/modeling/menus/view-menu/integration-pane/used-in-your-app.png" alt="User in Your App Section" class="no-border" width="300" >}}
 
-For more information on how to add entities and actions to your app, see [Adding an External Entity to an App](/refguide10/external-entities/#adding-external-entities) section in *External Entities* or [Call external action](/refguide10/call-external-action/). For working with business events, see [Using Business Events](/appstore/services/business-events/#two-way-be).
+For more information on how to add entities and actions to your app, see [Adding an External Entity to an App](/refguide10/external-entities/#adding-external-entities) section in *External Entities* or [Call external action](/refguide10/call-external-action/). For working with business events, see [Using Business Events](/appstore/services/business-events-configuration/#two-way-be).
 
 ## Searching Catalog Sources {#search}
 
@@ -157,5 +157,5 @@ A business event can be **Pub**lished or **Sub**scribed to, or both.
 * [External Entities](/refguide10/external-entities/)
 * [Consumed OData Service](/refguide10/consumed-odata-service/)
 * [Business Event Services](/refguide10/business-event-services/)
-* [Using Business Events](/appstore/services/business-events/#two-way-be)
+* [Using Business Events](/appstore/services/business-events-configuration/#two-way-be)
 * [How to Consume Registered Assets](/catalog/consume/)

content/en/docs/refguide9/modeling/integration/business-event-services/_index.md

@@ -47,12 +47,12 @@ To create a new business service in Studio Pro 9.24 and above, right-click on a
 
 {{< figure src="/attachments/refguide9/modeling/integration/business-event-services/new-business-event-service.png" class="no-border" >}}
 
-See the [Creating a New Business Event Service](/appstore/services/business-events/#two-way-be-create) section of *Mendix Business Events* for more extensive documentation.
+See the [Creating a New Business Event Service](/appstore/services/business-events-configuration/#two-way-be-create) section of *Mendix Business Events* for more extensive documentation.
 
 ##### Using an Existing Business Event Service {#use-existing}
 
 To create a new business service in Studio Pro 9.24 and above, right-click on a module in your app and go to **Add other** > **Business event service** > **Use an existing business event service**. After importing the YAML file, the business event service document is open in Studio Pro:
 
 {{< figure src="/attachments/refguide9/modeling/integration/business-event-services/existing-business-event-service.png" class="no-border" >}}
 
-See the [Using an Existing Business Event Service](/appstore/services/business-events/#two-way-be-existing) section of *Mendix Business Events* for more extensive documentation.
+See the [Using an Existing Business Event Service](/appstore/services/business-events-configuration/#two-way-be-existing) section of *Mendix Business Events* for more extensive documentation.

content/en/docs/releasenotes/studio-pro/10/10.3.md

@@ -114,7 +114,7 @@ If the microflow contains a [Show a page action](/refguide10/on-click-event/#sho
 * We fixed an issue that occurred when using the `div` operator in XPaths with at least one decimal operand where the result was an integer in HSQLDB.
 * When consuming an external action, Studio Pro may add entities to the domain model. It now adds these entities to the domain model of the module that the consumed OData service is in, rather than the domain model of the module that the microflow is in.
 * We fixed an issue in published REST services where messages about import mapping errors were duplicated in the response body.
-* We now add a prefix to a [business event entity](/appstore/services/business-events/#be-entities) name when it is created. If you decide to implement both the publishing of and subscription to an event, there are two entities created automatically. One of the entities is automatically renamed to **eventName_2** (by adding a prefix, you can make the name more meaningful).
+* We now add a prefix to a [business event entity](/appstore/services/business-events-deployment/#be-entities) name when it is created. If you decide to implement both the publishing of and subscription to an event, there are two entities created automatically. One of the entities is automatically renamed to **eventName_2** (by adding a prefix, you can make the name more meaningful).
 * We updated the HTTP response status codes for `POST`/`PATCH` on the publishing side depending upon the provision of the `Prefer` header in the request.
 * We fixed a `NullPointerException` that occurred when passing `null` to the `getValueFromString` method of `MendixBinary` members. This method now returns `null` when passed `null`.
 * We fixed an issue where some properties in the **Properties** pane looked editable, but the value of the property was not changed..

content/en/docs/releasenotes/studio-pro/9/9.24.md

@@ -1354,7 +1354,7 @@ We made the following improvements for selecting attributes:
 
 We made a major update to your business events modeling experience:
 
-* Business event service creators and users can now configure [multiple event publishers and subscribers](/appstore/services/business-events/#two-way-be). This means you get the full power of asynchronous communication across your enterprise landscape.
+* Business event service creators and users can now configure [multiple event publishers and subscribers](/appstore/services/business-events-configuration/#two-way-be). This means you get the full power of asynchronous communication across your enterprise landscape.
 * You can now create [business events](/appstore/services/business-events/) within the service document itself. Based on the definition of the events and the implementation, entities are created for you automatically.
 * Published business event service and consumed business event service options have been combined into [one menu item](/refguide9/business-event-services/) to help you get going quickly.