Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Concepts

The module needs to be migrated from the legacy application to the new modular architecture. This module should take contributions from the other modules to defines authorities

Use case

Web application

  • UC13-1: search profile: Profile list > enter search criteria > search
  • UC13-2: add profile: Profile list > add > select the authorities and define name > save
  • UC13-3: update profile: Profile list > Select Profile > update the authorities and name > save
  • UC13-4: replace profile: Profile list > Select Profile > update the authorities and name > replace > define replacement date
  • UC13-5: remove profile: : Profile list > Select Profile > remove > select replacement profile > conf
  • UC13-8: Duplicate profile: Profile list > Select Profile >duplicate > give the new name > conf

Back-end

  • UC13-7: propagation of replacing / removing to user

Authority


  • Roles

    • Roles

      • C/R/U/D

      • Duplicate


Entities

(already existing)

tblRole

tblRoleRight

Details design


Back end module


Because openimis care already have an adapter to read the openIMIS roles and authority, no business function will be required outside the database updates and profile replacements.

Mutations

Mutation as part of the schema file:

create roles => CreateRolesMutation

update roles => UpdateRolesMutation

submit roles => SubmitRolesMutation

replace roles => ReplaceRolesMutation

delete roles => DeleteRolesMutation

duplicate roles => DuplicateRolesMutation

Permissions

"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

Services

none

Front end

The front end should group the authorities/rights per managing module, in order to do that the two first digits for the authorities/rights code.

Profile search page

The list of role should use the same layout as other existing list in openimis (claims, insuree ...)

Profile card

Ideally when reading or editing a role/profile, each module will have a "box" containing its authorities/rights;  in read mode, the box will appear only if at least one of the authority right is selected. The box should move according to the screen size.

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 ?



  • No labels