topic Re: Using CallActiviti to another Workflow is bypassing Start Event in Alfresco Archive

Using CallActiviti to another Workflow is bypassing Start Event

root — Mon, 26 Aug 2013 15:11:59 GMT

Hi All.I am having an issue using callActiviti. The below steps will try to shade some light on the process I am following:1) Create a basic workflow ( workflowOne)2) Create a second basic workflow. (workflowTwo)3) Testing them individually everything is great.4) Now, using call activiti:<callAct

Re: Using CallActiviti to another Workflow is bypassing Start Event

jbarrez — Tue, 03 Sep 2013 10:04:12 GMT

Smells like a bug. Could you create an executable unit test that demonstrates this?

Re: Using CallActiviti to another Workflow is bypassing Start Event

randallgaz — Tue, 10 Sep 2013 17:09:22 GMT

I have also run into the Query return issue. ("exception": "org.springframework.extensions.webscripts.WebScriptException - 07260017 Wrapped Exception (with status template): Query return 3 results instead of max 1)

The get start task in the alfresco wrapper around the activi call is a get single result. It should be a set. Any child workflow or parallel join with a looping flow will result in more than one result. I believe it is a task history accumulator operation, but have not traced it enough to fully tell.

I do have a test case, but it was 4.0.2. I need to verify that it still exercises the case, and will submit a bug.

Randall

Re: Using CallActiviti to another Workflow is bypassing Start Event

randallgaz — Tue, 10 Sep 2013 21:16:17 GMT

/Ed followed up in this message with the exact location where the issue is:

http://forums.alfresco.com/forum/developer-discussions/workflow/view-details-page-broken-alfresco-using-callactiviti-call

After further debuging I was able to pinpoint the code where the issue is taking place. I may be wrong but the error occurs at this piece of code.

package org.alfresco.repo.workflow.activiti.properties;

ActivitiPropertyConverter.java

    /**
     * @param historicProcessInstance
     * @return
     */
    public Map<String, Object> getStartVariables(HistoricProcessInstance historicProcessInstance)
    {
        // Get historic variable values for start-event
        HistoricActivityInstance startEvent = activitiUtil.getHistoryService()
            .createHistoricActivityInstanceQuery()
            .processInstanceId(historicProcessInstance.getId())
            .activityId(historicProcessInstance.getStartActivityId())
            .singleResult();

        Map<String, Object> variables = getHistoricActivityVariables(startEvent.getId());
        return variables;
    }

Sincerely,
/Ed

- Randall

Re: Using CallActiviti to another Workflow is bypassing Start Event

trademak — Thu, 12 Sep 2013 07:08:58 GMT

Hi,

The problem is that in Alfresco workflow it always looks for a start event definition and a corresponding form config. I'll have a look with one of my colleagues how this could be implemented.

Best regards,

Re: Using CallActiviti to another Workflow is bypassing Start Event

root — Fri, 13 Sep 2013 19:25:04 GMT

Hi All,

Alfresco support is working in a fix for Alfresco version 4.1.6 and 4.2 Enterprise. I don't know if they will apply that same patch to the community edition, but I assume they may.

Thanks for the info.

/Ed