Author Topic: Swim Lanes not owning the element created inside  (Read 4233 times)

ducatiross

  • EA User
  • **
  • Posts: 114
  • Karma: +1/-0
    • View Profile
Swim Lanes not owning the element created inside
« on: January 16, 2014, 02:46:37 am »
Hello everyone.

I have been an Enterprise Architect user for about a year and on the whole, love it !

I've recently had a situation that I cannot find a reason for and hope someone could help.

I have drawn many Business Process diagrams, with swimlanes to represent different roles. Until recently, when I created a new activity and dragged it into a swimlane, the owned-by property of the activity became the swim-lane, which was perfect. Further, if I moved an activity from one swimlane to another, the new swimlane became the owner as I expected.

However, in the last week, this has stopped. If I use an existing swimlane on a diagram, both new activities created in it, and existing ones moved to it DO NOT have the owned-by property set to the swimlane, yet if I create a new swimlane and do either of these things with an activty, it DOES set the property as before.

I am really confused and think I must have changed a setting somewhere in the options that resulted in this, but have no idea how to fix it.

Anyone else have this issue and know of a solution ?

Thanks in advance.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Swim Lanes not owning the element created insi
« Reply #1 on: January 16, 2014, 04:15:09 am »
One idea: Tools/Options/Objects/Support for Composite should be turned on.

q.

ducatiross

  • EA User
  • **
  • Posts: 114
  • Karma: +1/-0
    • View Profile
Re: Swim Lanes not owning the element created insi
« Reply #2 on: January 17, 2014, 03:32:29 am »
Thanks qwerty. I checked this and I did have this option ticked. So it doesn't seem to be that.

However, with some experimenting I have found that :-
- If you create a new package with a diagram, drag some existing swimlanes to it and then create a new Activity object in one of the swimlanes, the Owned-By property of the Activity is not set.
- Finding the Activity in the Browser shows it under the Package I have just created.
- If I then drag it in the browser to the swimlane I want to be its owner, it sets the Owned-By property correctly.
- I can then move the activity between swimlanes on my diagram, and the Owned-By property is correctly changed to the new swimlane.

However, if I add a new diagram instead of a package :-
- I drag some swimlanes in
- I create some new activities in the swimlanes
- The Owned-By property is immediately set to the swimlane, and is changed immediately if I move it between swimlanes.

So, the act of making a package with a diagram results in different behaviour than if a diagram is created on its own.

Moving the diagram to be under the package in the Browser stops this working again, making the Package the default 'owner' of new elements until the element is moved in the browser under another object like a swimlane. Once moved, the element can be dragged on the diagram between swimlanes and the owner changes accordingly. It seems like the scope changes if a diagram is under a package, making the package the default owner of objects, not the element the object was created in (like a swimlane), until the object is explicity moved in the browser, altering the scope. Not sure if I have explained this well enough.

At least I know how to fix this when it happens again - if I can remember !



qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Swim Lanes not owning the element created insi
« Reply #3 on: January 17, 2014, 05:22:28 am »
I can reproduce that. One might look at this as being a bug. Or just EAUI. You should report that anyhow. Sometimes those things can be fixed easily. Sometimes they can be ignored easily. You'll see...

q.

Dermot

  • EA Administrator
  • EA User
  • *****
  • Posts: 591
  • Karma: +7/-0
    • View Profile
Re: Swim Lanes not owning the element created insi
« Reply #4 on: January 20, 2014, 03:45:43 pm »
This issue has been lodged and acknowledged through Registered Support.