Book a Demo

Author Topic: BPMN 1.1 versus BPMN 1.0 issue  (Read 3047 times)

jodsm

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
BPMN 1.1 versus BPMN 1.0 issue
« on: October 16, 2009, 09:43:11 pm »
After working for a while with EA 7.1 we have a number of BPMN 1.0 compliant diagrams. We recently upgraded to EA 7.5 (846) . Some of the diagrams must be adapted to the new spec (1.1). Unfortunately, the upgrading of 1.0 artifacts is not working as described in the manual :
"If you want a new element to revert to the BPMN version 1.0 appearance, set the Tagged Value to 1.0. Conversely, if you want an older element to assume the BPMN version 1.1 appearance, assign the BPMNVersion Tagged Value to it, with the value 1.1."
Adding a new Tagged Value (in the tagged values window for the element) to an existing (in this case intermediate) event and giving it the value 1.1 does not result in an element that can be of trigger type signal, nor can we make it catching or throwing.  :-/

Besides that, it is apparently still not possible to attach dataObjects to a sequence flow (notes or constraints are possible via the right click/attach...). This makes the MDG not fully compliant with the specs.
Any help would be greatly appreciated

jodsm

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: BPMN 1.1 versus BPMN 1.0 issue
« Reply #1 on: October 19, 2009, 09:13:38 pm »
adding several tagged values such as BPMNVersion, CatchOrThrow and specifying the list values seems to do the trick. When adding p.e. BPMNVersion as a tag, giving it the value 1.1 and then adding Signal in the list of triggers (that is result in case of an end event) one can have the event with a 1.1 appearance. But doing this for a lot of events becomes a tedious timeconsuming business.
Apparently, there is no way of synchronizing tag values for events as there is for flow objects (Pool, Activity, Process...). Am I overlooking something ?