"kukeltje" wrote : I've advised people internally at the company I work for
to NOT do this... I mean do not have managers or customers change processes themselves. I
know, the business want to skip the tech people, but instead of having them do it
themselves (yuck) create a new role, 'process designer' who does some invisible
tech work on the days the business suite is not there and use a graphical designer if he
is... Works perfectly here.
I understand that in most use cases where JBPM will be used workflow can be controlled by
the tech people, but in our use case having managers customize the workflow per person is
integral to the solution. What i was hoping is that we could create tested pieces of
workflow (possibly define workflow segments that are fully debugged) then allow managers
to combine these segments into a "master" workflow.
I don't know alot about JBPM at the moment and i'm not sure JBPM is the product
for us - we may need something more flexible. It sounds like JBPM is designed to be used
in a set manner. I think we may need something more flexible.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963940#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...