Symptom: the alarm is there, but the map is silent
The presenter triggers stillness, a notification appears, but the isometric map shows no marker. Or the other way round: a marker appears, but the siren does not play. Both symptoms have causes in the template configuration, not in the detection mechanism itself.
It is worth knowing the rule: stillness is drawn on the map only for a permit from a template named ALARM, and SOS for a template named SOS. Without attaching the location to the template, the alarm exists only in the cache and is not visible.
Condition 1: template names and an attached location
After the stillness threshold is exceeded, the system creates an alarm permit from the ALARM template and marks the alarm on the map. If the template has no demo location assigned, the permit has no place on the map and nothing will be drawn.
Before the demo, check every template: that its name is correct, that the hall location is attached and that the demonstration account has permission to use it.
- template name exactly ALARM for stillness,
- template name exactly SOS for the alarm from the watch,
- demo location attached to both templates,
- template available to the demonstration accounts.
Sample time of pre-demo checks
Condition 2: sound, meaning the template option and the user gesture
The map plays the siren when a new work appears in the work feed that comes from a template with map sound enabled. A silent report is a template without this option. The SOS siren lasts 5.3 s and repeats twice, and a second work arriving during the signal does not play a second sound.
Browsers block sound without a user gesture, so after opening the map one click on it is needed. After the first load of a hall the map only remembers the existing works and does not ring, the sound is triggered only by new works.
Pitfall: approval and the template with automation
A permit template with automatic approval gives the work an active status immediately, which shortens the scenario. On the other hand, the approval function from the pending list can approve the oldest pending work in the whole system.
On a demonstration instance the consequences are small, but always approve by the permit identifier. This avoids approving someone else's work if overdue reports are left on the instance.
Order of checks before the start
The recommended order of checks takes about fifteen minutes. Start with the templates, then check the location, next open the map and click it, and finally trigger a test event on a demonstration account.
Record the result of the test. If stillness is not drawn on the map, go back to the first point: the template name and the attached location are the cause in the vast majority of such cases during a demo.
Video
Frequently asked questions
Why is stillness not drawn on the map?
Most often the ALARM template has no location attached. Then the alarm exists only in the cache and is not visible on the map.
Why is there no siren?
The template may lack the option to play sound on the map, or the browser blocked the sound. Click the map after opening it.
Will the first load of the hall play the siren?
No. After the first load the map only remembers the existing works, and the sound is triggered only by new ones.
We will check the templates before your demo
The InnerWeb team will run a trial of the whole scenario with you and confirm that the locations are attached to the templates.
Let's talk