Location: BlogsFounder Blog
Posted by: paulrony	11/29/2008 10:07 PM
The SplendidCRM Workflow Engine is finally out the door. It has been a long hard road, but we were able to achieve all the goals we set. Aside from the expected requirements of being able to run just about any action based on just about any event in the CRM, one hidden requirement is the ability to track an error in the workflow back to the source. There is nothing worse than having a problem and not know where to look. Actually, this is a bit more important for us as only a fraction of the SplendidCRM users will create externally developed workflows. But, this might affect you if you need to do some advanced things in workflows, such as integrating with the Alphanumeric paging Activity from http://www.nsoftware.com/workflow/. /n software also has some other interesting activities such as the FTP Activity, the ZIP Activity or the Amazon Activity. Another complication with workflow is preventing circular workflows. For example, if you create an Account workflow that updates the same account that fired the workflow, they you could easily enter an endless loop. Or, what if you have two workflows have the side effect of firing one another, again causing an endless loop. SplendidCRM tries to protect against this by limiting events that can be fired from within a workflow.
Permalink |  Trackback