Both processinstance and taskinstance do have startDate as instance variable...
1) no, Business Activity Monitoring is currently under development. The simulation functionality might also be of interest to you
2) From what I read you want the tasks to be automatically started. There is no functionality for this. Use e.g. timers that end a 'wait-state' and transition to a specific task
Thank you both for your quick replies.
The startDate variable seems useful; I will see if I can use that for my 'scheduled start date' that a user needs to input for certain tasks in the process when they start a new process. However, it looks more like the actual date the task was started.
Maybe the scheduled start date should be a custom variable?
Sounds like an interesting development, the Bussiness Activity Monitoring feature.
Where can I find more info on Bussiness Activity Monitoring or the Simulation functionality?
The startDate indeed gets a value if the task is started. What you can do is
- make sure the tasks is not auto created (see api/xsd)
- create an action on task-node enter event that puts a 'trigger' on a (message) queue somewhere with a delay to create the task. afaik, most jms implementations support delayed delivery, so maybe that can be used, or maybe even jbpm timers...