Get the PDF

Configure the key XML attribute

To configure the Key XML attribute, refer to the ATI system functions key table in the Enable the ATI Giant Voice device section and follow the function list to create the following file:

The key name and description parameters cannot contain spaces or any of the following characters: ' ! $ % ^ ( ) = { } , ; : ? " < > |

BlackBerry AtHoc

release 7.9 or later release, when no endpoint is selected, and the targeting rule is MSG-TARGETING-REQUIRED, an alert template is not ready to publish.

<giantVoiceSetting> 
<messages> 
    <message id = "MSG-TARGETING-NOT-ALLOWED">The Giant Voice Key you have selected on the previous page does not allow
additional selection of Giant Voice poles or zones.  You may still target users for other devices, but Giant Voice targeting
will be ignored.</message> 
    <message id = "MSG-TARGETING-ALLOWED">The Giant Voice Key you have selected on the previous page already has Giant
Voice poles and zones targeted, but you can override them by targeting different zones in the Targeting area just below.</message> 
    <message id = "MSG-TARGETING-REQUIRED">The Giant Voice Key you have selected on the previous page does not have any
targeting information built-in, and will require you to target at least one Giant Voice pole or zone below.</message> 
</messages> 
<keys>
    <key 
        id = "1|NoPA|Emergency|NoStrobe|NoMopp" 
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED" 
        targetingRule = "TargetingNotAllowed"> 
        <name>Key Name</name> 
        <description>Key description</description> 
    </key>
    <key 
        id = "1|NoPA|Emergency|NoStrobe|NoMopp"
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED"
        targetingRule = "TargetingNotAllowed">
        <name>Cancel</name>
        <description>Cancel</description>
    </key>
    <key 
        id = "2|NoPA|Emergency|NoStrobe|NoHeatCondition"
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED"
        targetingRule = "TargetingNotAllowed">
        <name>Weekly Siren Test</name>
        <description>Weekly Siren Test</description>
    </key>
    <key 
        id = "3|NoPA|Emergency|NoStrobe|NoHeatCondition"
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED"
        targetingRule = "TargetingNotAllowed">
        <name>Attack</name>
        <description>Attack</description>
    </key>
    <key 
        id = "4|NoPA|Emergency|NoStrobe|NoHeatCondition"
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED"
        targetingRule = "TargetingNotAllowed">
        <name>National Anthem</name>
        <description>National Anthem</description>
    </key>
    <key 
        id = "5|NoPA|Emergency|NoStrobe|NoHeatCondition"
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED"
        targetingRule = "TargetingNotAllowed">
        <name>Tornado</name>
        <description>Tornado</description>
    </key>
    <key 
        id = "6|NoPA|Emergency|NoStrobe|NoHeatCondition"
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED"
        targetingRule = "TargetingNotAllowed">
        <name>Heat Condition 1</name>
        <description>Heat Condition 1</description>
    </key>
    <key 
        id = "6|NoPA|Emergency|NoStrobe|NoHeatCondition"
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED"
        targetingRule = "TargetingNotAllowed">
        <name>Heat Condition 2</name>
        <description>Heat Condition 2</description>
        </key>        
    <key 
        id = "6|NoPA|Emergency|NoStrobe|NoHeatCondition"
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED"
        targetingRule = "TargetingNotAllowed">
        <name>Heat Condition 3</name>
        <description>Heat Condition 3</description>
    </key>
    <key 
        id = "6|NoPA|Emergency|NoStrobe|NoHeatCondition"
        messageIdRef = "MSG-TARGETING-NOT-ALLOWED"
        targetingRule = "TargetingNotAllowed">
        <name>Heat Condition 4</name>
        <description>Heat Condition 4</description>
    </key>    
</keys>
</giantVoiceSetting>

As “PA” is the default function of the

IIM

and used only in

IIM

, it is included in the Device XML and not in the Key XML. Hence, there is no need to create a new Key entry.

There are four entries in the Key XML for function 6, whereas all other functions have one entry each. Function 6 has four Sub-Commands or areas that serve as sub-functions. All four functions have different names and entries in the “ID” string of the XML so that the REACT4000 knows which one of the four functions to initiate for that key entry.

Section:

Create a mass device key endpoint