Add'in: where to store a project's config data

[Guillaume]

Hi,

I'm writing an add'in which requires storing and using parameter values. These values are specific to each EA project, across all its users.

Hence I cannot store them within a config file on each client's PC.
I'm looking for a table to store these values ; usys_system stores key/value pairs which looks suitable to me. Is there any risk in using this? Would you recommend an alternative table or approach?

Thanks

[Ian Mitchell]

eaDocX does what is probably a very naughty thing, as saves a bunch of repository-level settings in t_xref. Seems that EA uses it for all kinds of random stuff, so it seemed an appropriate place.
We save it as XML in the Description field, and index it with our product name in the XRefID field.
@Sparx - this would be a really useful facility to offer in native EA, so that this kind of data could then be exported/imported like other ref data ?

[qwerty]

We once had this discussion here. The most versatile way is to use dedicated elements with tagged values. Using tables or even creating your own tables is possible but export via XMI is likely unsupported.

q.

[Guillaume]

Thanks for your replies. I'll try Ian's approach as XML data will enable me to extend the parameters list.

[Geert Bellekens]

eaDocX does what is probably a very naughty thing, as saves a bunch of repository-level settings in t_xref. Seems that EA uses it for all kinds of random stuff, so it seemed an appropriate place.
We save it as XML in the Description field, and index it with our product name in the XRefID field.
 

That's exactly what I suggested Phil when we discussed a similar issue at the Zurich event  

Another funny place to hide stuff is the notes of a root package. That field exists, but is never shown by EA.

Geert