© Copyright 2006 Riverscape Ltd. All rights reserved.
Click the appropriate function to see a screen capture. The message is formatted using a combination of plain text, database fields and global variables eg. date, time, user, workstation etc... If the criteria specified on the condition is satisfied then this message will be populated with the missing variables and then sent to the user as either a *BREAK, *NOTIFY, Email or SMS message etc... The message needs to have recipients defined if it is to be sent to anyone. All message types and message recipients are predefined to Informer by the administrator so they can be easily selected from a list. The user is performing a day to day function. In this case using DFU to update the 'COMPANY' file. If the criteria defined in the condition is satisfied then the associated message will be sent to the defined users. An iSeries message is sent to user RIVERJJ informing them of the event. An iSeries report is sent to the output queue of user RIVERJJ. The output queue is predefined to Informer by the administrator. An email is sent to user RIVERJJ. His email address has been predefined to Informer by the administrator. An SMS message is sent to user RIVERJJ. His mobile phone no. has been predefined to Informer by the administrator. The condition is specified for a database add, update, delete or for a valid combination of each. Rules can be applied which can further specify the event for which you are monitoring.