June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBPM-955) jBPM: support setting Actor or Swimlane on process level (to re-use sub-processes)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-955?page=all ] Thomas Diesler updated JBPM-955: -------------------------------- Assignee: (was: Tom Baeyens) > jBPM: support setting Actor or Swimlane on process level (to re-use sub-processes) > ---------------------------------------------------------------------------------- > > Key: JBPM-955 > URL: http://jira.jboss.com/jira/browse/JBPM-955 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2 > Environment: All > Reporter: Arjan van Bentem > Priority: Minor > > Currently, an Actor or Swimlane is assigned within the task definition. When using sub-processes it would be very convenient to make the assignments in the parent process, such as in the parent <process-state>, or maybe even in the outermost <process-definition>. > For example: both a helpdesk employee and the customer would need to fill in the same questionnaire at different points in the main process. The steps to fill in the questionnaire would be a generic sub-process, in which (at design time) one would not know the Swimlane nor Actor. This would require a way to set the swimlane in the parent's process-state: >  > <process-state name="Customer survey" swimlane="client"> > <sub-process name="survey" /> > </process-state> > : > : > <process-state name="Employee survey" swimlane="employer"> > <sub-process name="survey" /> > </process-state> > ... or > <process-state name="Employee survey"> > <assignment actor-id="..."/> > <sub-process name="survey" /> > </process-state> > ... or maybe even at an even higher level, where jBPM would iterate up into the chain, possibly though nested sub-processes, until some assignment is found? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-994) wrong ProcessDefinition XML encoding for viewing in web console

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-994?page=all ] Thomas Diesler updated JBPM-994: -------------------------------- Assignee: (was: Tom Baeyens) > wrong ProcessDefinition XML encoding for viewing in web console > --------------------------------------------------------------- > > Key: JBPM-994 > URL: http://jira.jboss.com/jira/browse/JBPM-994 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2 > Reporter: Alexander Schlett > > If the process definition contains expressions like "a==b && b==c" (the && is encoded as && in the original process definition xml file) > then FileDefinition seems not to encode it to valid XML on the file system, making the web console fail with this process definition (not wellformed XML). The XML is correct in the database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-807) Allow assignment of jBPM variables via EL evaluation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-807?page=all ] Thomas Diesler updated JBPM-807: -------------------------------- Assignee: (was: Tom Baeyens) > Allow assignment of jBPM variables via EL evaluation > ---------------------------------------------------- > > Key: JBPM-807 > URL: http://jira.jboss.com/jira/browse/JBPM-807 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Gavin King > Priority: Critical > > A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value. > What I want is to be able to say: > <assign variable="orderId" value="#{order.id}"/> > when a transition occurs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1060) Add EL support for Timer properties

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1060?page=all ] Thomas Diesler updated JBPM-1060: --------------------------------- Assignee: (was: Tom Baeyens) > Add EL support for Timer properties > ----------------------------------- > > Key: JBPM-1060 > URL: http://jira.jboss.com/jira/browse/JBPM-1060 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.2 > Reporter: Fabien Coppens > > It would be very useful to be able to obtain Timer properties (such as duedate) from implicit variables such as ContextInstance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-739) isSuspended() incorrectly reflects state immediately after suspension

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-739?page=all ] Thomas Diesler resolved JBPM-739. --------------------------------- Resolution: Out of Date > isSuspended() incorrectly reflects state immediately after suspension > --------------------------------------------------------------------- > > Key: JBPM-739 > URL: http://jira.jboss.com/jira/browse/JBPM-739 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.1 > Reporter: Ryan Campbell > Assigned To: Tom Baeyens > > instance.isSuspended() doesn't reflect suspended state if you have just suspsended an instance, only if you are reloading it from the DB. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-745) Add <action> to JPDL docs for create-timer

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-745?page=all ] Thomas Diesler resolved JBPM-745. --------------------------------- Resolution: Out of Date > Add <action> to JPDL docs for create-timer > ------------------------------------------ > > Key: JBPM-745 > URL: http://jira.jboss.com/jira/browse/JBPM-745 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Documentation > Affects Versions: jBPM 3.1, jBPM 3.1.1, jBPM 3.1.2 > Reporter: Brice Ruth > Assigned To: Tom Baeyens > Priority: Minor > > See http://docs.jboss.org/jbpm/v3/userguide/jpdl.html#create.timer.element > Much the same as defining a <timer /> in jpdl, <create-timer></create-timer> supports a nested <action /> element. This should be appropriately referenced/linked in the documentation in this section. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-753) Leaving a Superstate does not record a NodeLog

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-753?page=all ] Thomas Diesler resolved JBPM-753. --------------------------------- Resolution: Out of Date > Leaving a Superstate does not record a NodeLog > ---------------------------------------------- > > Key: JBPM-753 > URL: http://jira.jboss.com/jira/browse/JBPM-753 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.2 > Reporter: Britt Miner > Assigned To: Tom Baeyens > > Leaving a Superstate should persist a NodeLog, but doesn't. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-722) create ws call signalToken(Long id) and signalToken(Long id, String transition)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-722?page=all ] Thomas Diesler resolved JBPM-722. --------------------------------- Resolution: Out of Date > create ws call signalToken(Long id) and signalToken(Long id, String transition) > -------------------------------------------------------------------------------- > > Key: JBPM-722 > URL: http://jira.jboss.com/jira/browse/JBPM-722 > Project: JBoss jBPM > Issue Type: Sub-task > Reporter: Ronald van Kuijk > Assigned To: Ronald van Kuijk > Priority: Minor > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-811) sorted task lists

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-811?page=all ] Thomas Diesler resolved JBPM-811. --------------------------------- Resolution: Out of Date > sorted task lists > ----------------- > > Key: JBPM-811 > URL: http://jira.jboss.com/jira/browse/JBPM-811 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Gavin King > Assigned To: Tom Baeyens > > JbpmContext.getTaskList() should allow sorting and filtering of the task list, by either priority, creation date, or type > Something like Hibernate Criteria API makes sense: > ctx.createTaskLiskQuery().orderByPriority().filterByType("approve document").getTaskList() > Same facility should also exist for querying process definitions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-810) Actions that validate transitions

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-810?page=all ] Thomas Diesler resolved JBPM-810. --------------------------------- Resolution: Out of Date > Actions that validate transitions > --------------------------------- > > Key: JBPM-810 > URL: http://jira.jboss.com/jira/browse/JBPM-810 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Gavin King > Assigned To: Tom Baeyens > > It is useful to be able to have an action in the stack of actions for a transition "cancel" the transition: > <transition name="delete"> > <action expression="#{user.checkDeletePermission}"/> > <action expression="#{document.delete}"/> > </transition> > The first action can cancel execution of the transition (and shortcircuit the rest of the action stack) by something like: > * returning false? > * throwing a predefined exception class CancelTransitionException? > Or perhaps we could have a specific concept of a Validator: > <transition name="delete"> > <validator expression="#{user.admin}"/> > <action expression="#{document.delete}"/> > </transition> > jBPM could have a Validator interface, and the Seam integration would just let you use an EL, and check the boolean return value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2008