Skip to content
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.

System for mapping Escalation UID #77

Open
RFMoore opened this issue Sep 28, 2017 · 0 comments
Open

System for mapping Escalation UID #77

RFMoore opened this issue Sep 28, 2017 · 0 comments
Labels
Admin Admin Bounded context
Projects
Milestone

Comments

@RFMoore
Copy link
Collaborator

RFMoore commented Sep 28, 2017

Purpose:
[Escalation UID] helps define the escalation pathway for any report. The system follows geographical administrative boundaries (e.g. GPS points (ie Volunteers) escalate to Admin 4. Admin 4 escalates to Admin 3.)
In the creation of a new CBS form #37 , the administrator assigns [FullName] (User database - #13) to be responsible for a given geographic level. We want the User database [Escalation UID] to update with the [Volunteer UID] according to the higher level [FullName].

How admin boundaries
Highest level: Admin 0
Second highest: Admin 1
Third highest: Admin 2
Fourth highest: Admin 3
Fifth highest: Admin 4

Confirmation:
#13 user database updated based on new CBS form value in "Point of Contact" (#37).

@RFMoore RFMoore created this issue from a note in Admin (Backlog) Sep 28, 2017
@karolikl karolikl added this to the Future milestone Dec 17, 2017
@eprom eprom added the Admin Admin Bounded context label Jun 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Admin Admin Bounded context
Projects
Admin
  
Backlog (not MVP)
Development

No branches or pull requests

3 participants