kukeltje wrote : known issue in the current webconsole. afaik it is fixed
in the cvs head version
Sorry kukeltje, but I am using the last jBPM version, the 3.2.2 version, as you
can see here http://www.jboss.org/jbossjbpm/jbpm_downloads/.
I didn't understand very well you message.
Any
I am having the same problem.
kukeltje, can you explain what solution you have provided?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4151997#4151997
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4151997
I tried all ways to assign an actor to a task, not only using swimlanes, but
directely from the task selecting a task-node- then selecting the task in the
properties menu- then clicking in assignment and selecting actor and
entering with a valid user, but didn't work too.
Please, any help?
SOLUTION HERE:
http://jira.jboss.com/jira/browse/JBPM-1022?actionOrder=asc
Read Sebastian's comment:
I might be wrong,
but isn't it possible to easily fix it by changing the line in tasks.xhtml :
j4j:listTasks includeEnded=true target=#{tasks}/
by this one:
j4j:listTasksForActor
I am having the same problem, and I could not fix it doing what jeffcwang said.
I am using JBoss jBPM 3.2.2. When I execute the websale example the swimlane
task assignment don't work well.
I am runing the websale using jBPM Console Administrator, when I run the
websale example, show in the
known issue in the current webconsole. afaik it is fixed in the cvs head
version
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4151866#4151866
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4151866
starttasks cannot be assigned via a swimlane they are always assigned to
the actor who starts the task and this actor is put in the swimlane related to
the task.
This is by design. If you think it should be different, look in the jira if
there is already an issue for this and vote for it.
A possible way is to define the first node in the process with the initial
command. Then you don't have to use a start-state. I think it should fits yor
needs.
process-definition name=ProcessName initial=NodeName
|
I never tried this solution, so correct me if i am wrong.
View the original
This unit test shows the use of initial.
ProcessDefinition processDefinition =
ProcessDefinition.parseXmlString(
| process-definition +
| xmlns='' name='test'
initial='task1' +
|
thanks, i'll try that
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4074499#4074499
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4074499
___
jboss-user mailing list
I found a workaround for this problem. It seems that there is a bug here. If
you have a task in the start-state and try to assign it via a swimlane, it will
create a swimlane instance that always maps to manager. For example, if the
swimlane name is shipper and the actor_id is shipper in the
11 matches
Mail list logo
