team notification on package changes ?

[JohnDoe]

Hi,

is there a possibility to inform EA users, if model changes are saved to DB ? We plan to setup a group of EA modellers (50+) all editing different parts of the models. The question came up, how to inform each other, that model changes happened.

Of course there is the option to use the element matrix and reports, but these reports have to be done manually. Our team needs some mechanism to be informed about new and changed elements.

Regards
Bernd

[thomas.kilian]

Database triggers could do that fairly easy. However, the number of change message might be seen as spam :-/

[JohnDoe]

Of course, there could be triggers on database level, but this would be a solution independent of EA.

I was hoping that it could be possible to "subscribe" to some events as a user.

Regards
Bernd

[«Midnight»]

Perhaps the ModelWatcher class is what you need. Check it out in the help file under the Repository section of the SDK.

I am using the help file compiled 2008-02-22, but I think this has been around for a little while.

HTH, David

[JohnDoe]

Thanks midnight,

I haven't used the SDK. Do I need to install a compiler/IDE (c, c#, Java) to use the SDK, or is there another option to make use of these features ?

By the way: Using SDK functionality means, my EA client has to be running online to discover model changes ?

Regards
Bernd

[«Midnight»]

Sorry Bernd,

I did not explain this well. The SDK was issued in draft form around a year ago. Since then Sparx incorporated it into the EA documentation, rather than continue to split it off.

So...

Now the SDK is the old API reference - you'll see it if you traverse the contents tree of the EA help file - with newer material added.

[I fell into the habit of referring to this part of the documentation as the SDK while the SDK (work with me) was in beta. After it was 'reabsorbed' into the main documentation it kept the SDK acronym (in part of its title) so I continued to use the term.

Excuse ends.]

So, what I was referring to was the documentation of the very same API as we all know and love. Read it again and you'll find the reference.

Sorry to have caused the confusion.

David