Skip to content

Commit ab22c95

Browse files
committed
Review
1 parent 1bef4b3 commit ab22c95

File tree

1 file changed

+9
-11
lines changed
  • content/en/docs/marketplace/platform-supported-content/services

1 file changed

+9
-11
lines changed

content/en/docs/marketplace/platform-supported-content/services/event-broker.md

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -321,21 +321,19 @@ The Mendix Event Broker allows users to upload an AsyncAPI document for these ex
321321

322322
Technical Contacts with a license to the Mendix Event Broker can manage this feature from the **Uploaded Events** tab on the [Event Broker Manager](https://broker.mendix.com/) page.
323323

324-
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_ede_get_started.png" >}}
324+
To begin, click **Get Started** or **Upload AsyncAPI Document**.
325325

326-
To begin, click **Get Started** or **Upload AsyncAPI Document**, which involves uploading a file, verifying event information, and selecting spaces.
326+
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_ede_get_started.png" >}}
327327

328328
#### Upload an AsyncAPI File
329329

330330
Upload an AsyncAPI contract based on the [AsyncAPI format](#asyncapi-format). If there are any errors with the content or file format, an error box will display a list of the issues found.
331331

332332
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_ede_create_1.png" >}}
333333

334-
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_ede_create_1_errors.png" >}}
335-
336334
#### Verify File Information
337335

338-
The details of the uploaded file are extracted in the Verify section. This allows you to confirm that all information is accurate and meets the required expectations.
336+
The details of the uploaded file are extracted in the **Verify** section. This allows you to confirm that all information is accurate and meets the required expectations.
339337

340338
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_ede_create_2.png" >}}
341339

@@ -391,11 +389,11 @@ To use an uploaded event in a Bridge, you must configure a [Bridge with AWS SQS]
391389

392390
To use an uploaded event in an application, download the AsyncAPI contract for Studio Pro and import it as a new business event in your Mendix application. The download button is available on the [Service Details](#service-details) page.
393391

394-
After downloading the file, open your Studio Pro app and import the file as a new business event using the **Use an existing business event service** option.
392+
Use the **Use an existing business event service** option to import the file as a new business event.
395393

396394
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_ede_import_file.png" >}}
397395

398-
Click **OK**, and the new business event is created and ready to be used with the same features as any other imported event.
396+
Click **OK**. This creates the new business event that is ready to be used with the same features as any other imported event.
399397

400398
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/event_broker_ede_imported_file.png" >}}
401399

@@ -415,13 +413,13 @@ Externally defined events are provided to the Event Broker via an AsyncAPI docum
415413

416414
The mandatory information required in the file includes:
417415

418-
* **Title** - the service name.
419-
* **Message** - represents the business events.
420-
* **Payload** - the attributes that form the message.
416+
* **Title** the service name
417+
* **Message** represents the business events
418+
* **Payload** the attributes that form the message
421419

422420
{{% alert color="info" %}}
423421

424-
Message names must be unique. Duplicate events cannot be uploaded even if it is deployed anywhere in the Mendix space or uploaded before.
422+
Message names must be unique. Duplicate events cannot be uploaded if it is deployed anywhere in the Mendix space or uploaded before.
425423

426424
{{% /alert %}}
427425

0 commit comments

Comments
 (0)