[jboss-dev-forums] [Design of JBoss jBPM] - Re: various questions

[tom.baeyens@jboss.com]

"Fady" wrote : First of all, each workflow instance should be given a subject 
  | ...
  | the
  | subject field provides with a quick way of identifying a task.
  | 

you mean as a variable ?  what data should be filled in ?  i don't think that it is a good idea to force the user to enter a subject.  apart from that, the process definition contains a name and a description.  

also the task definition has a name that is copied into the task instance as a kind of default value.  after that, the task instance name is changeable.  don't know if the UI allows this currently, though.

would the task instance name cover your requirements ?  or how is your subject different ?

"Fady" wrote : and a
  | priority. 
  | ...
  | The
  | priority fields highlights the criticality of the task
  | 

task definitions already have a priority.  this priority is copied into a task instance when it is created.  then the priority can be changed for that specific task instance.  is that what you're looking for ?

"Fady" wrote : 
  | Moreover, is there any extra documentation outside the repository? For
  | instance I want to know what each JBPM tag is doing without having to
  | go into the actual code. An architecture document if available would
  | be very helpful.
  | 

currently i'm the architecture document :-(  feel free to use me for this purpose.  maybe i should respond to all your questions in a wiki page so that can grow to become the architecture document...

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012321#4012321

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012321