Sorry about that...I definitely see how explaining why normal paths like
building it into the process definition aren't a possibility would help people
that are kind enough to help me... and hopefully others who might be searching
for answers later.
To answer your questions...
anonymous wrote
There are certain situations I have where a task node should be skipped. I'm
pretty sure you're not supposed to do this (i.e. cancel the task) from an event
like when the node is entered or when the task is created... and I've already
seen problems with the token being locked when I do... but
It's not an option that our user community would accept (i.e. the option you
suggest has been posed and shot down as the skip feature is already possible in
our current workflow engine).
Customer's workflows typically have hundreds of tasks any of which workflow
managers can elect to skip.
That was what I was thinking thanks for the feedback. (And for what it's
worth I don't like having to implement this... seems to run in the face of
having a process to follow and then throwing in some extra steps... but you
gotta do what you gotta do if the users can't live without being
Ronald thanks for the reply I gotcha on the terminology.
I had seen the milestone pattern before but I'm not sure if that meets my need?
I don't really know when where in the process definition the user will need
to essentially pause the current execution perform some arbitrarily
I've seen things here and there in the forums on ad-hoc tasks in a workflow...
but nothing in particular to handle this situation. Does anyone have a good
way to accomplish this?
SITUATION
A process is in progress when a performer realizes they have to perform some
ad-hoc task or tasks for
To add some additional fields to my process definitions, I've subclassed the
jBPM ProcessDefinition object with my own.
subclass name=com.xxx.XXXProcessDefinition
| extends=org.jbpm.graph.def.ProcessDefinition
| discriminator-value=S
| property
I was planning on using standard queries to gather the data, however, the
problem I was coming up with a consistent way for process designers to build in
nodes that could be indentified as different so they when processes are
executing managers can look at the execution from a macro standpoint
We have a need for process designers to place nodes in their processes to
pattern a milestone that fulfills some reporting needs. For instance, they may
want to report on what date each instance of a process started and then on what
date each of their their milestones were reached.
Is doing
Thanks for the quick reply Ronald.
I was aware of the term milestone being used in a workflow pattern for
synchronizing parallel branches... although I assume this was not fully baked
yet as the milestone-node doesn't appear the jPDL schema. Looks like there
is a test case that exercises
So I've seen Jiras for this topic, but I'm not quite sure how to reassign a
swimlane instance to new actors. Here's the situation:
Swimlane instance is assigned to actors: A B
String actorsString = A,B;
| String[] actorsArray = actorsString.split(,);
|
Believe I answered this one for myself... this relationship is defined as
inverse=true in the Hibernate mappings... therefore changing the pooledactor
set on the swimlane will no effect to the persistent data.
We must change the assinment on the PooledActor side:
12 matches
Mail list logo
