Book a Demo

Author Topic: BPMN Sim - Why the duplicate entries in the Siulation Window?  (Read 3472 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
BPMN Sim - Why the duplicate entries in the Siulation Window?
« on: October 19, 2022, 12:03:10 am »
Here is a simulation run of a specific scenario against a "process Under Simulation"

Code: [Select]
[161809748]      Configuration: mode: Interpreted simulation, platform: BPMN
[161809749]      Preparing Simulation Data
[161812102]      Loading Machine
[161812537]      Simulation Started
[161812546]      2 NOT D&A  Scenario
[161813644]      2 NOT D&A  Scenario.StartEvent1
[161814764]      2 NOT D&A  Scenario.Other Group Scenario setup
[161815875]      2 NOT D&A  Scenario.Call:D&A Report Access Management
[161819196]      2D&A Report Access Management
[161820468]      2D&A Report Access Management.Start report-access incident
[161822393]      2D&A Report Access Management.Submit report-access incident
[161823615]      2D&A Report Access Management.CT Resolver Groups.D&A Resolver Group.Locate Report Owner and other details
[161823616]      2D&A Report Access Management.CT Resolver Groups.D&A Resolver Group.Triage change for applicability
[161823616]      2D&A Report Access Management.CT Resolver Groups.D&A Resolver Group.Triage change for applicability
[161824804]      2D&A Report Access Management.CT Resolver Groups.D&A Resolver Group.Triage change for applicability
[161824826]      2D&A Report Access Management.CT Resolver Groups.Non-D&A Resolver Group.Other Resolver Group to resolve
[161824827]      2D&A Report Access Management.CT Resolver Groups.Non-D&A Resolver Group.Other Resolver Group to resolve
[161826023]      2D&A Report Access Management.CT Resolver Groups.Non-D&A Resolver Group.Other Resolver Group to resolve
[161826027]      2D&A Report Access Management.Agree to close incident
[161826039]      2D&A Report Access Management.Agree to close incident
[161827225]      2D&A Report Access Management.Agree to close incident
[161827233]      2D&A Report Access Management.EndEvent2
[161827238]      2D&A Report Access Management.EndEvent2
[161828842]      2D&A Report Access Management.EndEvent2
[161830087]      2D&A Report Access Management.EndEvent2
[161832533]      2D&A Report Access Management.Agree to close incident
[161833752]      2D&A Report Access Management.EndEvent2
[161834970]      SIMULATION ERROR: invalid assignment left-hand side Expression: $RETURN$_of_2D&A_Report_Access_Management=sim['2D&A Report Access Management'].return;
[161837442]      2 NOT D&A  Scenario.EndEvent1
[161839795]      Simulation Ended

Does anybody know why those duplicate entries are there?

TIA,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Takeshi K

  • EA User
  • **
  • Posts: 632
  • Karma: +43/-1
    • View Profile
    • Sparx Systems Japan
Re: BPMN Sim - Why the duplicate entries in the Siulation Window?
« Reply #1 on: October 19, 2022, 10:52:53 am »
Hello Paolo,

Maybe the 'D&A Resolver Group.Locate Report Owner and other details' has 3 outgoing Sequence flows. They might be place at the same place (so you can see only 1 Sequence flow) or 2 outgoing Sequence flows are hidden.

HTH,
--
t-kouno

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: BPMN Sim - Why the duplicate entries in the Siulation Window?
« Reply #2 on: October 19, 2022, 12:12:45 pm »
Hello Paolo,

Maybe the 'D&A Resolver Group.Locate Report Owner and other details' has 3 outgoing Sequence flows. They might be placed at the same place (so you can see only 1 Sequence flow) or 2 outgoing Sequence flows are hidden.

HTH,
Thanks, Takeshi-san!
I thought that might be the case, but I couldn't find them.  I have now used "insert Related Elements" on the 'D&A Resolver Group.Locate Report Owner and other details' vertex to find the extra, hidden, Sequence Flows and removed them!

Paolo
« Last Edit: October 19, 2022, 01:19:46 pm by Paolo F Cantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Takeshi K

  • EA User
  • **
  • Posts: 632
  • Karma: +43/-1
    • View Profile
    • Sparx Systems Japan
Re: BPMN Sim - Why the duplicate entries in the Siulation Window?
« Reply #3 on: October 19, 2022, 12:21:50 pm »
Hi Paolo,

Please double-click the 'Locate Report Owner' Activity and check the 'Links' group (tab) if 3 outgoing Sequence flows to the 'Triage change for applicability' exist or not. If exist, right-click and delete two of them.

Your similation log is the same when 3 Squence flows exist between the two Activities.
--
t-kouno

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: BPMN Sim - Why the duplicate entries in the Siulation Window?
« Reply #4 on: October 19, 2022, 01:24:18 pm »
Hi Paolo,

Please double-click the 'Locate Report Owner' Activity and check the 'Links' group (tab) if three outgoing Sequence flows to the 'Triage change for applicability' exist or not.  If they exist, right-click and delete two of them.

Your simulation log is the same when 3 Sequence flows exist between the two Activities.
Thanks again, Takeshi-san.
Now that I have fixed the lousy HTML (caused by the forum WYSIWYG editor), you can see I had already removed them.  However, your mechanism is better!

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!