Conversation
Collaborator
MarkvanMents
left a comment
MarkvanMents
left a comment
There was a problem hiding this comment.
I've made a few suggestions - feel free to pick up whichever ones you want.
|
|
||
| ### New Features | ||
|
|
||
| - We added a **Cancel synchronization** nanoflow activity and action to stop synchronization. |
Collaborator
There was a problem hiding this comment.
Activity or action? I think we should use one or the other?
Collaborator
There was a problem hiding this comment.
Activity. I'll fix this one.
| - We added a **Cancel synchronization** nanoflow activity and action to stop synchronization. | ||
| - We added a `reloadApp` function to the `mx-api/ui` Client API that allows you to reload your application. By passing the optional `withState` parameter, you can preserve the application's state during the reload. This method is not supported on native mobile. For more information, refer to the [Client API documentation](/apidocs-mxsdk/apidocs/client-api/). | ||
| - We added non-interrupting event sub-processes to the workflow editor. This allows users to trigger optional process flows at any point during a workflow's execution. By using the `notify workflow` mechanism and targeting the sub-process's start event, these additional flows can be initiated without interrupting the main workflow. | ||
| - We added a `allowUpload` flag on `file` and `image` properties that provides upload capabilities to progressive web apps. We added new types `EditableFileValue` and `EditableImageValue` to provide upload related methods (such as `setValue`, `setValidator`, and other typical ones). This flag is optional to ensure backwards compatibility, with the default value being `false`. Native widgets do not currently support this feature. |
Collaborator
There was a problem hiding this comment.
Suggested change
| - We added a `allowUpload` flag on `file` and `image` properties that provides upload capabilities to progressive web apps. We added new types `EditableFileValue` and `EditableImageValue` to provide upload related methods (such as `setValue`, `setValidator`, and other typical ones). This flag is optional to ensure backwards compatibility, with the default value being `false`. Native widgets do not currently support this feature. | |
| - We added an `allowUpload` flag on `file` and `image` properties that provides upload capabilities to progressive web apps. We added new types `EditableFileValue` and `EditableImageValue` to provide upload-related methods (such as `setValue` and `setValidator`). This flag is optional to ensure backwards compatibility, with the default value being `false`. Native widgets do not currently support this feature. |
|
|
||
| ### Improvements | ||
|
|
||
| - The `OQL DELETE FROM` statement now supports associations with on delete behavior: |
Collaborator
There was a problem hiding this comment.
Suggested change
| - The `OQL DELETE FROM` statement now supports associations with on delete behavior: | |
| - The `OQL DELETE FROM` statement now supports associations with [on delete](/refguide/association-properties/#delete-behavior) behavior with the following functionality: |
Comment on lines
+26
to
+27
| * **Delete associated objects as well** | ||
| * **Delete the object only if there are no associated objects** |
Collaborator
There was a problem hiding this comment.
I don't think these are UX elements?
Suggested change
| * **Delete associated objects as well** | |
| * **Delete the object only if there are no associated objects** | |
| * Delete associated objects as well | |
| * Delete the object only if there are no associated objects |
Comment on lines
+51
to
+52
| #### Other Improvements | ||
|
|
Collaborator
There was a problem hiding this comment.
This is the wrong heading level.
Also, we don't normally have "Other Improvements" all the improvements should be together. I suggest moving the Updated Language Codes to after the Improvements section and not having two sets of improvements.
| - We fixed an issue in the call external action activity in Studio Pro where resolving inconsistencies would clear additional attributes. | ||
| - We fixed an issue in the OpenAPI documents of published REST services. The dates used in examples now use correct values. | ||
| - The consumed REST service editor in Studio Pro is now available in all languages that Studio Pro supports, not just English. | ||
| - We fixed `com.mendix.systemwideinterfaces.core.IUser::getUserName` which was always returning the user name at the time of login. It's now returning the actual user name after a cached session has been revalidated. |
Collaborator
There was a problem hiding this comment.
Suggested change
| - We fixed `com.mendix.systemwideinterfaces.core.IUser::getUserName` which was always returning the user name at the time of login. It's now returning the actual user name after a cached session has been revalidated. | |
| - We fixed `com.mendix.systemwideinterfaces.core.IUser::getUserName` which was always returning the user name at the time of login. It is now returning the actual user name after a cached session has been revalidated. |
| - We fixed an issue in the OpenAPI documents of published REST services. The dates used in examples now use correct values. | ||
| - The consumed REST service editor in Studio Pro is now available in all languages that Studio Pro supports, not just English. | ||
| - We fixed `com.mendix.systemwideinterfaces.core.IUser::getUserName` which was always returning the user name at the time of login. It's now returning the actual user name after a cached session has been revalidated. | ||
| - Resolved an OS command injection vulnerability in the Git process runner reported by Veracode. |
Collaborator
There was a problem hiding this comment.
Is there a CVE for this? Could be this (https://zeropath.com/blog/git-gui-cve-2025-46334-arbitrary-code-execution) but needs to be checked with version control team.
Suggested change
| - Resolved an OS command injection vulnerability in the Git process runner reported by Veracode. | |
| - We resolved an OS command injection vulnerability in the Git process runner reported by Veracode. |
| - The consumed REST service editor in Studio Pro is now available in all languages that Studio Pro supports, not just English. | ||
| - We fixed `com.mendix.systemwideinterfaces.core.IUser::getUserName` which was always returning the user name at the time of login. It's now returning the actual user name after a cached session has been revalidated. | ||
| - Resolved an OS command injection vulnerability in the Git process runner reported by Veracode. | ||
| - Resolved an issue where partially cloned apps were mistakenly identified as fully cloned during the cloning process, potentially leading to a 128 error. |
Collaborator
There was a problem hiding this comment.
Suggested change
| - Resolved an issue where partially cloned apps were mistakenly identified as fully cloned during the cloning process, potentially leading to a 128 error. | |
| - We resolved an issue where partially cloned apps were mistakenly identified as fully cloned during the cloning process, potentially leading to a 128 error. |
| - We fixed an issue on macOS where some views would behave in unwanted ways when scrolling. | ||
| - We fixed an issue in the React client where enabling autofocus on a popup that only contained focusable elements in the header or footer resulted in no element being focused. | ||
| - We fixed an issue where autofocus was not enabled for login dialogs and popups shown by the `Show message` action. | ||
| - We fixed an issue where logging in with incorrect credentials would throw an error in the client console instead of showing a validation message. This was caused by the Runtime not returning a 401 response for authentication failures. We also fixed the same issue for license-related errors where a 402 response was not being returned. (Ticket 268509) |
Collaborator
There was a problem hiding this comment.
Suggested change
| - We fixed an issue where logging in with incorrect credentials would throw an error in the client console instead of showing a validation message. This was caused by the Runtime not returning a 401 response for authentication failures. We also fixed the same issue for license-related errors where a 402 response was not being returned. (Ticket 268509) | |
| - We fixed an issue where signing in with incorrect credentials would throw an error in the client console instead of showing a validation message. This was caused by the Runtime not returning a 401 response for authentication failures. We also fixed the same issue for license-related errors where a 402 response was not being returned. (Ticket 268509) |
| - We fixed an issue in the React client where enabling autofocus on a popup that only contained focusable elements in the header or footer resulted in no element being focused. | ||
| - We fixed an issue where autofocus was not enabled for login dialogs and popups shown by the `Show message` action. | ||
| - We fixed an issue where logging in with incorrect credentials would throw an error in the client console instead of showing a validation message. This was caused by the Runtime not returning a 401 response for authentication failures. We also fixed the same issue for license-related errors where a 402 response was not being returned. (Ticket 268509) | ||
| - Fixed TabContainer not updating the active tab attribute or firing the onChange nanoflow on tab switch when the TabContainer entity is passed as a nanoflow argument. |
Collaborator
There was a problem hiding this comment.
Suggested change
| - Fixed TabContainer not updating the active tab attribute or firing the onChange nanoflow on tab switch when the TabContainer entity is passed as a nanoflow argument. | |
| - We fixed an issue where a TabContainer was not updating the active tab attribute or firing the onChange nanoflow on tab switch when the TabContainer entity was passed as a nanoflow argument. |
Collaborator
|
@ConnorLand Sorry, I've commited some changes that are supposed to be for another branch. I've reverted those commits :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.