Deadline Settings

A Deadline Setting allows you to specify a time for a business process (that is not in a state of ACTIVE) to move to the front of the queued business processes waiting to run.

This notifies the system to place the business process in queue to move to the front of the queue. Every effort will be made to run the business process at the front of the queue. If the business process in queue misses its queue and reaches the first and second deadline, an exceptional event will be fired and posted to the dashboard. In order for you to receive the notification, you need to define the event posted to dashboard by setting EnableDeadlines=true in noapp.properties for each queue and define the eventrule in the eventrule.properties file.

EnableDeadlines.1=true for queue 1.

To set the Deadline Setting, set it for the number of hours or minutes from the business process start time. By default deadline and notifications are not set. To modify a Deadline Setting, you must modify the business process by checking the business process out, then check it back in.

Select the appropriate setting.

Do not set deadline

Run the business process without a deadline for queued business processes. This is the default selection.

To run a queued business process on a deadline, clear the check box.

Complete by Deadline

Enables you to specify a deadline time, in hours and minutes, by which the business process must complete once it is put in a queue.

Note: The deadline setting applies as long as the business process remains in a queue and does not apply for running business process.

First Notification: Hours and Minutes

Enables you to specify whether to receive notification before a business process deadline (as long as business process remains in a queue).

Second Notification: Hours and Minutes

Enables you to specify whether to receive another notification before a business process deadline (as long as business process remains in a queue).

Deadline Notification also requires additional setup for these property files:

1. Uncomment rule1 and rule 2 in eventrules.properties file.
   • Uncomment the following two sets of rules to enable Event Notification.

     
     name.rule1 = RuleEventAbnormal
     expression.rule1 = "/event[contains(ExceptionLevel,'Abnormal') or 
     contains(ExceptionLevel,'ABNORMAL')]"
     action.rule1.1 = com.sterlingcommerce.neo.event.rule.BPSpawnerAction
     priority.rule1 = 3
     
     name.rule2 = RuleEventExceptional
     expression.rule2 = "/event[contains(ExceptionLevel,'Exceptional') or 
     contains(ExceptionLevel,'EXCEPTIONAL')]"
     action.rule2.1 = com.sterlingcommerce.neo.event.rule.BPSpawnerAction
     priority.rule2 = 4
     

2. Confirm rules listener setting in listenerStartup.properties.

   # rule listener

   
   Listener.Class.3=com.sterlingcommerce.woodstock.event.listeners
                    .rule.RuleListener
   

3. The user wishing to receive these notifications needs to belong to the following groups
   • Abnormal Event Notifications
   • Exceptional Event Notifications