search

17477195 / signavio-core-components

Automatically exported from code.google.com/p/signavio-core-components
GNU General Public License v3.0
0 stars 0 forks source link

BPMN 2.0 Export: Call Activiti becomes Task respectively Sub-Process #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Steps to reproduce the problem:
1. Create a new BPMN 2.0 process with a Task or Sub-Process
2. Set the property is a Call Activity to true
3. Export the BPMN 2.0 XML representation

Expected output:
<callActivity id="23" name="A" calledElement="myReusableProcess" />

Instead I got:
<task completionQuantity="1" startQuantity="1" isForCompensation="false" 
name="A" id="sid-7F69557C-82BB-4F64-A714-E21B3FB62D19"/>
<subProcess triggeredByEvent="false" completionQuantity="1" startQuantity="1" 
isForCompensation="false" name="B" 
id="sid-14D64C28-B39C-4EBC-8AB7-B8261C88BCED"/>

Tested using Activiti Modeler 5.0.beta2 on Kubuntu 10.04 x86_64 GNU/Linux.

I couldn't find the attribute 'calledElement' represented in the UI.

Original issue reported on code.google.com by falko.me...@gmail.com on 5 Oct 2010 at 1:01

GoogleCodeExporter commented 8 years ago 
hi,

I hit the same issue. Any update on this?
seems nobody was assigned to handle this issue

thanks
arief

Original comment by real.sha...@gmail.com on 15 Dec 2010 at 11:02

GoogleCodeExporter commented 8 years ago 
same issue here. Version is activiti 5.0 rc1.

Original comment by dirk.her...@gmail.com on 3 Jan 2011 at 3:04

GoogleCodeExporter commented 8 years ago 
Hi, 

Activiti 5.2, the problem is still unsolved. CallActivity-s do not have a 
calledElement which leads to quite some manual fixing.

