By looking at H2 database schema of Activiti, the ACT_RU_TASK table has following columns: CREATE_TIME_ START_DEADLINE_ COMPLETION_DEADLINE_ SKIPPABLE_ (Not sure purpose of this field)
In beta 2, you can retrieve the start time of a task through the historicActivityInstance object.
But I agree it makes sense to expose the create time in the Task interface and in the query API. (the other properties were removed in beta2). Here's the Jira: http://jira.codehaus.org/browse/ACT-209
Thanks for creating the Jira to expose create time column.
I had double checked and saw those columns in beta2. The schema.version = 5.0.beta2 in ACT_GE_PROPERTY table. The way I start the H2 database is: ant h2.start ant db.drop ant db create
Why have START_DEADLINE_ and COMPLETION_DEADLINE_ properties been removed?
In beta 2, you can retrieve the start time of a task through the historicActivityInstance object.
But I agree it makes sense to expose the create time in the Task interface and in the query API. (the other properties were removed in beta2). Here's the Jira: http://jira.codehaus.org/browse/ACT-209
What kind of semantics will task's duedate property have? I mean, what happens to the process when a task becomes "late"? Some (standard) process event is triggered? The task state is changed by the system?
Because it was not able to set those properties programmatically. They were remnants of the old implementation we did when we worked on tasks.
What we will add in the near future, is a dudate for the task (== completion deadline).
By default, I believe we shouldnt do nothing with (in the engine). However, it must be usable in for example a timer event, such that you can model what needs to happen when the duedate is passed.
