Title here
Summary here
Nanoflow actions and whether they will trigger a server request on Web
Nanoflow actions can be used in both Web, Offline and Native profiles. The behaviour of Nanoflow actions differs per profile, this reference guide is limited to Web and lists the number of network requests per action for Nanoflow and Microflow.
This list is still work in progress (last update: 20240123). Tested against Mendix 9.24.13
Note: even if the number of network requests is equal, a microflow is often preferred because of security considerations: Don’t use nanoflows for web applications
Actions
Object actions
Persistable entities
| Action | Properties | Nanoflow | Microflow | Result |
|---|---|---|---|---|
| Create object | 1 | 1 | Equal number of network requests. | |
| Create object | with commit | 2 | 1 | Microflow has fewer network requests. (additional request for the commit in a nanoflow) |
| Create object | with event (after create) | 1 | 1 | Equal number of network requests. |
| Create object | with commit and event (after create) | 2 | 1 | Microflow has fewer network requests. (additional request for the commit in a nanoflow) |
Non-Persistable entities
| Action | Properties | Nanoflow | Microflow | Result |
|---|---|---|---|---|
| Create object | 0 | 1 | Nanoflow has fewer network requests. (a NPE can be created client side if it has no additional properties | |
| Create object | with commit | 0 | 1 | Nanoflow has fewer network requests. (a NPE can be created client side if it has no additional properties |
| Create object | with event (after create) | 1 | 1 | Equal number of network requests. |
| Create object | with commit and event (after create) | 1 | 1 | Equal number of network requests. |
| Create object | with 1 or more system attributes (e.g. createdDate) | 1 | 1 | Equal number of network requests. |
| Create object | with commit and 1 or more system attributes (e.g. createdDate) | 2 | 1 | Microflow has fewer network requests. (additional request for the commit in a nanoflow) |
Client actions
| Action | Properties | Nanoflow | Microflow | Result |
|---|---|---|---|---|
| Open page | 0 | 1 | Nanoflow has fewer network requests. | |
| Close page | single | 0 | 1 | Nanoflow has fewer network requests. |
Observations
- Nanoflows require an additional network request for the commit on a create object
- Nanoflows require a network request (server interaction) for NPE’s if it contains a system attribute (createdDate, changedDate, owner, changedBy)
- Open/Close page actions sometimes trigger a network request for the page xml file, this happens for both Nanoflows and Microflows and are not counted in the number of network requests