[JBoss JIRA] Created: (JBPM-2805) Add access to event type in EventListener interface
by Mike Martin (JIRA)
Add access to event type in EventListener interface
---------------------------------------------------
Key: JBPM-2805
URL: https://jira.jboss.org/jira/browse/JBPM-2805
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.x
Reporter: Mike Martin
Add the ability to determine the event type ("start" or "end") from within an EventListener implementation. There should also be the ability to easily determine the name of the process definition step where the event occurred.
This makes it possible to write a single event listener that handles many different kinds of events. As far as design, it seems odd that the notify() method has a *Execution parameter, rather than an "event" parameter that contains all information about the event that occurred; the latter would be more in line with the way event listener interfaces are usually designed in Java.
--
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, 4 months
[JBoss JIRA] Created: (JBPM-2870) Auto-assign the autenticate user for a task
by Jaber C. Mourad (JIRA)
Auto-assign the autenticate user for a task
-------------------------------------------
Key: JBPM-2870
URL: https://jira.jboss.org/browse/JBPM-2870
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: JBPM 4.3 with spring
Reporter: Jaber C. Mourad
I'm looking for something to assign automatically the current authenticate user when it is known by the ProcessEngine.setAuthenticatedUserId method.
My usecase is very simple (but, AFAIK, no simple solution for this !) :
when a user start a particular process, I need to assign or make it candidate to a particular task (the first one generally)... As it is that particular user who create the instance, it is assigned to complete that task...
If it is possible to have an EL to describe the current autenticate user it would be very helpfull.
for example :
<task assignee="${context.authenticateUser}" candidate-users="${context.authenticateUser},bob" g="170,179,92,52" name="autoAssignTask">
<transition g="-81,-24" name="to theEnd" to="theEnd"/>
</task>
In that way it doesn't need to modify jpdl but it need to make the authenticate userId available.
Regards
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBPM-2773) TaskService: allow search for assigned candidate tasks
by Kai Weingärtner (JIRA)
TaskService: allow search for assigned candidate tasks
------------------------------------------------------
Key: JBPM-2773
URL: https://jira.jboss.org/jira/browse/JBPM-2773
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: any
Reporter: Kai Weingärtner
Fix For: jBPM 4.x
I would like to be able to find all tasks a user is a candidate for, regardless of the task being assigned or not. Currently the TaskQuery.candidate - filter also sets the unassigned filter. Thus, already assigned candidate tasks can never be found.
Possible use cases:
- a task needs to be reassigned due to sickness of the assignee
- user A needs to take user B's task, when a customer approaches user A about a task concerning him
Solution:
- don't add the unassigned filter in the candidate filter of TaskQuery but make them separate. To achieve the current result, one could set both filters explicitly.
--
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, 4 months
[JBoss JIRA] Created: (JBPM-2814) Trouble using a custom BusinessCalendar because of 'new BusinessCalendarImpl' in BusinessDayCalendarBinding
by Per Christian Henden (JIRA)
Trouble using a custom BusinessCalendar because of 'new BusinessCalendarImpl' in BusinessDayCalendarBinding
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2814
URL: https://jira.jboss.org/jira/browse/JBPM-2814
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Per Christian Henden
Fix For: jBPM 4.x
I've followed the howto on the JBPM webpages to replace BusinessCalendarImpl with my own implementation. My custom BusinessCalendar.add is called, that works, but in JBPM's BusinessDayCalendarBinding. java 'new BusinessCalendarImpl' is called and a BusinessCalendarImpl is used throughout the class.
This choice results in a problem when setting the 'days' field based on parsing jbpm.business-calendar.cfg.xml. The field is written to the 'new BusinessCalendarImpl' and not to my custom BusinessCalendar. This means that in my custom BusinessCalendar implementation I have no access to that information ('days' is null).
Other places in the JBPM code a processEngine.get(BusinessCalendar.class) is done to get an instance of the (custom) BusinessCalendar.
--
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, 4 months
[JBoss JIRA] Created: (JBPM-2813) Do not throw exception from BusinessCalendar when calculated end date ends up in the past
by Per Christian Henden (JIRA)
Do not throw exception from BusinessCalendar when calculated end date ends up in the past
-----------------------------------------------------------------------------------------
Key: JBPM-2813
URL: https://jira.jboss.org/jira/browse/JBPM-2813
Project: jBPM
Issue Type: Patch
Security Level: Public (Everyone can see)
Reporter: Per Christian Henden
Fix For: jBPM 4.x
The case where the subtract method is called with a duedate expression and reference date that resolves to a date in the past is handled by throwing a JbpmException ("duedate <date> ends in the past"). While this may sound like a good decision in theory, it is problematic in practice.
As a user of the API it means I have two choices when calling the subtract method. I must either -resolve the calcuation myself- before calling the method, to avoid the exception, or I must catch the -generic- JbpmException and decide on a duedate myself not knowing what went wrong.
When someone requests a date that is in the past in this way there's basically three options:
1) Let them have it. - This seems like a silly solution to me, duedates in the past doesn't make sense.
2) Throw an error. - In this case a specific exception should be thrown so that the user of the API can know why he got an exception.
An alternative to today's solution is to throw a less generic exception, maybe 'DueDateIsInThePastException' or IllegalArgumentException.
3) Return the current date, i.e. return Clock.getTime(). - Optionally a warning that the date was overriden to not be in the past can be logged, but this seems unecessary to me.
Attached patch implements alternative #3 (against trunk/revision 6208), which I believe is the best choice.
--
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, 4 months