Changes between Version 12 and Version 13 of UserGuidelines/Alerts


Ignore:
Timestamp:
12/02/12 01:40:17 (9 years ago)
Author:
Nuwan Waidyanatha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UserGuidelines/Alerts

    v12 v13  
    2424''Example'' the ''headline'' text in a CAP message template for a flood event could be something like this: '''''[YYYY] [MMM]''' heavy rains have caused flash floods in the '''[LOCATION]''' area''. If the floods was in Varnasi area on 2012-09-25, then the message creator would replace the MMM YYYY and LOCATION to create the headline to be specific as such: '''''2012 September''' heavy rains have caused flash floods in the '''Varnasi''' area''.
    2525
     26* '''template name''' - the template name should be a generic name such as earthquake, cyclone, epidemic, et; one that a message creator can easily identify.
    2627* '''Locked''' - If you mark a field as locked, it cannot be edited in the actual alert message that inherits the template and extends it.
    27 * '''Message Type''' - Make sure the set the message type to Draft. At the time of issuing the message, the message creator will change that to ''Actual, Exercise, System, Test'',
     28* '''Status''' - Make sure the set the message ''status'' to '''''Draft'''''. At the time of issuing the message, the message creator will change that to ''Actual, Exercise, System, Test'',
     29* '''All the values''' - enter all other values as you deem essential, then apply the syntax mentioned earlier in creating place holders for words or sentences that should be replaces at the time of creating the actual message with hazard event specific information.
    2830
    2931[[Image(http://i.imgur.com/K98gj.png)]]