topic Re: Async user tasks and service tasks not working in Alfresco in Alfresco Archive

Async user tasks and service tasks not working in Alfresco

srobinson — Thu, 17 Jan 2013 04:51:02 GMT

I have a workflow with asynchronous user tasks and service tasks. The workflow works great in the stand alone Activiti Explorer, but when it is deployed in Alfresco and I run it in Share, the tasks do not run asynchronously and therefore it errors out. Is there a setting that needs to be overwritt

Re: Async user tasks and service tasks not working in Alfresco

frederikherema1 — Thu, 17 Jan 2013 08:24:10 GMT

Also, it is to be noted that I am using Alfresco 4.0.e which uses Activiti 5.7

Activiti 5.7 didn't have async continuations yet. On alfresco community (4.2.d), this is supported, however…

Re: Async user tasks and service tasks not working in Alfresco

srobinson — Thu, 17 Jan 2013 15:10:41 GMT

Thanks for the reply. Do you recommend upgrading Activiti in the current version of Alfresco or upgrading Alfresco to get a version of Activiti that supports async continuations?

- Shannon

Re: Async user tasks and service tasks not working in Alfresco

frederikherema1 — Fri, 18 Jan 2013 08:03:52 GMT

Upgrading activiti-version in alfrresco is possible, but is not just a "drop in replacement" of the Jar. Some code needs to be altered and SQL-upgrade-script (patches in alfresco 4.2) need to be run. I think it's better to switch to the latest community-version. Beware, this is not yet production stable, I presume (the 4.2.d build)…

Re: Async user tasks and service tasks not working in Alfresco

srobinson — Fri, 18 Jan 2013 22:52:34 GMT

When will Alfresco 4.2.d be Production ready?

- Shannon

Re: Async user tasks and service tasks not working in Alfresco

frederikherema1 — Sun, 20 Jan 2013 16:43:58 GMT

Any major version that is released (no nightly build) goes through QA. So 4.2d is actually as production-ready as a community release will ever get (no warranty supplied by alfresco). So "not production stable" might be wrong, It's just not as thoroughly QA'ed as an enterprise release is. If you are using community in production, this version is as safe as any other version you were using before.