[
https://jira.jboss.org/jira/browse/JBPM-2560?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-2560:
----------------------------------------
Phil, thank you for your contribution. I've incorporated your fix and test case.
Ronald, I worked on the task activity due date and description but still do not have a
test. Factoring out the due date calculation logic is also on the todo list. I'm also
considering to support EL in the task name as in jbpm3. Tell me if you can think of
another property where EL could be useful.
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