nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Having trouble specifying the process for a call activity

fiddleatwork

Hi,

I'm new to Activiti and I'm hoping to use it to model our processes. In the short-term, I will just be modeling them. But hopefully in the future we can deploy them with activiti.

When I add a call process, I go to Main Config and I click on Called Element … which opens up a list of my processes. I select a process. I save my file. But when I click on another item and then come back to my call activity, the called element is not retained. As a result I cannot use the call activity.

Is this a bug? Is there something else I must do to set the called element?

Thank you for your help.

Find more posts tagged with

Comments

mpalka

I experience the same issue with the latest version of the Designer on Eclipse Kepler. Is there any workaround or fix? Shall I report it somewhere?

mpalka

I can see a bug has been reported for this issue already.
http://jira.codehaus.org/browse/ACT-1760

It was supposed to be realeased with version 5.14 of the Designer. Has it been released already? I can see that my Designer version is 5.12. Should the version of the Designer be in sync with the Activity "core" release?

jbarrez

Yes - the designer is following version numbering.
BUT 5.14 has not been released yet. Tijs is fixing up last bits for that release, so it should be any day now that 5.14 designer is released.

fiddleatwork

Could we get this feature in a nightly build? I have to make a choice between Eclipse BPMN2 modeler and Activity Designer and neither of these tools currently support the call activity.

Thanks

ejyanezp

Hello, I had this same issue with the Eclipse Designer 5.14.1. Then I upgrade to 5.15.0 and problem persists. The project of Activiti's Eclipse plugin is apart from Activiti itself. I'll be looking at it trying to help (https://github.com/Activiti/Activiti-Designer). But there is a work around!

Edit the semantic part of the XML process directly:

<br><callActivity id="callactivity1" name="Call activity" calledElement="process-to-call"><br></callActivity><br>
This way the called element will remain in the XML and in the Called Element field of the Main Config tab.

Regards,
e.
PD: do not freeze… act!