topic Re: Listing active workflows in Alfresco Archive

Listing active workflows

samuel_penn — Fri, 06 Jun 2008 15:29:33 GMT

Hi all,First off, I've seen http://wiki.alfresco.com/wiki/Workflow_JavaScript_API but I'm using 2.2 so though it looks like what I want, it's not too useful.What I'd like to be able to do is to get a list of active advanced workflows from Javascript. I thought I might be able to do this by running a

Re: Listing active workflows

birgir — Tue, 10 Jun 2008 08:47:58 GMT

I am looking for similar functionality as you. First off I was hoping a Lucene custom search would do the trick but doesnt seem to fully support workflow based search.

Regarding your query, here's a humble guess. In the lucene XML search definition you have a pairing of types or aspects and properties. There is no property value in your query e.g bpmutcome,bpm:startDate,bpm:taskId etc.

Hope this is of any help

Re: Listing active workflows

samuel_penn — Tue, 10 Jun 2008 09:14:43 GMT

That might be true, however if I perform a similar search on standard content, then I get back results:


search.luceneSearch("TYPE:\"{http://www.alfresco.org/model/content/1.0}content\"");
‍‍‍

I'll give that a try however to see if it makes any real difference (a quick test actually brought back a document (not a workflow) for some reason, possibly it had been in a workflow at some point). I obviously need to do some more investigation.

I've also found this post, which may be one way to do it, however it's not an approach I fancy since it's way too low level:

http://forums.alfresco.com/viewtopic.php?f=34&t=12271&p=40613&hilit=windows+cannot+find+cifs#p41067

Re: Listing active workflows

birgir — Tue, 10 Jun 2008 14:13:38 GMT

It seems to me that workflows are not stored at all in the Alfresco repository, as far as I know this makes workflow search out of Lucene scope (If anyone can show otherwise please explain). It would be ideal to be able to add workflow types and properties to Lucene config.

However, reading your recuirements are you aware of the "All active tasks" dashlet is out of the box, listing all non completed tasks in the repo and status. Otherwise, querying the workflow tasks can be done using the foundation services in java or more specifically the workflowservice. The workflow console implementation is a good reference. Also the WorkflowBean used for the "pooled tasks" dashlet and "My tasks todo".

http://jsourcery.com/api/sourceforge/alfresco/2.0.0/org/alfresco/web/bean/workflow/WorkflowConsoleBean.source.html#j723712063 (ATN! 2.0.0)

http://jsourcery.com/api/sourceforge/alfresco/2.0.0/org/alfresco/web/bean/workflow/WorkflowBean.source.html

If anyone knows if or how to use Lucene for workflow based search please enlighten the rest of us.

Re: Listing active workflows

samuel_penn — Tue, 10 Jun 2008 14:50:11 GMT

However, reading your recuirements are you aware of the "All active tasks" dashlet is out of the box, listing all non completed tasks in the repo and status.

No, I wasn't. Which version of Alfresco is that in, or can it be downloaded from somewhere? It doesn't appear to be listed as an option in my dashboard for 2.2.

Thanks,
Sam.

Re: Listing active workflows

samuel_penn — Tue, 10 Jun 2008 15:26:44 GMT

Looks like this answers my questions: http://forums.alfresco.com/viewtopic.php?f=34&t=8629

Re: Listing active workflows

birgir — Wed, 11 Jun 2008 08:46:56 GMT

ok, that settles it then, Lucene does not work.

I know there is a security vulnerability to the "All active task dashlet" (any user could manipulate the tasks), they might have left it out in the default config. I have in webapps\jsp\workflow\tasks-active-dashlet.jsp and in web-client-config.xml


<dashlet id="tasks-active" label-id="tasks_active_title" description-id="tasks_active_desc" jsp="/jsp/workflow/tasks-active-dashlet.jsp" allow-narrow="false" />
‍‍‍

User config of dashboards:
http://wiki.alfresco.com/wiki/User_Configurable_Dashboards

Re: Listing active workflows

samuel_penn — Mon, 16 Jun 2008 16:28:57 GMT

Found it - it was commented out in the web-client-config configuration, which was why I couldn't see it in the front end. It is, as you say, a security hole since anybody can accept/modify a task. It may be a good starting point however if we need to develop our own solution.

Thanks for the help,
Sam.