You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{< figure src="/attachments/catalog/catalog-home.png" alt="Catalog home page" class="no-border" >}}
22
22
23
23
REST services provided by Mendix Apps running in Mendix Cloud (published [OData](/refguide/published-odata-services/) and OpenAPI REST Services), Web Services, and Business Events are automatically registered in your organization's Catalog upon deployment. This provides you with an up-to-date view of all the OData, OpenAPI, Web Service and Business Event endpoints published and consumed by your Mendix apps. These assets can be [curated](/catalog/manage/curate/) in the Catalog to ensure that they are exposed to the relevant users and can be found easily.
Copy file name to clipboardExpand all lines: content/en/docs/catalog/manage/curate.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Information that is added or changed during curation is stored in the Catalog fo
27
27
28
28
Owners and curators of registered assets can click **Curate** from the Catalog home page to see the curation list screen. This page provides an overview of all the registered assets you can curate as an owner under the **My Assets** tab. Curators will also see the **Company Assets** tab that lists all the registered assets.
2. Drag the image file into the upload area or click **Upload** to browse and select a file from your file system. Click **Step 2: Crop image** to proceed.
130
130
3. Move the wire-frame to select an area of the loaded image and change the size of the wire-frame to crop the image to the area that you want to use. When you are satisfied, click **Apply Changes**.
@@ -133,11 +133,11 @@ To **Upload a different icon** for the app, follow these steps:
133
133
134
134
4. A preview of the application icon is shown. Click **Save** to upload the selected icon.
2. The description from the service metadata is displayed in the **Description provided by the contract**. This cannot be changed, as it is part of the service definition. You can provide an alternative description in the **Description** box.
164
164
@@ -172,7 +172,7 @@ Add tags to categorize a registered service and provide additional means for fin
172
172
1. On the Service details page of a selected service, click **Edit** to display the Edit Service screen.
173
173
2. To add tags, click the empty **Tags** input area.
{{< figure src="/attachments/catalog/curate/service-metadata-tags.png" alt="List of tag suggestions" class="no-border" >}}
176
176
177
177
3. To add or edit the tags, enter a tag string and press <kbd>Enter</kbd> or select one from the list of existing tags that are used in the Catalog. To separate multiple tags, use spaces.
Copy file name to clipboardExpand all lines: content/en/docs/catalog/manage/landscape.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ Services are depicted as a round node with the icon that indicates the **Technol
62
62
63
63
Apps are displayed as square icons with the application icon and the environment that the app is deployed to is given below the app name. The example below shows a non-Mendix app (**TeamcenterMfg**), a Mendix app (**CompanyCarDemo**) which are deployed to the Mendix Free App environment, **Sandbox**. The third example shows another Mendix app (**HRSample_App**) deployed to the production environment which has a custom icon. For further information on adding a custom icon to your app see [Changing the Application Icon](/catalog/manage/curate/#application-icon).
{{< figure src="/attachments/catalog/search/attributes-associations.png" alt="Sample dataset with example association" class="no-border" >}}
164
164
165
165
***Name** – the name of the association that is exposed in the OData service contract.
166
166
***Navigates to** – the dataset the association is made with. Click the link to see the details of the associated dataset in the Catalog.
@@ -170,7 +170,7 @@ Under the **Associations** tab for each dataset, the associations are displayed:
170
170
171
171
The metadata panel at the right of the asset details screen displays details from the service metadata contract and values that have been curated in the Catalog:
@@ -219,7 +219,7 @@ The environment type indicates the quality and the status of the data that the e
219
219
220
220
The **Curation Option** is displayed in the asset detail screen if you are the owner of the selected asset or a curator. In **Edit**, you can edit the information that is displayed in the Catalog for an asset.
For the selected service, you can edit the [Application Details](/catalog/manage/curate/#curate-application), the [Service Details](/catalog/manage/curate/#service-details), and the Authentication.
225
225
@@ -237,7 +237,7 @@ The resulting ZIP file is named `DataHub_<service_name>_<service_version>_<techn
When you click **Download**, the following file is downloaded: `DataHub_SAP_Intelligence_1.0_OData4.zip`. This ZIP file has the folder `DataHub_SAP_Intelligence_1.0_OData4`, which contains all the metadata files that define the service.
Copy file name to clipboardExpand all lines: content/en/docs/catalog/register/register-non-odata-resources.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ There are certain limitations on consumed OData services. For more information o
29
29
30
30
The diagram below represents how an OData API wrapper can be used to connect a custom app service to a Mendix Studio Pro app:
31
31
32
-
{{< figure src="/attachments/catalog/register-non-odata-resources/non-odata.png" alt="Catalog connecting to non-OData resources" class="no-border" >}}
32
+
{{< figure src="/attachments/catalog/register-non-odata-resources/non-odata.png" alt="Diagram of Catalog resources connecting to non-OData resources" class="no-border" >}}
33
33
34
34
Once the OData service is available, find the generated *$metadata* file for your data, and use that to register your service in the Catalog via the connector on the home page. For more information on setting up the connection, see [Published OData Services](/refguide/published-odata-services/).
0 commit comments