4 messages in com.mysql.lists.eventum-develRE: Workflow Enhancement
FromSent OnAttachments
Scott Maier10 May 2006 12:39 
Barry Benowitz10 May 2006 14:04 
Bryan Alsdorf11 May 2006 23:49 
Scott Maier12 May 2006 11:58 
Subject:RE: Workflow Enhancement
From:Barry Benowitz (barr@raritan.com)
Date:05/10/2006 02:04:50 PM
List:com.mysql.lists.eventum-devel

Hi Scott,

My two cents is that this sounds like a good idea, but maybe we need some more discussion before you go ahead and make the change. For example, I would think that we need pre *and* post hooks available, so I would not simply move the existing workflow calls to the "top", but rather add some new ones.

Also, hopefully you will be able to contribute your change back to Eventum for us all to use.

Thanks,

Barry

-----Original Message----- From: Scott Maier [mailto:smai@gmail.com] Sent: Wednesday, May 10, 2006 3:40 PM To: even@lists.mysql.com Subject: Workflow Enhancement

Is is possible to have the workflow calls moved to the top of the main functions so that they are called first before anything else happens and return a value that would return out of the function to prevent it from completing? The main reason is so that validation can be put into the workflow and prevent the action from happening.

For example, I want to make sure that certain custom field(s) are filled in before the issue can be closed (the field is not required at time of reporting). So in my workflow I can check this easily. The problem is that the workflow is fired after the issue has been closed which defeats the purpose.

It appears to be a simple change, move the workflow up and wrap a conditional statement around it to capture a value of 1 or -1 from the workflow handleIssueClosed function.

Are there any issues with doing this that I am not aware of? I can easily do this in the code myself, but I hesitate making core changes that might prevent me from updating easily in the future.

Let's face it, the average computer user has the brain of a Spider Monkey. - Bill Gates