Executing Automatic Programs

The following programs can notify managers of overdue or required conditions and can be scheduled to run automatically:

Program 1-OverDueNotification.cmd. Execute this program to notify users via email when activities are overdue. Refer to Activity Types for required settings.

Program 2-ProActiveReview.cmd. Execute this program to notify proactive reviewers via email that documents are coming due for review. You can also create an activity.

Program 3-CycleNotification.cmd. Execute this program to notify users via email and create activities for cycle training.

Program 4-DocumentExpirationNotification.cmd. Execute this program to notify users via email that documents are reaching their expiration date.

Program 5-ExpiredTraining.cmd. Execute this program to archive cycle training if overdue. (Refer to Program 3 – Training is expiring – CycleNotication.cmd for required settings.)

Program 6-COTrainingComplete.cmd. Execute this program to notify Change Order administrators that all training is complete against a Change Order.

Program 7-TrainingNotificationDeviation.cmd. Execute this program to automatically create activities and send emails to users with gaps in their requirements.

Program 8-SetDocumentEffectiveDate.cmd. Execute this program to set the Document Effective date after all training is complete.

Program 9-BeforeDueNotification.cmd. Execute this program to notify users before activities are due. Refer to Activity Types for required settings.

The following steps outline what must be done for these to execute correctly.

Step 1: Set parameters in Application Options (must have permissions to this function). Refer to Step 1: Setting Parameters in Application Options.

Step 2: Set programs to run on webserver using the Windows Task Scheduler.

Step 3: Update the App_config.xml file in TMS_Web\NotificationFunctions to have to correct location of the web.config file for the TMS website (line 4, <web_config_location>).

Step 4: To set the due date for the automatic activities, there are parameters in each program in the App_Config.xml file in the NotificationFunctions directory on the server: <duedate_days>30</duedate_days>. In this example, the due dates for the cycle notification (expired training) would be set to 30 days out from the date of execution. See your IT department for setting these defaults.

Steps 1 and 2 are described in the next two topics.