...

• Roles

  • Roles

    • C/R/U/D

    • Duplicate

    • Replace

Entities

Already existing:

...

• create roles => CreateRolesMutation

• update roles => UpdateRolesMutation

• submit roles => SubmitRolesMutation

• replace roles => ReplaceRolesMutation

• delete roles => DeleteRolesMutation

• duplicate roles => DuplicateRolesMutation

...

• "gql_query_roles_perms": ["122001"]

• "gql_mutation_create_roles_perms": ["122002"]

• "gql_mutation_update_roles_perms": ["122003"]

• "gql_mutation_replace_roles_perms": ["122006"]

• "gql_mutation_duplicate_roles_perms": ["122005"]

• "gql_mutation_delete_roles_perms": ["122004"]

• "role_print_perms": ["122001"]

Models

The models should be created based on the existing tables.

...

Another solution is to show checkboxes grouped per entity and module

...

Open point: Xavier Gillmann (Unlicensed) how to get the string for the rights and module name ? should we use the module configurations json ? will it support standard translation ?

...

when the mutation “getAvailableRole“ will called then a signal will be sent Signal_get_module_role, the listener of that signal should return a module role definition object

roles = []

Signal_get_module_role()

for signal_listener

roles .amend(signal_listener.return_value)

module role definition object:

module_name: str

module_label = List of ‘lan_code':’display for lang_code'

roles = list of:

'role_name': str

'role_value': int

‘role_label’: List of ‘lan_code':’display for lang_code'

Solution 2 to retrieve the role (PREFERED)

...