is your domain specific task a wait state task? Meaning do you call completeWorkItem method within the execute method of the handler? If so then work item info will not contain any data as there is no need to persist it. You can enable hibernate sql logging to see what sort of queries are produced. WorkItemInfo table is populated only if the work items are asynchronous - try adding user task to your process and then you should see entries in that table.
Hi Maciej, thank you for your answer. I have couple of questions here
To understand more, if a workItem task takes longer than a configured time (some time configured within JBPM framework) , then it gets persisted into the DB ?
and the second question, is there anyway I can FORCE the persistence of a workItemTask ? by means of an API call or something?
1 of 1 people found this helpful
persistence of work items is not based on time, it's based on their type so to say. So if you create work item handler then:
- if you call completeWorkItem method as part of executeWorkItem then it won't be persisted
- if you don't call completeWorkItem method as part of executeWorkItem then work item will be persisted in db and will wait for a signal to complete it and move on with process
So invoking or not completeWorkItem method is the API to trigger persistence of the work item.