Book a Demo

Author Topic: Links custom properties  (Read 3280 times)

Denis Avdonin

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Links custom properties
« on: September 06, 2007, 06:40:13 am »
Hi All,

Does anyone know if it is possible to configure custom properties for different type of links? For example, for an association in the 'Advanced->Custom Properties' context menu I can see 'isDerived' property. For a generalization the same dialogue presents 'isSubstitutable'. And for aggregations there is no 'Custom Properties' sub-menu item available at all. How does one configure these though? Or is it possible at all?

I have tried to find an answer in the documentation and search this forum, but no luck so far. So any pointers are very much appreciated.

Thank you.

Denis

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Links custom properties
« Reply #1 on: September 06, 2007, 09:43:56 am »
Denis,

I was doing something related to this only yesterday.

Sadly, I can confirm that custom properties are still documented as read-only. Even more sadly, I can confirm that the documentation is still correct in this regard.

You'll have to do something like open a second channel to the database via something like OLEDB, then update the fields yourself. Be careful until you know exactly what to put in the fields.

David
No, you can't have it!

RoyC

  • EA Administrator
  • EA Practitioner
  • *****
  • Posts: 1297
  • Karma: +21/-4
  • Read The Help!
    • View Profile
Re: Links custom properties
« Reply #2 on: September 06, 2007, 02:09:03 pm »
You are correct David, although you can change the values of the properties. The relevant topic is at:

http://www.sparxsystems.com.au/EAUserGuide/index.html?advancedpropertiesdialog.htm

The topic is a little obscure, so I have clarified the text and put in more index entries to help locate the information. Those changes will wash through at the next build release.

Roy
« Last Edit: September 06, 2007, 02:11:54 pm by RoyC »
Best Regards, Roy

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Links custom properties
« Reply #3 on: September 07, 2007, 05:02:45 am »
Thanks Roy,

This is particularly important in recent builds. In data modeling the new style for representing stored procedures as individual classes uses a property for the code.

David
No, you can't have it!

nrocha

  • EA Novice
  • *
  • Posts: 11
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Links custom properties
« Reply #4 on: November 22, 2007, 06:55:01 am »
Quote
Denis,

I was doing something related to this only yesterday.

Sadly, I can confirm that custom properties are still documented as read-only. Even more sadly, I can confirm that the documentation is still correct in this regard.

You'll have to do something like open a second channel to the database via something like OLEDB, then update the fields yourself. Be careful until you know exactly what to put in the fields.

David


I'm currently trying to do exactly this (extract the values of the custom properties from the DBMS) but I can't find the place where they are...

Having the ID of an object/element, how can I access its custom properties and their values??

Regards.

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Links custom properties
« Reply #5 on: November 22, 2007, 11:02:23 am »
In build 818 some of the documentation for this seems to have evaporated.

My understanding is that there is an Element.Properties collection. The collection itself is (I believe) read-only. That is, you might not be able to add a new property via automation. [I could be quite wrong here, and this information is missing from the current documentation.]

Each member of the above collection is a Property structure - this is not a property in the sense of a UML class, but an EA API data structure. Each property has several read only fields: Name, PropType (from an enumeration), and a Validation string which you can parse and use for your own purposes. The property also has a variant Value field, which you may read and write.

David
No, you can't have it!