|
Overview |
The Omnify Server Monitor web services contain built-in features for sending email alerts to users when they are due or overdue to take action on particular events (such as: Tasks, Training, and Signoff).
The alerts are configured to perform daily checks for each event and if the event criteria are met, the system will email the appropriate resources.
You can configure the events to determine grace periods and the frequency at which a user will receive the email.
These options are set in the web.config file and covered in subsequent sections.
You can also configure the content of the email alerts by making modifications to the web services source code.
However, it is highly recommended that you contact a qualified Omnify Software application engineer before making any changes in the source code.
|
|
The Server Monitor Web Services can be configured to alert users when tasks on Projects, Changes/ECO, Training, or Quality/CAPA objects are nearing their due date.
Each object has a separate option in the web.config file for enabling:
<configuration>
<appSettings>
<add key="ServerMonitor-EmailAlert_RunProjectTaskAudit" value="no"/>
<add key="ServerMonitor-EmailAlert_RunChangeTaskAudit" value="no"/>
<add key="ServerMonitor-EmailAlert_RunQualityTaskAudit" value="no"/>
<add key="ServerMonitor-EmailAlert_RunTrainingTaskAudit" value="no"/>
</appSettings>
Setting the specific task option to "yes" will enable the alert.
Another setting (in the web.config file) can be used to define how many days before the due date the email will be generated.
<configuration>
<appSettings>
<add key="ServerMonitor-EmailAlert_DueDateDaysBefore" value="0"/>
</appSettings>
When each email is sent, the system will automatically record the date and time the email was sent.
Another setting (in the web.config file) can be used to define how many days to wait until another email reminder is sent.
<configuration>
<appSettings>
<add key="ServerMonitor-EmailAlert_EmailDayBuffer" value="2"/>
</appSettings>
Note: in the above example, the system will wait 2 days before sending another reminder to the user.
|
|
The Server Monitor Web Services can be configured to alert users when they are active for Training events.
The web.config file contains an option for enabling the training alert:
<configuration>
<appSettings>
<add key="ServerMonitor-EmailAlert_RunUserTrainingAudit" value="yes"/>
</appSettings>
Setting the option to "yes" will enable the alert.
Another setting (in the web.config file) can be used to define how many days before the due date the email will be generated.
<configuration>
<appSettings>
<add key="ServerMonitor-EmailAlert_DueDateDaysBefore" value="0"/>
</appSettings>
When each email is sent, the system will automatically record the date and time the email was sent.
Another setting (in the web.config file) can be used to define how many days to wait until another email reminder is sent.
<configuration>
<appSettings>
<add key="ServerMonitor-EmailAlert_EmailDayBuffer" value="2"/>
</appSettings>
Note: in the above example, the system will wait 2 days before sending another reminder to the user.
|
|
The Server Monitor Web Services can be configured to alert users when they are active for signoff on Items, Changes/ECO, or Quality/CAPA objects.
Each object has a separate option in the web.config file for enabling:
<configuration>
<appSettings>
<add key="ServerMonitor-EmailAlert_RunItemSignoffAudit" value="no"/>
<add key="ServerMonitor-EmailAlert_RunChangeSignoffAudit" value="no"/>
<add key="ServerMonitor-EmailAlert_RunQualitySignoffAudit" value="no"/>
</appSettings>
Setting the specific task option to "yes" will enable the alert.
When each email is sent, the system will automatically record the date and time the email was sent.
Another setting (in the web.config file) can be used to define how many days to wait until another email reminder is sent.
<configuration>
<appSettings>
<add key="ServerMonitor-EmailAlert_EmailDayBuffer" value="2"/>
</appSettings>
Note: in the above example, the system will wait 2 days before sending another reminder to the user.
|
|