How to store task report data into DB

We have execute process report smart service or Query process analytics to get data from TasksReportand design a batch process to save data

Thanks Susmetha,

Could you please explain it a bit more?

hi, You can use query process analytics to get the report data and then create a table to store required fields from this report data. once you have these two then create a batch process and configure the timing based on your convenience and run this process to store report data to db. This process will have the script task which will pull the report data and a write to db node which will store this data to the table.

Thanks Gopal,

Is it possible to create a batch process as soon as task gets created?

Have it as a scheduled process that pulls the tasks details or if you are planing to have tasks table specific for Application, u can have the write to db called at the start and end of tasks that inserts /update the tasks details

Hi All,

Is this possible to capture the details into DB without having task report.

May be you can try the record centric approach for task management to do so. You will not have to worry about keeping instances alive for a long time or creating task reports.

Thanks Konduru,

Could you please elaborate it a more?

Short lived processes will keep the your app performance better. 

 Just like having an audit table and writing the data to it whenever you make changes. You can Similarly have a task table and when ever you assign the task to someone try to capture the details of assignee and all other required fields and save it to the db. you can later show these tasks to the related person based on the assignee.

For this what you need to do is, you will have to create short-lived instances that is you create instance only on demand or only when someone is trying to initiate a task or complete the task. 

when you are assigning a task to a user/group make sure the details are captured and stored in the DB and that particular instance where you are capturing should end after the completion of the task details entry into the Db. Post that when the assignee logs in he can take up the task and it will create a new instance for that particular task. 

This will help you keep the app performance up and also you can have a track on all the tasks that were assigned(all details such as assigned on, by, completed on, over dues and always have them in your db and you can look back at it anytime)

Short lived processes will keep the your app performance better. 

 Just like having an audit table and writing the data to it whenever you make changes. You can Similarly have a task table and when ever you assign the task to someone try to capture the details of assignee and all other required fields and save it to the db. you can later show these tasks to the related person based on the assignee.

For this what you need to do is, you will have to create short-lived instances that is you create instance only on demand or only when someone is trying to initiate a task or complete the task. 

when you are assigning a task to a user/group make sure the details are captured and stored in the DB and that particular instance where you are capturing should end after the completion of the task details entry into the Db. Post that when the assignee logs in he can take up the task and it will create a new instance for that particular task. 

This will help you keep the app performance up and also you can have a track on all the tasks that were assigned(all details such as assigned on, by, completed on, over dues and always have them in your db and you can look back at it anytime)