Saving service tasks to database

[egrabowska]

Hi,

I'm using Activiti engine to create application for automation and monitoring of some specific processes. Most of the tasks within these processes don't require any interaction with the user so I'm using <serviceTask> tag to define them and then link with proper Java implementation.

Ability to browse history of past process instances is crucial feature of this system. I have FULL history level set. Unfortunately I've noticed that only user tasks get persisted in act_hi_taskinst table. Why is that? Is there any simple way to persist also information about my service tasks? Is it against concepts standing behind Activiti?

[martin_grofcik]

Hi,

Have a look on the following example:
org.activiti.standalone.history.FullHistoryTest#testVariableUpdates
in the activiti source.

Regards
Martin

[egrabowska]

Thank you for your answer, I've already noticed that service tasks are saved into another table. Maybe you should consider adding more detailed description of database schema to your documentation. Tests code isnt usually the first place to look for specs.

[jbarrez]

We always accept pull requests if you think you can improve something, even in the docs.

There are two tables: ACT_HI_TASKINST and ACT_HI_ACTINST. The Java Api's also abstract this and give you easy ways to retrieve those.