How to safely deal with pending escalations
KB001224
PRODUCT
Introduction
How to safely deal with pending escalations
Implementation
E-Mails that should not be sent:
If there are pending escalation mails that should not be sent, the following tips can be useful:
- Modify the date in the _Async table to be far in the future
- Change the status of all the Process Instances in _ProcInst to an undefined value (like ‘ID + 10’) where ProcInstID is part of _Async.
- Alter the kAsync sproc to NOT return any records – note that this may impact later testing and is not advised if you want to use these Process Instances again
Save e-mails to file system:
If a high-volume stress test need to be performed and instead of sending out a lot of workflow e-mails, rather save the e-mails on the file system for later review, the following tip can be applied:
Simply add the following lines to the appropriate place in K2Hostserver.config:
<system.net>
<mailSettings>
<smtp deliveryMethod="SpecifiedPickupDirectory" from="administrator@denallix.com">
<specifiedPickupDirectory pickupDirectoryLocation="c:foo"/>
</smtp>
</mailSettings>
</system.net>
The System.Net.Mail classes that are used for sending e-mails will automatically use these settings in the .config file if they exist. Specify the directory where you want your emails stored.
