Author Topic: Handling of nested controlled packages  (Read 11059 times)

Jüri

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
    • View Profile
Re: Handling of nested controlled packages
« Reply #15 on: November 20, 2008, 07:53:30 pm »
Hi all!

Does anybody know, can such logic be developed using EA Automated Interface (if sparx does not resolve the problem):

On each Get Latest/Get Package/Check out event automated interface will:
  • Create automatically dummy object for missing object (such way you do not loose connections)
      o If such object (GUID) is imported later to the model, developed add-in will replace previously created dummy object with real object
  • During package checked- in previously developed add-in will   restrict to export (or will remove from xml) previously created dummy objects.
  • Same developed add-in can restrict change of the created dummy object by user (this can be done according to help)

Seams very simple logic!? Can it be done using automated interface? Please help, if you know!:)

Thank you!

DanG83616

  • EA User
  • **
  • Posts: 180
  • Karma: +0/-0
    • View Profile
Re: Handling of nested controlled packages
« Reply #16 on: November 21, 2008, 02:21:43 am »
I cannot see how Sparx doesn't consider this a showstopper. I am now feeling very stupid for creating packages for our entire system only to find that it will be impossible to maintain.

Perhaps Sparx, or some enterprising user, can develop a plugin to check for unresoved links prior to check in.

DanG83616

  • EA User
  • **
  • Posts: 180
  • Karma: +0/-0
    • View Profile
Re: Handling of nested controlled packages
« Reply #17 on: November 21, 2008, 02:24:25 am »
Oops. Sorry, I didn't see Juri's final post. He said what I was only thinking.

Frank Horn

  • EA User
  • **
  • Posts: 535
  • Karma: +1/-0
    • View Profile
Re: Handling of nested controlled packages
« Reply #18 on: November 21, 2008, 07:02:14 pm »
Quote
On each Get Latest/Get Package/Check out event automated interface will:
 • Create automatically dummy object for missing object (such way you do not loose connections)
     o If such object (GUID) is imported later to the model, developed add-in will replace previously created dummy object with real object
 • During package checked- in previously developed add-in will   restrict to export (or will remove from xml) previously created dummy objects.
 • Same developed add-in can restrict change of the created dummy object by user (this can be done according to help)

Good idea, Jüri, but probably not possible the way things are. As far as I know there are no events on check in or check out or get all latest, and not even api methods to call version control functions.