Skip to content

Commit 98f149f

Browse files
committed
Update links
1 parent 2aa91c9 commit 98f149f

File tree

14 files changed

+59
-59
lines changed

14 files changed

+59
-59
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,14 +27,14 @@ Business event services in are defined centrally by one app for a specific use c
2727

2828
To create a new business service, right-click on a module in your app and go to **Add other** > **Business event service** > **Create a new business event service**. The business event service document is open in Studio Pro:
2929

30-
{{< figure src="/attachments/refguide/modeling/integration/business-event-services/new-business-event-service.png" class="no-border" width="700" >}}
30+
{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/business-event-services/new-business-event-service.png" class="no-border" width="700" >}}
3131

3232
See the [Creating a New Business Event Service](/appstore/services/business-events/#two-way-be-create) section of *Mendix Business Events* for more information.
3333

3434
##### Using an Existing Business Event Service {#use-existing}
3535

3636
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:
3737

38-
{{< figure src="/attachments/refguide/modeling/integration/business-event-services/existing-business-event-service.png" class="no-border" width="700" >}}
38+
{{< figure src="/attachments/refguide/modeling/integration/use-platform-supported-content/business-event-services/existing-business-event-service.png" class="no-border" width="700" >}}
3939

4040
See the [Using an Existing Business Event Service](/appstore/services/business-events/#two-way-be-existing) section of *Mendix Business Events* for more information.

content/en/docs/refguide/modeling/integration/web-services/consumed-web-services/consume-a-complex-web-service.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -26,52 +26,52 @@ To import a web service directly, follow these steps:
2626
2. Specify a name for the new consumed web service and click **OK**.
2727
3. In the **Consumed Web Service** box, specify the **WSDL Source** to be use this consumed web service. Click **Edit**, and in the **WSDL Source** dialog box, specify a **URL** or load a **File** from your computer.
2828

29-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-complex-web-service/enter-wsdl-url.png" class="no-border" width="700" >}}
29+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-complex-web-service/enter-wsdl-url.png" class="no-border" width="700" >}}
3030

3131
4. Click **Import** to fetch the services and operations in the WSDL. If prompted, in the **WSDL Source** dialog box, select the ports you want to use and click **OK**.
3232

3333
5. In the **Consumed web service** screen, review the **Services** and **Operations** available to the imported web service. If you click on any of the operations, information about the operation will be displayed in the right pane. You can select individual web service operations from the list, otherwise the whole service and operation will be imported:
3434

35-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-complex-web-service/consumed-web-service-doc.png" class="no-border" width="700" >}}
35+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-complex-web-service/consumed-web-service-doc.png" class="no-border" width="700" >}}
3636

3737
## Configuring the Web Service Call
3838

3939
To configure the web service call, follow these steps:
4040

4141
1. If you did not use the web service wizard or did not use the option in the wizard to automatically create a microflow, create a microflow that will call the imported web service:
4242

43-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-complex-web-service/import-microflow.png" class="no-border" width="500" >}}
43+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-complex-web-service/import-microflow.png" class="no-border" width="500" >}}
4444

4545
{{% alert color="info" %}}Make sure the microflow either creates the variables required as arguments for the web service call or has them passed to it.{{% /alert %}}
4646

4747
2. If you are creating your own microflow, add the [Call web service](/refguide/call-web-service-action/) activity to the microflow. For details on how to add activities to a microflow, see [Activities](/refguide/activities/).
4848
3. Double-click the activity to open the **Call Web Service** properties editor and in the **Operation** field, click **Select**.
4949
4. In the **Select Web Service Operation** dialog box, you can select the operation for this web service call:
5050

51-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-complex-web-service/select-web-service-op.png" alt="select web service op" class="no-border" width="700" >}}
51+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-complex-web-service/select-web-service-op.png" alt="select web service op" class="no-border" width="700" >}}
5252

5353
5. In the **SOAP Request Body** tab of the **Call Web Service** properties editor, you can configure the SOAP body. This contains the parameters needed to execute the web service request. The **Simple**, **Export Mapping**, and **Custom** options enable you to select the type of SOAP body to use. Click **Edit value** and use one of the following to change the domain-to-XML mapping or the variables from the microflow used as input arguments:
5454
* **Simple expressions for each request parameter** — if the imported web service requires only primitive arguments:
5555

56-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-complex-web-service/simple-expression-param.png" class="no-border" width="700" >}}
56+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-complex-web-service/simple-expression-param.png" class="no-border" width="700" >}}
5757

5858
* **Export mappings for each request parameter** or **Export mapping for the entire request** — if the domain model entities need to be mapped to XML elements
5959
* **Custom request template** — for the definition of a custom XML body with parameters:
6060

61-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-complex-web-service/custom-request-temp.png" alt="custom-request-temp" class="no-border" width="700" >}}
61+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-complex-web-service/custom-request-temp.png" alt="custom-request-temp" class="no-border" width="700" >}}
6262

6363
6. In the **HTTP Headers** tab, if the Mendix Runtime should use HTTP authentication before calling the web service, check **Use HTTP authentication** and enter the **User name** and **Password** using the **Edit** buttons:
6464

65-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-complex-web-service/http-authentication.png" alt="http-authentication" class="no-border" width="700" >}}
65+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-complex-web-service/http-authentication.png" alt="http-authentication" class="no-border" width="700" >}}
6666

6767
7. In the **SOAP Response** tab, you can configure the handling of the return from the web service call as follows:
6868
* If the return is a complex XML structure, select **Mapping** and use an XML-to-domain mapping to map the XML elements to the domain model entities:
6969

70-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-complex-web-service/18581790.png" class="no-border" width="700" >}}
70+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-complex-web-service/18581790.png" class="no-border" width="700" >}}
7171

7272
* If the return is a primitive, you can store it in a variable by selecting **Store in variable****Yes** and provide the **Type** and **Variable**:
7373

74-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-complex-web-service/18581789.png" class="no-border" width="700" >}}
74+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-complex-web-service/18581789.png" class="no-border" width="700" >}}
7575

7676
* If you want to ignore the return, select **Ignore**
7777

content/en/docs/refguide/modeling/integration/web-services/consumed-web-services/consume-a-simple-web-service.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -29,11 +29,11 @@ To import a WSDL, follow these steps:
2929
3. On the **Consumed Web Service** screen, click **Edit**. Enter `https://www.w3schools.com/xml/tempconvert.asmx?wsdl` as the **URL** and click **Import**.
3030
4. The **Select Ports** dialog box is displayed for selecting a web service port:
3131

32-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/select-ports.png" class="no-border" >}}
32+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/select-ports.png" class="no-border" >}}
3333

3434
5. Click **OK** to select the default, then click **OK** to close the **WSDL Source** dialog. The operations **CelsiusToFahrenheit** and **FahrenheitToCelsius** are imported into the app:
3535

36-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/wsdl-source-dialog-box.png" class="no-border" >}}
36+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/wsdl-source-dialog-box.png" class="no-border" >}}
3737

3838
## Creating Logic to Call the Web Service
3939

@@ -42,55 +42,55 @@ To create logic to call the web service, follow these steps:
4242
1. Right-click your module in the **App Explorer** and select **Add microflow** from the menu:
4343
2. Name your microflow *ConvertCelsiusToFahrenheit* and click **OK**.
4444

45-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/add-microflow.png" class="no-border" >}}
45+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/add-microflow.png" class="no-border" >}}
4646

4747
3. An empty microflow is displayed:
4848

49-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/empty-microflow.png" class="no-border" >}}
49+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/empty-microflow.png" class="no-border" >}}
5050

5151
4. Open the **Toolbox** and drag a **Create variable** activity to the line between the start and end event.
5252
5. Double-click the new activity to open the **Create Variable** properties editor.
5353
6. For the **Data Type**, select **Integer/Long** and enter *100* as the value. For the **Output Variable Name** enter *TemperatureInCelsius*:
5454

55-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/create-variable.png" class="no-border" >}}
55+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/create-variable.png" class="no-border" >}}
5656

5757
7. Click **OK.** The microflow will look like this:
5858

59-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/18582079.png" class="no-border" >}}
59+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/18582079.png" class="no-border" >}}
6060

6161
8. Drag a **Call web service** activity from the toolbox and add it to the microflow just before the end event.
6262
9. Double-click this activity to open the **Call Web Service** properties editor. For the **Operation** of your consumed web service, click **Select**. Expand the **TemperatureConverter** web service and under **TempConvert**, click **CelsiusToFahrenheit** > **Select**:
6363

64-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/call-web-service-editor.png" class="no-border" >}}
64+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/call-web-service-editor.png" class="no-border" >}}
6565

6666
10. In the **Location** section for this operation, check the **Override location** box to override the location and use the secure location of the web service.
6767
11. Click **Edit** and change `http` to `https` for the URL in the **Location** editor, then click **OK**.
6868
12. In the **SOAP Request Body** tab of the **Call Web Service** properties editor, double-click the **Celsius (optional)** input parameter and enter `toString($TemperatureInCelsius)` for the expression, as the web service operation expects a string value. Then, click **OK**.
6969

70-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/soap-request-body.png" class="no-border" >}}
70+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/soap-request-body.png" class="no-border" >}}
7171

7272
13. In the **SOAP Response** tab, select **Yes** for the **Store in variable** option. Enter *TemperatureInFahrenheit* for the **Variable name**:
7373

74-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/call-web-service-soap-response.png" class="no-border" >}}
74+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/call-web-service-soap-response.png" class="no-border" >}}
7575

7676
14. Click **OK**. The microflow will look like this:
7777

78-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/microflow-part-2.png" class="no-border" >}}
78+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/microflow-part-2.png" class="no-border" >}}
7979

8080
15. Drag a **Show message** activity from the **Toolbox** to the line before the end event.
8181
16. Double-click the new activity to open the **Show Message** dialog box.
8282

8383
17. Select **Information** as the **Type**, and enter *The temperature in Fahrenheit is: {1}* for the **Template**. The *{1}* functions as a placeholder for the parameters.
8484

85-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/show-message.png" class="no-border" >}}
85+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/show-message.png" class="no-border" >}}
8686

8787
18. Create a new parameter and enter `$TemperatureInFahrenheit` for the expression (this is the return value of the web service operation) and click **OK**:
8888

89-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/parameter.png" class="no-border" >}}
89+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/parameter.png" class="no-border" >}}
9090

9191
19. Click **OK** again to save the show message activity values. The microflow now looks like this:
9292

93-
{{< figure src="/attachments/refguide/modeling/integration/consume-a-simple-web-service/completed-microflow.png" class="no-border" >}}
93+
{{< figure src="/attachments/refguide/modeling/integration/web-services/consume-a-simple-web-service/completed-microflow.png" class="no-border" >}}
9494

9595
20. Create a menu item that triggers this microflow. For details on how to create a menu item, see [Setting Up Navigation](/refguide/setting-up-the-navigation-structure/).
9696

0 commit comments

Comments
 (0)