Any comment here?
I found this behaviour has been introduced with these changes: Check UI actions for lazily loaded screens
- 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:
- Let the user pick entries where he wants to change their states.
- The user clicks on the action button.
- Action changes the states of the entries and change Save button into red color.
- 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?