topic Re: callActivity not setting the start user in second execution in Alfresco Archive

callActivity not setting the start user in second execution

iblanco — Mon, 13 Jun 2016 16:39:55 GMT

I'm using Activiti 5.19 embeded in Alfresco.I'm doing some test to check if calling activities dynamically could solve one of our use cases.So I defined a workflow that simply takes a process name from a config variable and calls that activity. The activity itself executes a little script task and t

Re: callActivity not setting the start user in second execution

jbarrez — Mon, 20 Jun 2016 12:56:08 GMT

What do you mean with 'second time'? I only see one call activity? Or does it loop back (That's what I assume)?

Re: callActivity not setting the start user in second execution

iblanco — Mon, 20 Jun 2016 13:10:36 GMT

Hi Joram:

Yes, it does loop back after executing each activity. The called activity is just a process with a single user task so whenever the user task is completed the parent process is resumed and calls the activity again.

I execute my process as user "admin". When the activity is called for the first time the called activity has the start_user_id set as "admin" as expected (both processes, the "parent" process and the called process, both have the user set correctly).

When I end the user task, once more with user "admin", the execution of the parent process resumes as expected and the callActivity is called once more but this time the child process has no "start_user_id" set at all.

It seems to me like if "resuming the parent" would cause the loss of the authentication.

I've tried to debug the issue across Activiti code and saw that the current authenticated user is saved in a ThreadLocal variable. Maybe there is some kind of thread when resuming the execution or something like that?

Thanks

Re: callActivity not setting the start user in second execution

jbarrez — Wed, 22 Jun 2016 09:38:13 GMT

> I've tried to debug the issue across Activiti code and saw that the current authenticated user is saved in a ThreadLocal variable.

That is correct.

How are you running this? Via Explorer? Unit test?

Re: callActivity not setting the start user in second execution

iblanco — Wed, 22 Jun 2016 09:39:27 GMT

I'm deploying and running it in Alfresco 5.1g.

Re: callActivity not setting the start user in second execution

jbarrez — Fri, 01 Jul 2016 15:58:39 GMT

I've added a unit test for it here, but I cannot reproduce it on the Activiti engine: https://github.com/Activiti/Activiti/commit/a6c8fda1e64497f50e76bb1ada77044d4a77cdaf

Would be interesting to see what the differences are between this and your case.