On Oct 25, 11:52 pm, "John Mettraux" <[EMAIL PROTECTED]> wrote: > > Hi Matt, > > just out of curiosity, which product/project got chosen ? > > Cheers, > > -- > John Mettraux -///- http://jmettraux.openwfe.org
Intalio, although in the short term I think we're going to just build a custom solution without a general-purpose BPM. All we really needed was an approval-and-notification system, and the business logic for this is simple enough and consistent enough that a flexible BPM system isn't really necessary. In terms of a broader BPM solution though, which I think we will be adopting sooner or later, over the course of several meetings I found it increasingly difficult to make a case for OpenWFEru... the system analyst/business people found the language confusing (they really just want flow diagrams), and the programmers argued that using OpenWFEru adds complexity without much added benefit (all the real work happens in parcipants, and writing participants for OpenWFEru can be somewhat awkward right now). I'm a bit disappointed since 1) this will limit my ability to continue working on Fluxr, and 2) I'm trying to push Ruby at my organization as much as possible (I have grandiose visions of an enterprise powered by ActiveResource-centered apps), and so far this has been the first time when I couldn't make it work :( --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-dev?hl=en -~----------~----~----~----~------~----~------~--~---
