topic Activiti and Other View Technolgies Integration in Alfresco Archive

Activiti and Other View Technolgies Integration

limcheekin — Wed, 08 Sep 2010 06:37:05 GMT

Hi,We are using Grails GSP as the view layer of the workflow application instead of Activiti Explorer. So we will need to create our own task lists. I will use the vacation request process as an example. Let's say a user submitted a request, at this point a task is pending in management unassigned t

Re: Activiti and Other View Technolgies Integration

jbarrez — Wed, 08 Sep 2010 08:56:25 GMT

The task id is unique per process definition. It is even unique for all the tasks ever created, even when you would run Activiti in a cluster.

So yes, you can use the task id to find the correct process instance for that specific vacaction request.

Re: Activiti and Other View Technolgies Integration

limcheekin — Wed, 08 Sep 2010 10:10:24 GMT

The task id is unique per process definition. It is even unique for all the tasks ever created, even when you would run Activiti in a cluster.

So yes, you can use the task id to find the correct process instance for that specific vacaction request.

Thanks for promptly response. Is this approach is the best way? Do you have better suggestion in mind?

Regards,
Chee Kin

Re: Activiti and Other View Technolgies Integration

jbarrez — Thu, 09 Sep 2010 07:56:23 GMT

I wouldnt use the same id for the task and the vacation request. Rather, I would give the vacation request record a unique id, and store that reference as a process variable (note: I'm not storing the whole vacation request record as a process variable).

Then, if you need the vacation request record, you simply do:
String executionId = task.getExecutionId();
long vacationRequestId = runtimeService.getVariable(executionId, "vacactionRequestId");

Re: Activiti and Other View Technolgies Integration

limcheekin — Fri, 10 Sep 2010 03:37:57 GMT

I wouldnt use the same id for the task and the vacation request. Rather, I would give the vacation request record a unique id, and store that reference as a process variable (note: I'm not storing the whole vacation request record as a process variable).

Then, if you need the vacation request record, you simply do:
String executionId = task.getExecutionId();
long vacationRequestId = runtimeService.getVariable(executionId, "vacactionRequestId");

Thanks for the suggestion and sample code. I think your suggestion was better idea.

Regards,
Chee Kin