[
https://jira.jboss.org/jira/browse/JBPM-2560?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2560:
----------------------------------------
Alex, please mention explicitly here when you are done. I'll make sure the duedate can
accept EL as well then (or you in case if you want to do this yourself, look in TimerImpl.
(maybe the content of duedateDescription should be put in a TimerUtil class to be
reusable. And try to see if the description can accept EL as well. This makes it possible
to runtime have more explicit descriptions.
Task definition does not have some properties set from jPDL task
element
------------------------------------------------------------------------
Key: JBPM-2560
URL:
https://jira.jboss.org/jira/browse/JBPM-2560
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.1
Environment: jBPM 4.1
Reporter: Phil Bingley
Assignee: Alejandro Guizar
Fix For: jBPM 4.4
Attachments: jbpm-api.patch, jbpm-jpdl.patch, JpdlParser.java.patch,
JpdlParser.java.patch, TaskActivity.java.patch, TaskParsingTestCase.java
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The duedate and priority values in a jPDL task definition are not set on the task
definition when parsed. This means that the due date is not automatically set when the
task is created, nor the priority.
--
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