Versions Compared

Old Version 1

changes.mady.by.user Josh Zamor

Saved on

compared with

New Version Current

changes.mady.by.user Josh Zamor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Nick Reid, Josh Zamor, Chongsun Ahn


We met to address the current state of loading a user, getting the user's permissions, all the users programs, facilities, etc.

...

We found that overall we have a lot of overlap in the current endpoints.


Current plan:


OrderWorkTicket
1

User's permission strings is under development in sprint 31, we want to schedule work in sprint 32 to use these in the UI

Jira Legacy
serverJIRA (openlmis.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-2811

2

make a new users/{id}/facilities resource - it will include home and supervised facilities, current endpoint users/id/supervisedFacilties is to be phased out

Jira Legacy
serverJIRA (openlmis.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-2885

3

change /user/{id}/programs to be home and supervised programs (we'll keep the exisiting forHomeFacility query param, and not change representation)

4

start using permissions strings in UI (see #1)

    1. phase out using the roleAssignments api call and the role assignments returned currently as apart of a user
    2. phase in using the result of this list, which has program and facility ids for each named right, and using the result of the #2 and #3 when we need a program or facility name (link based on ID)



After the above occurs we'd like to try to improve the /api/users resources performance by removing:

...