topic Re: Using Activiti in a large Spring web app in Alfresco Archive

Using Activiti in a large Spring web app

vireswali — Tue, 21 Oct 2014 19:16:23 GMT

We have a large reporting webapp, which has a part subsystem that does request tracking and routing. Since Activiti is spring absed liek our app, so we closed on activiti as our workflow and routing engine. However we intend to use activiti as a service layer integration pattern instead of direct UI

Re: Using Activiti in a large Spring web app

smirzai — Wed, 22 Oct 2014 09:48:58 GMT

Actually you need to push only the variables which have some workflow effect to activiti. If you are rendering your forms, it is your freedom to populate the form from database, based by some ID got from Activiti, and modify them on submit and just let activiti know to forward to the next step.

Re: Using Activiti in a large Spring web app

vireswali — Thu, 23 Oct 2014 07:18:13 GMT

okie. so that essentially means to keep out all mutation logic from workflows. Only routing in there. And always give the workflow task variables the latest values that would result. By the way I was also thinking along the lines of evens. Would it be the right approach to allow mutations of DOs in workflow asks and delegates and then have post events on the task to synch the data in DB?

Re: Using Activiti in a large Spring web app

jbarrez — Thu, 23 Oct 2014 08:24:23 GMT

Only routing in there would be very strict. You can inject services into your delegates and do the changes there. I don't see a problem with that.

Re: Using Activiti in a large Spring web app

vireswali — Thu, 23 Oct 2014 09:53:21 GMT

Thanks Joram. that helps immensely.