Alarm Sound Management
Each User can customize alarm sounds and save their preferences in the Alarm Window's "Enable Sound" command. The enabling status type is memorized for each project user or for each runitme user so that when user logs in the enabling status will be restore to how it was when user last logged off.
By comparing the logged on Users "Access Level" with the active alarm threshold's "Read Access Area level" will determine the alarm to show in the Alarm Window. If the active user does not have the sufficient access rights, the alarm will not show in the window automatically disabling its sound.
|
|
After the user logs off the 'Enable Sound' button will be restored back to the previous status before user logged on. If, for example, the sound was enabled before user logged on, and then disabled after user logged on, once the user has logged off with alarm still active, it will obtain the condition it had by being restored with the alarm sound.
In cases where the alarm is set with "Read Access Levels" different to those for default, when no users are logged on this alarm will not be displayed in the alarm window but its sound will still be activated based on the enable button's status.
|
Networking
In regards to applications in networking, a Client application that uses the Alarm window is capable of enabling or disabling the Client machine locally the warning sound when alarm notifications arrive from the Server application. Also in this case the status of the "Enable Sound" button setting for the warning sound will be retained after screen closes and reopens, independently for each user to whom the Alarm Window has given access towards the Server application. Therefore, in this case, alarms that display in the Client Alarm Window and the consequent warning sound are managed in function with the user used for connecting to the Server (user inserted in the "Network Client Settings" from the Client project's "Network Services" resource or the user inserted in the "Default Logon User" property from the Server project's "Network Client" resource).
If the "Password Management" has been enabled in the client application as well, the Cllient user's Access level defined for the same user in the Server application will be considered (and not the one defined in the Client) and compared with the active alarm threshold's Read Access Area Level, and only if they match will the alarm be displayed in the Alarm Window.
|
|
The warning sound stops ringing when the Client's Alarm Window disconnects from the Server. This may happen for different reasons: timeout with Server, screen change, etc. If you wish that the warning sound of a new alarm sounds independently form the fact that the Alarm Window screen is displayed or not, you will need to set the client screen with the "Keep in Memory" option and enable the "Pre-load Screens" property situated in the Client project's "Execution" property group.
|
It is also possible to set more then one Alarm Window on the same screen, each one connected to different Servers with the each single Alarm Window's activated alarm Ack/Reset command received by the relative Server.
Once again, the "_SysVar_:AlarmsSoundState" system variable and the "Alarm - Enable Sound" command have the same behaviour as described above for the Alarm Windows. Even if the "Enable sound" button is disabled in only one of the Alarm Windows, the general alarm sound status will be disabled for all the windows. Likewise, if a "Enable Sound" button is re-enabled, the general alarm sound status will be re-enabled for all the windows.
Web Client
When there are active alarms in the project, a warning sound is given by the Web Client independently from the screen page opened. In addition, these warning sound can be acknowledged using the icon placed on the applet status bar. The warning sound is set through applet's "PlaySoundOnAlarm" (default "false") parameter. This parameter gets inserted automatically upon creation html files but can also be created manually for html files created by previous Movicon versions. You can also customize the sound produced by adding the optional "FileToPlayOnAlarm" parameter in the html file with the desired WAV file to be played. This parameter is also inserted by default upon creating htlm files. The audio file must be place on the Web server in the same folder where the Movicon "MovWebClientX.jar" applet resides, usually found in the project's resource folder.
For further information on the syntax used for the two parameters described above please refer to the section on "HTML creation pages" in the WebClient manual.
Restrictions
Statuses for warning sound users cannot be saved in Windows CE independently from the fact that the password management is enabled or not.
On ".wav" type audio files can be reproduced on Web Client.
