Author Topic: Automatically save stereotype in specified package  (Read 4029 times)

bITs.EA

  • EA User
  • **
  • Posts: 80
  • Karma: +2/-0
    • View Profile
Automatically save stereotype in specified package
« on: April 07, 2016, 08:32:09 pm »
Simple question: is it possible to save certain stereotypes in a specified package?

Eg. I've created a new stereotype "pain point" and I want to store them automatically in the "pain point package". My problem is the pain points can be created on many different locations and some will be used on different locations too. So I want 1 repository (= package) of pain points.

Is this possible in EA?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13241
  • Karma: +554/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Automatically save stereotype in specified package
« Reply #1 on: April 07, 2016, 09:00:11 pm »
Not out of the box.

But you could write an add-in, or an EA-Matic script to do that.
If you use the EA_OncontextItemModified you could move the element to the appropriate package if it has this specific stereotype.

Geert

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8061
  • Karma: +118/-20
    • View Profile
Re: Automatically save stereotype in specified package
« Reply #2 on: April 08, 2016, 03:03:47 pm »
Warning - I've seen problems by someone automatically moving the package of an element on those broadcasts.

In particular, it breaks things badly when modifying an element from the project browser.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13241
  • Karma: +554/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Automatically save stereotype in specified package
« Reply #3 on: April 08, 2016, 03:42:58 pm »
Warning - I've seen problems by someone automatically moving the package of an element on those broadcasts.

In particular, it breaks things badly when modifying an element from the project browser.
Is that somewhere on the backlog to be fixed?

Geert