Improved naming options for relations
As a Solution builder
I want be able use the reverse relationship name to display in (for instance) matrices.
So That I can give a better reflection of the metamodel from the point of view of "one element" in it. I am sure there are other uses as well, but this is the one most important to us at the moment.
Benefits Improved ability display single element from the meta model and show all the "incoming" relationships by the name they use in (for instance) queries.
Acceptance Criteria
- Ability to use "reverse relationship name" under "relationship" in naming convention.
Customer / Originator LFV
Priority Low
-
Hi Matthew,
Yes, something along the lines of "Type (reverse)" is what I am after. For the "a lot of permutations" comment, are you talking about things like "Src" Type (reverse) "Dest"?
Our need is (at the moment) just to have "Type (reverse)" in this list. However, if I was to wish freely, I would like a better way of creating naming conventions, possibly by being able to combine a set of tags freely, those tags being:
- Name
- Source
- Destination
- Type
- Type (reverse)
- "Free form text" (e.g. for creating blank spaces and/or other separating characters)
The dialog would need some reworking and possibly the same concept would need be applied to all of the above naming conventions. The way I see it, this would benefit us in what we display and how and you in that adding new tags would probably be easier, than adding options ad infinitum to satisfy singular client needs as they arise...
Makes sense?
-kHz
Please sign in to leave a comment.
Comments
4 comments