- Issue created by @jdleonard
- 🇺🇸United States bluegeek9
I think it is good to be able to lock relationship types.
I don't think any of the current relationships need to be locked.
- 🇺🇸United States jdleonard Austin, TX, USA
Contrived example coming up! Let's say I want to create a family tree (and there's no missing links). I create a module that can traverse sibling and parent Relationships to generate a tree visual. That task is easier (and can benefit from existing data if any) if Sibling and Parent Relationship Types have well-known IDs and are known to be present. CRM could do that.
The (good) reason I can think of to not do so is to not force the presence of the Relationship Types upon end users. Perhaps it would also be helpful to have a Relationship Type base field "Hidden from UI" or "Disabled" or something like that. A way to "get this out of my way" while maintaining its presence for any modules that depend on it.
I'm not full throated on this. A decision on it could certainly be postponed.