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.

Designer issues with Subprocess

mark1970

Hi all,
we're currentely evaluating using activiti for a BPMN 2.0 project.We would need to use intensively subprocesses, however we have found some issues with the designer.

#1 The generated BPMN 2.0 xml contains a wrong id for subprocesses' startEvent/endEvent.
See this example generated by Activiti Designer:

  <process id="helloworld" name="helloworld">
    <startEvent id="startevent1" name="Start"></startEvent>
    <endEvent id="endevent1" name="End"></endEvent>
    <subProcess id="subprocess1" name="Sub Process">
      <startEvent id="startevent2" name="Start"></startEvent>
      <serviceTask id="subprocess1_servicetask1" name="Service Task" activiti:class="sample.JavaService"></serviceTask>
      <endEvent id="endevent2" name="End"></endEvent>
      <sequenceFlow id="subprocess1_flow3" name="" sourceRef="subprocess1_startevent2" targetRef="subprocess1_servicetask1"></sequenceFlow>
      <sequenceFlow id="subprocess1_flow4" name="" sourceRef="subprocess1_servicetask1" targetRef="subprocess1_endevent2"></sequenceFlow>
    </subProcess>
    <sequenceFlow id="flow1" name="" sourceRef="startevent1" targetRef="subprocess1"></sequenceFlow>
    <sequenceFlow id="flow2" name="" sourceRef="subprocess1" targetRef="endevent1"></sequenceFlow>
  </process>‍‍‍‍‍‍‍‍‍‍‍‍‍

Here, the sequenceFlow references a source node "subprocess1_startevent2" which should be rather "startevent2".

 <sequenceFlow id="subprocess1_flow3" name="" sourceRef="subprocess1_startevent2" targetRef="subprocess1_servicetask1"></sequenceFlow>‍

The same for subprocess1_flow4.

#2 We would need very much a reusable sub process definition in the Designer. Do you know in which release will be available Call Activity in the Eclipse Designer ?

Thanks a lot
Mark

Find more posts tagged with

Comments

tiesebarrell

Hi Mark,

the bug you mentioned has been resolved and the fix will be in the next release, which should be somewhere in the first week of March.

As far as I know, CallActivity hasn't been added yet. However, I had already noted that as something we should be adding soon. No release planned yet, but thanks for the reminder.

mark1970

Hello tiesebarrel, thank you very much for the quick reply. So, will be waiting for March release. Thanks again
Mark

totyumengr

Hi Tiese,

Use 0.8.0, the ID of element in subprocess have add a prefix(subprocess id),

<subProcess id="subprocess3" name="&#31649;&#29702;&#23618;&#23457;&#26680;"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <startEvent id="subprocess3startevent6" name="Start"></startEvent>

but the bpmndi namespace's element not refer the correct id(startevent6 –>subprocess3startevent6).

<br><bpmndi:BPMNShape bpmnElement="subprocess3" id="BPMNShape_subprocess3"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <omgdc:Bounds height="379" width="801" x="140" y="89"></omgdc:Bounds><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </bpmndi:BPMNShape><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <bpmndi:BPMNShape bpmnElement="startevent6" id="BPMNShape_startevent6"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <omgdc:Bounds height="55" width="55" x="150" y="117"></omgdc:Bounds><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </bpmndi:BPMNShape><br>

Before next release, what i can do to resolve it?

trademak

Hi,

I understand this is a bug an we should fix this, but what's the problem you are running into?
The BPMNDI information is there to make the diagrams interchangeable between tools like the modeler, but nothing more.
So let me know why you want to know how to resolve this before the next release.

Thanks,

totyumengr

Hi Tijs,

So let me know why you want to know how to resolve this before the next release.

I design bpmn20 model use Eclipse designer, this will generate BPMNDI information in model file,
when i try to deploy this model, error occurred

Invalid reference in 'bpmnElement' attribute, sequenceFlow flow40not found | rill/activiti5/pangu/pg-support.bpmn20.xml | line 154 | column 66<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.util.xml.Parse.throwActivitiExceptionForErrors(Parse.java:190)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.bpmn.parser.BpmnParse.execute(BpmnParse.java:172)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.bpmn.deployer.BpmnDeployer.deploy(BpmnDeployer.java:76)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.db.DbRepositorySession.deploy(DbRepositorySession.java:65)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.cmd.DeployCmd.execute(DeployCmd.java:53)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.cmd.DeployCmd.execute(DeployCmd.java:30)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.interceptor.CommandExecutorImpl.execute(CommandExecutorImpl.java:24)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:42)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.RepositoryServiceImpl.deploy(RepositoryServiceImpl.java:43)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.repository.DeploymentBuilderImpl.deploy(DeploymentBuilderImpl.java:103)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.test.TestHelper.annotationDeploymentSetUp(TestHelper.java:96)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.activiti.engine.impl.test.AbstractActivitiTestCase.runBare(AbstractActivitiTestCase.java:87)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at junit.framework.TestResult$1.protect(TestResult.java:110)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at junit.framework.TestResult.runProtected(TestResult.java:128)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at junit.framework.TestResult.run(TestResult.java:113)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at junit.framework.TestCase.run(TestCase.java:124)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at junit.framework.TestSuite.runTest(TestSuite.java:232)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at junit.framework.TestSuite.run(TestSuite.java:227)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:515)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1031)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:888)<br>&nbsp; [org.activiti.engine.impl.interceptor.CommandContext]<br>

