[jbpm-users] jbpm prototype findings tasks, timers and cleaning up

We're currently prototyping a jBpm solution and have so far found it to be very effective. We are now experimenting with tasks and timers and have had to implement a few features ourselves, I'm not sure if we are using the engine correctly in doing this and wanted to list my experiences. Tasks We found that when leaving a task-node with multiple tasks signal="first" we leave open tasks. We implemented an action to remove all open tasks for this node on "node-leave". This seems to be a common pattern for us. Timers Timer only support events at points relative to 'now' i.e "In 3 business hours" We have represented a timer in the process that can be dynamic; an example is a task expiry (which links with the removal of tasks above) driven by an external business concept. We implemented our own CreateTimerAction wrapping the jBpm one and use a strategy for the resolution of 'dueDate'. This means we use an event node with a nested action (our CreateTimerAction) to create the Timer at the appropriate place. Has anyone else has a similar experience and do these concepts make sense? Kind regards, Dan Oxlade ________________________________________________________________________ This e-mail and its attachments are confidential. If you are not the intended recipient of this e-mail message, please telephone or e-mail us immediately, delete this message from your system and do not read, copy, distribute, disclose or otherwise use this e-mail message and any attachments. Although RI3K believes this e-mail and any attachments to be free of any virus or other defect which may affect your computer, it is the responsibility of the recipient to ensure that it is virus free and RI3K does not accept any responsibility for any loss or damage in any way from its use. RI3K Limited is a company registered in England no: 3909745. Registered office 10, Ely Place, London, EC1N 6RY. VAT registration no: 769 0192 07