Skip to content

External entities do not require a separate license anymore #6457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MarkvanMents merged 4 commits into from
Sep 1, 2023
Merged

External entities do not require a separate license anymore #6457

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4b80bf4
External entities do not require a separate license anymore
joostverhoog Aug 29, 2023
eff65a2
Second mention of Data Hub licenses
MarkvanMents Aug 29, 2023
1660f57
Apps don't have to be licensed to use Catalog
MarkvanMents Sep 1, 2023
9911a50
Merge branch 'development' into license
MarkvanMents Sep 1, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion content/en/docs/developerportal/deploy/general/licensing-apps-outside-mxcloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,6 @@ Unlicensed apps, running outside the Mendix Cloud, have a number of restrictions
| **Number of Concurrent Users** | 6 | Depends on your pricing plan.¹ ² |
| **Time limitation** | Runtime stops after 2-4 hours (randomly chosen) regardless of user activity.³ | Does not have a time limitation. |
| **Number of Named Users** | No Limit | Depends on your pricing plan.¹ |
| **Data Hub** | 1000 objects per day | Depends on your pricing plan.¹ |

¹ More information on the capabilities of different license options is available on [Mendix Platform Pricing](http://www.mendix.com/pricing).

Expand Down
4 changes: 0 additions & 4 deletions content/en/docs/refguide/modeling/domain-model/external-entities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,6 @@ External entities can be used with local entities. However, as the datasets are

To follow how to add external entities from the [Integration Pane](/refguide/integration-pane/), see [Adding External Entities](#adding-external-entities).

{{% alert color="info" %}}
A license is required to use Mendix Data Hub and connect to external data sources through consumed OData services in your apps.
{{% /alert %}}

## 2 Adding an External Entity to an App {#adding-external-entities}

To add an external entity to your app model, follow these steps:
Expand Down
4 changes: 2 additions & 2 deletions ...ent/en/docs/refguide/modeling/integration/odata-services/wrap-services-odata.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@ OData is a set of best practices for building REST APIs that standardizes many a

### 2.2 Compatibility with Data Hub

Wrapping a service, API, or database in OData ensures compatibility with the [Catalog](/catalog/). Published OData services are registered automatically in the [Catalog](/catalog/), making them easily usable in other Mendix apps. Discovering and using OData resources in [external entities](/refguide/external-entities/) is made easy for licensed users on a [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/), as [published OData Services](/refguide/published-odata-services/) are registered automatically in the [Catalog](/catalog/) and made available in the Studio Pro [Integration Pane](/refguide/integration-pane/).

Wrapping a service, API, or database in OData ensures compatibility with the [Catalog](/catalog/). Published OData services are registered automatically in the [Catalog](/catalog/), making them easily usable in other Mendix apps. Discovering and using OData resources in [external entities](/refguide/external-entities/) is made easy if you are using [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/), as [published OData Services](/refguide/published-odata-services/) are registered automatically in the [Catalog](/catalog/) and made available in the Studio Pro [Integration Pane](/refguide/integration-pane/).
## 3 Non-Persistable Entities as Published OData Resources {#npe-published-odata}

When building a connector or integration, you might only need to move data from back-end services to the client apps instead of storing the data in the database. To support this, you can expose [non-persistable entities](/refguide/entities/#non-persistable-entity) as [published OData resources](/refguide/published-odata-resource/). Previously, only persistable entities could be exposed as published OData resources.
Expand Down