Delete BPMNDI fragment manually, parse OK.
So i want to know:Activiti designer have nightly-build version? So i do not need to wait a month

Or does designer have a configuration to prevent BPMNDI fragment generation?

trademak

Hi,

I didn't think of that one. That's an annoying bug.
That's why I fixed it and released an archived site with the fix.
You can find it here: http://activiti.org/designer/archived/activiti-designer-0.8.0.1.zip.
That should work.

Best regards,

totyumengr

Hi Tijs,

It's working OK now!
Wonderful~~Thanks~

PS:
To resolve it once, i commented parse method[BpmnParse#parseDiagramInterchangeElements()] to ignore BPMNDI parsing.

h_ter_schuur

Thijs,

Great to hear you fixed this issue. Could you also assign the related JIRA issue (ACT-670) to yourself and resolve the issue in the issue tracker.

[size=85]P.S. Is it possible to make the activiti designer a separate project in the JIRA issue tracker, or change the versioning scheme of the Eclipse designer. It is hard to search on version specific desginer issues (unless one knows that Activiti 5.3 matches Designer version 0.8.0)[/size]

trademak

Hinse,

Thanks for the pointer.
Regarding the JIRA issue tracker. Did you already tried using the components link and then choose for the Activiti Designer?
There you can easily browse through all open issues for the Designer. Note that there are a lot issues we created ourselves to remember us about certain functionality.

Best regards,

aklemp

Hi,

I'm using the provided designer version 0.8.0.1 which is a great step forward in using call activities and inline subprocesses. Unfortunately I'm having a minor and a blocking issue with it.

The minor one: inline sub processes cannot be nested. This is currently not required but might be a nice feature for someone someday.

Far more critical is the call activity. Using it leads to an exception deep in the XML parser when opening the workflow again in the designer. I noticed that the attribute is now "calledElementRef" instead of "calledElement". Unfortunately, it doesn't work if I manually rename it back to "calledElement". I'm not sure why the designer must be able to resolve the workflow as it might be available at runtime only and not during design time.

Thanks a lot for your help in advance
aklemp

Generated BPMN 2.0 snippet:

<br><bpmn2:CallActivity id="callactivity5" name="Call Activity" incoming="flow28" outgoing="flow133" calledElementRef="SubGraphTest1"/><br>

Error message:

<br>Could not open the editor: org.eclipse.emf.ecore.xmi.UnresolvedReferenceException: Unresolved reference 'SubGraphTest1'. (platform:/resource/test/bpm/graph/GraphTest1.activiti, 1190, 134)<br>

Stacktrace:

<br>org.eclipse.emf.ecore.xmi.UnresolvedReferenceException: Unresolved reference 'SubGraphTest1'. (platform:/resource/test/bpm/graph/GraphTest1.activiti, 1190, 134)<br> at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleForwardReferences(XMLHandler.java:1154)<br> at org.eclipse.emf.ecore.xmi.impl.XMLHandler.endDocument(XMLHandler.java:1228)<br> at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endDocument(AbstractSAXParser.java:737)<br> at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:516)<br> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)<br> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)<br> at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)<br> at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)<br> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)<br> at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)<br> at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:181)<br> at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:180)<br> at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1494)<br> at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1282)<br> at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:255)<br> at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:270)<br> at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:397)<br> at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getEObject(ResourceSetImpl.java:216)<br> at org.eclipse.graphiti.ui.editor.DiagramEditorInput.getEObject(DiagramEditorInput.java:676)<br> at org.eclipse.graphiti.ui.editor.DiagramEditorInput.setEditorEditingDomain(DiagramEditorInput.java:571)<br> at org.eclipse.graphiti.ui.editor.DiagramEditorInput.<init>(DiagramEditorInput.java:268)<br> at org.eclipse.graphiti.ui.editor.DiagramEditorFactory.createEditorInput(DiagramEditorFactory.java:76)<br> at org.eclipse.graphiti.ui.internal.editor.DiagramEditorInternal.init(DiagramEditorInternal.java:1063)<br> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:237)<br> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:211)<br> at org.activiti.designer.eclipse.editor.ActivitiMultiPageEditor.createDiagramPage(ActivitiMultiPageEditor.java:69)<br> at org.activiti.designer.eclipse.editor.ActivitiMultiPageEditor.createPages(ActivitiMultiPageEditor.java:89)<br>&nbsp;&nbsp; [&hellip;]<br>

trademak

Thanks for reporting the calledElement bug. I'll look into it.
About the sub process nesting, yes this is a limitation at the moment.
In coming releases we may remove this limitation, if there's enough user request for this.

Best regards,

aklemp

Hi,

here is another issue with the designer 0.8.0.1. Using boundary timer events in activities of sub processes doesn't work correctly. The coordinates of the timer are not stored in the XML which leads to validation exceptions during deployment of the workflow. It is working correctly when adding a boundary timer event to the sub process directly (i.e. not to an embedded activity). But of course this is not a workaround since the timer leaves the sub process and not the activity.

Regards,
aklemp

trademak

Hi,

Right. I've fixed this in the trunk.

Best regards,

walterjs

I've had a go at implementing the nesting of sub-processes. Here is the JIRA.

http://jira.codehaus.org/browse/ACT-892.