The Problem:

Currently, OutSystems web application screen parameters are case-sensitive. If a browser receives a URL with incorrect casing, the input parameter is not recognized.

For example: .../Screen/?UserId=123 works, but .../Screen/?userid=123 fails to receive the variable

Current Solution (not ideal):

Fallback method, that reads the current parameters and corrects them if needed, but this is not ideal and it can lead to issues.

Read about it here.

Proposed Solution:

Since Service Studio already prevents duplicate variable names with different casings (you cannot have both "UserId" and "userid"), the platform should automatically map URL parameters to screen variables regardless of casing. This would ensure that internal assignments are recognized even if the incoming URL casing varies.