Please fix this. (See also: 
http://forums.activiti.org/en/viewtopic.php?f=6&t=335&p=1252&hilit=calledelement
#p1252 )

Original comment by dirk.her...@gmail.com on 7 Feb 2011 at 1:47

GoogleCodeExporter commented 8 years ago

Original comment by nicolas....@googlemail.com on 8 Feb 2011 at 12:22

GoogleCodeExporter commented 8 years ago

Original comment by swbsigna...@googlemail.com on 14 Feb 2011 at 12:16

GoogleCodeExporter commented 8 years ago 
Issue 15 has been merged into this issue.

Original comment by nicolas....@googlemail.com on 15 Feb 2011 at 2:02

GoogleCodeExporter commented 8 years ago 
bug fix commited in revision 49

Original comment by swbsigna...@googlemail.com on 18 Feb 2011 at 2:54

GoogleCodeExporter commented 8 years ago 
Hi, 

I just updated to activiti 5.3/signavio modeler 5.3 and I am not able to find 
the "calledElement". Is revision 49 included in modeler 5.3?

Kind regards

Dirk

Original comment by dirk.her...@gmail.com on 2 Mar 2011 at 2:20

GoogleCodeExporter commented 8 years ago 
Activiti 5.3 is based on revision 50

Original comment by joram.ba...@gmail.com on 2 Mar 2011 at 2:25

GoogleCodeExporter commented 8 years ago 
So what am I missing?

Original comment by dirk.her...@gmail.com on 2 Mar 2011 at 2:58

GoogleCodeExporter commented 8 years ago 
I only see ways to make sub processes as well. I do not find a way to create a 
callActiviti using the modeler in the 5.3 release. Can you point to the docs or 
the way to create call activities in 5.3? (Since the bug was marked as fixed in 
rev 49, and activiti 5.3 is based on Rev 50, I am assuming that rev 50 includes 
changes applied in rev 49.)

Thanks

Original comment by ned.wolp...@gmail.com on 2 Mar 2011 at 5:06

GoogleCodeExporter commented 8 years ago 
If you have a subprocess, select 'call activity' in the right pane.

Original comment by joram.ba...@gmail.com on 2 Mar 2011 at 5:12

GoogleCodeExporter commented 8 years ago 
callActivitys are created when you drag a subprocess and check the "Is a Call 
Activity" checkbox in the Properties frame. However a calledElement attribute 
is missing in the properties and the generated XML. Unfortunately I do not know 
how to validate the resulting XML but from my understanding the calledElement 
attribute is not optional.

Original comment by dirk.her...@gmail.com on 2 Mar 2011 at 5:13

GoogleCodeExporter commented 8 years ago 
Okay, I see the problem was that when starting up, the right-hand 'attributes' 
pane does not exist, nor was there a way to get it to display. Once I 
saved/closed the file via modeler and re-opened it, it was there.  Resulting 
XML for this one element:

      <callActivity completionQuantity="1" id="sid-42ECB13F-A215-453F-B317-4AC1931B2781" isForCompensation="false" name="callOtherThing" startQuantity="1">
         <extensionElements>
            <signavio:signavioMetaData metaKey="bgcolor" metaValue="#ffffcc"/>
         </extensionElements>
      </callActivity>

Original comment by ned.wolp...@gmail.com on 2 Mar 2011 at 5:30

GoogleCodeExporter commented 8 years ago 
The Call Activity issue has been fixed, but the responsible jars of the 
platform extension projects have just been committed in the platform project 
yesterday. 

In the current core components the call activity works as follows:

- If a Task is a call activity, a global task is generated in the XML and 
referenced in the calledElement attribute.
- If an expanded sub process is a call activity, the process is generated in 
the XML and referenced via calledElement attribute.
- Linking a collapsed sub process to another process so that it is contained in 
the xml file is not supported.

Original comment by nicolas....@googlemail.com on 4 Mar 2011 at 10:25

GoogleCodeExporter commented 8 years ago 
Just checked out revision 52. As far as I can see, the calledElement attribute 
is nowhere to be found. Neither in the UI nor in the generated XML files. Am I 
missing something here?

Original comment by Robby.Co...@gmail.com on 24 Jun 2011 at 10:28

GoogleCodeExporter commented 8 years ago 
is this really fixed? Where can I enter the value for calledElement?

Original comment by mwi...@gmail.com on 22 Feb 2012 at 11:34

GoogleCodeExporter commented 8 years ago 
know i got it:

calledElement is not in the ui, the modeler generates a globalTask, like it is 
said in Comment 15:

example:
<?xml version="1.0" encoding="UTF-8"?><definitions 
xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" 
xmlns:activiti="http://activiti.org/bpmn" 
xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" 
xmlns:omgdc="http://www.omg.org/spec/DD/20100524/DC" 
xmlns:omgdi="http://www.omg.org/spec/DD/20100524/DI" 
xmlns:signavio="http://www.signavio.com" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" exporter="Signavio 
Process Editor, http://www.signavio.com" exporterVersion="5.3.1" 
id="sid-87be8c2d-e75c-44cb-8bd7-8dfcbe2b6d23" 
targetNamespace="http://www.signavio.com/bpmn20" 
xsi:schemaLocation="http://www.omg.org/spec/BPMN/20100524/MODEL 
http://www.omg.org/spec/BPMN/2.0/20100501/BPMN20.xsd">
   <globalTask id="sid-1d2a833f-7d52-48f3-b75e-1ebfd289b41b" name="unterprozess"/>
   <process id="Subprozess-Cycle-Test_" isExecutable="false">
      <startEvent id="startEvent_1" name="">
         <outgoing>sequenceFlow_15</outgoing>
      </startEvent>
      <callActivity calledElement="sid-1d2a833f-7d52-48f3-b75e-1ebfd289b41b" completionQuantity="1" id="unterprozess_5" isForCompensation="false" name="unterprozess" startQuantity="1">
         <extensionElements>
            <activiti:in source="x" target="x"/>
            <activiti:out source="y" target="y"/>
         </extensionElements>
         <incoming>sequenceFlow_15</incoming>
         <outgoing>sequenceFlow_18</outgoing>
      </callActivity>
      <endEvent id="endEvent_11" name="">
         <incoming>sequenceFlow_18</incoming>
      </endEvent>
      <sequenceFlow id="sequenceFlow_15" isImmediate="true" name="" sourceRef="startEvent_1" targetRef="unterprozess_5"/>
      <sequenceFlow id="sequenceFlow_18" isImmediate="true" name="" sourceRef="unterprozess_5" targetRef="endEvent_11"/>
   </process>

Original comment by mwi...@gmail.com on 22 Feb 2012 at 2:23