thinkwise-software-factory-menu

Create the item as a dependent-record add under its parent group rather than using the bound create-item task. The bound tasks like task_create_list_bar_item take zero parameters and can fail on commit with a mandatory menu_item_type error they expose no way to set.

List bar is the default for internal back-office apps with several groups of items. Tile suits small curated entry sets or customer-facing touch contexts. Tree should be avoided — it has verified API gaps, including no bound tasks on module_grp and no exposed item entity.

Locate the existing row in the role_menu_overview, role_list_bar_grp_overview, or role_list_bar_item_overview entity and edit its granted flag. A row already exists for every role at every level, so never try to add a new one.

A later patch in the same staging session can silently revert list_bar_item_description or list_bar_grp_description to null. Set the description last, in the same combined call as the item ID and target fields, and re-check the value in the response.

Not with an in-place edit, because the group ID is part of the item's composite key. Delete the item from its current group, then re-add it as a dependent record under the new group reusing the same item ID, target, and order_no.

Objects created through bound tasks get an auto-generated bracket-placeholder translation until translated. Items created via the dependent-record-add workaround may get no transl_object at all, which is recoverable by manually adding one and running the generic task_generate_transl_objects task.