Skip to main content

After performing the upgrade from 2024.1 to 2024.2, the Universal interface gives an unexpected and undesirable result when performing a task.

Suddenly certain fields have a gray background, where they did not have that in the old version.

The old (Universal) version was 2024.1.11.1.0, the new one is 2024.2.12.3.0.

All fields (except the 'Barcode pallet' field) of the task in question are read-only, no field is mandatory. The fields have different types and domains.

Does anyone have any idea what causes this new appearance and especially how we can possibly adjust this?

Thank you in advance

 

New version

 

Old version

 

New version dark mode

To make the situation even stranger, in Dark mode only 2 of the above 4 fields have a different background color...

 

 

Hi Marc,

This looks like behavior of the Read-only input control setting in Domains added in 2023.2. This setting affects the presentation of read-only fields.

Maybe during of after the upgrade something has changed in your model that made these fields read-only; maybe some Layout logic for example. I do agree it is strange that in the last photo two of the fields do have the background.

Hello Mark

Thanks for your quick reply.
All fields (except 'Barcode pallet') of the task are read only.
I checked the domains, and all domains had 'Read-only input control' enabled. Also for the fields that are not shown with a gray background....

I unchecked the 'Aantal op pallet' field for the domain used and synced the model to IAM. That made no difference.

If this was already introduced in 2023.2, we should also see this effect in the old version (= 2024.1.11.1.0), right?

The model was not modified at all. We have deliberately only upgraded the environment, and are now testing whether we can upgrade the production environment without any problems.

I'm afraid this is either a regression issue or a bug. Could you create a ticket for this in TCP? 

Edit: Solved in Universal GUI version 2024.2.13.1

Okay Mark.

I've created a ticket in TCP

Turns out there was a bug in Universal….

This is solved in version  Universal GUI 2024.2.13.1

Terms & ConditionsCookie settings