November 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2541) State of final node when worlflow contains "async node" but should be the same as without async node

by Christophe Lallement (JIRA)

State of final node when worlflow contains "async node" but should be the same as without async node ---------------------------------------------------------------------------------------------------- Key: JBPM-2541 URL: https://jira.jboss.org/jira/browse/JBPM-2541 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Environment: windows XP, java 1.6. Run of distrib example. Reporter: Christophe Lallement when we use workflow without sync (default) node, the final state of wokflow is "complete" (if we have en ter state "completed" on end node). It works fine when we execute wokflow synchronously. But when we change a node to set it at value "async": 1/ First we need to use a Job to change process a state node. 2/ The end value of the workflow is already "async" It's very important because manipulation of workflow depend of nature of node in this workflow. What we do if version 1 of workflow has only sync node then version 2 has asyn node ? I find it 's a shame to have 2 APIs to manipulate the workflow, this means knowing in advance whether the nodes are synchronized or not. Is there a way to avoid this ? You can check this to test end value of distribution sample: org.jbpm.examples.async.activity Regards -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2237) Reporting for jBPM4

by Heiko Braun (JIRA)

Reporting for jBPM4 ------------------- Key: JBPM-2237 URL: https://jira.jboss.org/jira/browse/JBPM-2237 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2157) Identity management editor

by Heiko Braun (JIRA)

Identity management editor -------------------------- Key: JBPM-2157 URL: https://jira.jboss.org/jira/browse/JBPM-2157 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-1797) Add authorization to the console

by Heiko Braun (JIRA)

Add authorization to the console -------------------------------- Key: JBPM-1797 URL: https://jira.jboss.org/jira/browse/JBPM-1797 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 CR1 Role based access to specific parts of the console -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2600) Update to console 1.2.0

by Heiko Braun (JIRA)

Update to console 1.2.0 ----------------------- Key: JBPM-2600 URL: https://jira.jboss.org/jira/browse/JBPM-2600 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2559) Transitions with timers from a user activity lead to incompleteable and indeleteable tasks

by Sebastian Schneider (JIRA)

Transitions with timers from a user activity lead to incompleteable and indeleteable tasks ------------------------------------------------------------------------------------------ Key: JBPM-2559 URL: https://jira.jboss.org/jira/browse/JBPM-2559 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Environment: Windows XP, Apache Tomcat 6, JDK 1.6 (should not be relevant) Reporter: Sebastian Schneider Priority: Critical Fix For: jBPM 4.2 Situation: ======= Imagine you want to model an escalation of a user activity. After a specific timeout a transition should be taken to deal with the escalation. The transition might lead to a user activity assigned to someobody else or to a different role or more important to the next steps performed automatically without a reaction of the user. Problem: ======= When the timeout event fires the transition is taken and the execution moves on to the next activity. However the task remains in the user's task list who had the task assigned. The task was not completed. Deleting the task will not succeed since you cannot delete a task which belongs to an execution. Completing the task will also fail since the associated execution does not exist anymore but was already removed from the database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2009