CAP Broker Use Cases

This page accommodates all the micro-evel use caases associated with the warning functions facilitated through http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO SAMBRO].

Acknowledge Message

The use case diagram describes how at the time of implementation, the Admin (Implementer) generated subscriber group, termed as first-responders, are assigned to acknowledge (ACK) to a message and the process of recording those acknowledgements.The process flow is intuitive from the use-case diagram as well.

Process	Description
assign a ACK to group	First we must get subscriber groups and select the desired group. These groups are created by the Implementer. Second the Implementer would assign event type, assign warning priority, and assign location to a ACK. We may not require that low priority messages for certain event types in some location are acknowledged and are simply informative alerts.
issue CAP alert msg	At the time of authoring a message, the Editor would set the Event Type, Location, and Warning Priority, which would determine the first-responder groups that should receive CAP alert msg through the deliver CAP alert msg process. In the CAP alert msg they would receive a URL with the link to acknowledge the message. This link would typically be a CAP <resource> element.
send msg "ACK"	The first-responder has two options to send msg acknowledgement: 1) click on the link, login, and press the ACK button or 2) send an SMS with keyword ACK or "ACKNOWLEDGE" with the <identifier> and user login details
record ACK	The process will get subscriber ID (or Person ID) and get CAP identifier (i.e. message id) to record the acknowledge for a particular message by a particular message recipient.

Report SOP Status