Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: CJacks on February 24, 2005, 07:33:04 am

Title: Set Run State
Post by: CJacks on February 24, 2005, 07:33:04 am
I am trying to fill in some deployment documentation with data that is stored in a database. (the subject system stores a lot of its implementation specifications in database tables)  I have been able to create types using the “import DB schema” and create basic objects in the model using the CSV import feature for a package. (using a DB access program to write CSV files from a SQL result set) I then used the automation interface, C#,  to assign the classifier type to the objects. The next step is assigning the runtime state to the objects. I assume I can do this with the automation interface but I haven’t been able to figure out where and how the runtime state is stored.  ???

Could someone tell me, relative to either the diagram object or, preferably, the package element collection the navigation to the runtime state structure for an object?

I need to do this for several tables with up to several hundred records.  :o

Thanks in advance.  :)
Title: Re: Set Run State
Post by: mikewhit on February 24, 2005, 09:29:12 am
(guess) Might well be an Attribute of some type ...?
Title: Re: Set Run State
Post by: CJacks on February 24, 2005, 09:50:14 am
I created an object and put in known values and then checked out the Abstract, Attributes (empty), AttributesEx (point to attributes of classifier), Attribute Tags of AttributesEx(#) (empty), CustomProperties (empty), Elements (empty), Status (different information), Tagged Values (empty) and TaggedValuesEx (empty).

I also looked for an interface that had the correct set of variables and couldn’t find one but that wasn’t an exhaustive check.

For now the information will have to go into the note, but that isn’t very satisfying for the documentation.

Thanks anyway for the suggestion.
Title: Re: Set Run State
Post by: CJacks on February 24, 2005, 10:11:11 am
I might have found it. StateTransistions seems to change number with the addition of another Run State and seems to track correctly.

Now to check.