11.3 RNs #10132

ConnorLand · 2025-09-24T08:28:34Z

No description provided.

ConnorLand · 2025-09-24T12:39:32Z

content/en/docs/releasenotes/studio-pro/11/11.3.md

+    * If you connect to SQL Server using integrated security in a module such as [Database Connector](https://marketplace.mendix.com/link/component/2888), you may need to update the JDBC driver in `userlib` as well.
+- Maia for Pages now has knowledge about styling properties and can set and update their values.
+- When either the `X-Forwarded-Proto` or `X-Forwarded-Scheme` header is set to `http` cookies will now be set without the `secure` attribute, even if the `ApplicationRootUrl` is set to a secure URL.
+- In React Client, we now offer a quick fix for finding the usages of a select page configured for an association widget.


I'll look into documenting this quick fix more explicitly.

ConnorLand · 2025-09-24T12:41:07Z

content/en/docs/releasenotes/studio-pro/11/11.3.md

+- We have made several improvements to the modernized app explorer to enhance usability, performance, and stability. We have (temporarily) disabled the [Enter], [Left Arrow], and [Right Arrow] hotkeys on expandable nodes and [Left Arrow] on leaf nodes in the modernized app explorer.
+- We added `Check all` and `Uncheck all` functionality while selecting REST requests, when importing an OpenApi contract in Consumed Rest Services.
+- When creating a new branch, invalid characters (~ ^ : ? * [ \) are now automatically replaced by a dash (-) to adhere to Git's naming limitations.
+- Studio pro now replaces the invalid characters in branch name dialog with dashes as they are typed.


Are both these dash bullets valid, or duplications of each other?

I've made a suggestion for combining them.

ConnorLand · 2025-09-24T12:43:34Z

content/en/docs/releasenotes/studio-pro/11/11.3.md

+  * An association in the database contained any dangling references
+  * Foreign key constraints were newly enabled
+  * The association storage was changed to or from being a direct association 
+- We fixed an issue where a foreign key constraint violation in the database could result in a NullPointerException. (Ticket 258430)


The thing that broke 10.24.7

Maybe I should tweak the lang to be 1-1 as the other bullet.

@ConnorLand was this ever released in 11.x? If not there was nothing to fix and we should get rid of this, otherwise people will worry that there was a bug in 11.2?

MarkvanMents

A few suggestions for new features and improvements.
Let me know if you have any questions.

content/en/docs/releasenotes/studio-pro/11/11.3.md

MarkvanMents · 2025-09-25T14:57:45Z

content/en/docs/releasenotes/studio-pro/11/11.3.md

+    * If you connect to SQL Server using integrated security in a module such as [Database Connector](https://marketplace.mendix.com/link/component/2888), you may need to update the JDBC driver in `userlib` as well.
+* Maia for Pages now has knowledge about styling properties and can set and update their values.
+* When either the `X-Forwarded-Proto` or `X-Forwarded-Scheme` header is set to `http` cookies will now be set without the `secure` attribute, even if the `ApplicationRootUrl` is set to a secure URL.
+* In React Client, we now offer a quick fix for finding the usages of a select page configured for an association widget.


Should this be "the React Client"?

MarkvanMents · 2025-09-25T15:00:56Z

content/en/docs/releasenotes/studio-pro/11/11.3.md

+* When creating a new branch, invalid characters (~ ^ : ? * [ \) are now automatically replaced by a dash (-) to adhere to Git's naming limitations.
+* Studio pro now replaces the invalid characters in branch name dialog with dashes as they are typed.


I think these two are so similar they can be combined.

Suggested change

* When creating a new branch, invalid characters (~ ^ : ? * [ \) are now automatically replaced by a dash (-) to adhere to Git's naming limitations.

* Studio pro now replaces the invalid characters in branch name dialog with dashes as they are typed.

* When creating a new branch, invalid characters (~ ^ : ? * [ \) are now automatically replaced by a dash (-) to adhere to Git's naming limitations. This means that Studio Pro now replaces the invalid characters in branch name dialog with dashes as they are typed.

MarkvanMents

@ConnorLand
Finished reviewing the Fixes. Looks good, and I can't see any places that need more documentation.
I've made lots of very minor language changes which you can ignore if you want.
There are a couple of things which might be worth checking up on and a couple of places where things could be combined into a single fix.

content/en/docs/releasenotes/studio-pro/11/11.3.md

MarkvanMents · 2025-09-26T07:10:05Z

content/en/docs/releasenotes/studio-pro/11/11.3.md

+* We fixed an issue where a user is asked to provide git credentials for Repository optimization.
+* We fixed an issue where user gets an **Oops** pop-up window when creating non-versioned app.
+* We fixed an issue with the icon of the security level dialog that the the dark-mode icon was visible in light-mode.
+* We fixed an issue where a "404 - file not found for file: .well-known%2Fappspecific%2Fcom.chrome.devtools.json" error was shown in the Studio Pro console when opening a React app in Chrome with dev tools open. This error was caused by Chrome's automatic workspace folders feature.


I think this %2F is a slash and this should be:

Suggested change

* We fixed an issue where a "404 - file not found for file: .well-known%2Fappspecific%2Fcom.chrome.devtools.json" error was shown in the Studio Pro console when opening a React app in Chrome with dev tools open. This error was caused by Chrome's automatic workspace folders feature.

* We fixed an issue where a "404 - file not found for file: .well-known/appspecific/com.chrome.devtools.json" error was shown in the Studio Pro console when opening a React app in Chrome with dev tools open. This error was caused by Chrome's automatic workspace folders feature.

But probably best to check with the relevant team

Oh right. Weird. I wonder if GitLab or something changed it.

content/en/docs/releasenotes/studio-pro/11/11.3.md

Co-authored-by: Mark van Ments <[email protected]>

Upload RNs

8bce289

ConnorLand added Needs language review Update release and/or featured date 11.3 labels Sep 24, 2025

ConnorLand commented Sep 24, 2025

View reviewed changes

ConnorLand added 3 commits September 25, 2025 16:15

Order all fixes

e26a276

Fix oops

67a7480

Change ticketed fixes to align with previous lang

2a2e655

MarkvanMents assigned ConnorLand Sep 25, 2025

MarkvanMents reviewed Sep 25, 2025

View reviewed changes

MarkvanMents reviewed Sep 26, 2025

View reviewed changes

ConnorLand and others added 17 commits September 26, 2025 15:08

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

15685aa

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

035d4cd

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

7d747dd

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

c8ba236

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

d957ee0

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

81362f4

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

70a29bb

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

b4cb799

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

e3050d0

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

54386ca

Co-authored-by: Mark van Ments <[email protected]>

Update 11.3.md

0049ddf

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

1eaacc9

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

cf12866

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

6001bb9

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

b656642

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

179f637

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

03a8296

Co-authored-by: Mark van Ments <[email protected]>

ConnorLand and others added 8 commits September 26, 2025 15:18

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

db004f5

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

93b775e

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

0e72ce5

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

0ae7600

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

b07230f

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

d4e88b8

Co-authored-by: Mark van Ments <[email protected]>

Update content/en/docs/releasenotes/studio-pro/11/11.3.md

dec2a12

Co-authored-by: Mark van Ments <[email protected]>

Update 11.3.md

121ebdc

		* When creating a new branch, invalid characters (~ ^ : ? * [ \) are now automatically replaced by a dash (-) to adhere to Git's naming limitations.
		* Studio pro now replaces the invalid characters in branch name dialog with dashes as they are typed.

	* We fixed an issue where a "404 - file not found for file: .well-known%2Fappspecific%2Fcom.chrome.devtools.json" error was shown in the Studio Pro console when opening a React app in Chrome with dev tools open. This error was caused by Chrome's automatic workspace folders feature.
	* We fixed an issue where a "404 - file not found for file: .well-known/appspecific/com.chrome.devtools.json" error was shown in the Studio Pro console when opening a React app in Chrome with dev tools open. This error was caused by Chrome's automatic workspace folders feature.

11.3 RNs #10132

Are you sure you want to change the base?

11.3 RNs #10132

Uh oh!

Conversation

ConnorLand commented Sep 24, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

MarkvanMents left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

MarkvanMents left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!