Action button with multiple checkboxes on detail page of lazily loaded screen is not working

bugs
1

Description

  1. In our project we have a master-detail screen.

  2. On detail screen section there are multiple buttons and some of them are set with Mode set to MultipleCheckboxes and Merge type set to AppendMergeExisting

    obrazek

  3. When the user clicks on the action button, status field is changed of selected entries and user is suppossed to save changes using save button (screen is in dirty mode).

Expected behaviour

In version 2022, all buttons work as expected and described above and this functionality was supported.

Current behaviour

In version 2024.2.1 user receives validation error:
obrazek

Additional notes

Is that validation correct for multiple checkboxes on detail screen section? I understand why it has sense on Master, but on detail I would not expect this behaviour. Architect usualy informs about these model problems as Model Errors but there is no error.

I think it is bug so I put it into bugs category but I am not sure if there is some consideration that I am missing. For our project it means that we canā€™t currently achieve the previous behaviour to let user select entries, change their status using action button and confirm changes by saving.

2

Any comment here?

I found this behaviour has been introduced with these changes: Check UI actions for lazily loaded screens

  1. I believe that the check is invalid at this case because we donā€™t use the Action button on the parent screen section but on the child screen section where everything should work fine.

I want to achieve this behaviour as it worked in previous versions:

  1. Let the user pick entries where he wants to change their states.
  2. The user clicks on the action button.
  3. Action changes the states of the entries and change Save button into red color.
  4. User clicks on the Save button and the changed entries are saved to the database.

Should I model the situation to make current behaviour fixed/changed?

3

The current restriction seems to be too strict. Weā€™re going to review it internally and I think weā€™re going to ease the restriction and have it only on root entities.

In the current situation the only way to achieve desired behaviour is to set the screen to eagerly loaded, but it might have perfomance repercursions.

4

Well, for our project the only valid workaround is to save changed states immediatelly and donā€™t let user confirm with Save button. Parent table has more than 40000 entries, so it must be lazy loaded screen.

It would be great if we can return the original behaviour.

5
1 Like