Inheritance of relationships and fields in it

[FraukeBAG]

Dear Vincent and hello everyone,
thank you very much for your work and this fantastic tool! :)
I’ve been testing it for a while now and have a suggestion for improvement. Something I already missed in LeanIX is inheritance.
For example, if I have a relation on a child, I want to see it on the parent too without having to maintain it twice.
For instance, I’d like to see all the applications on an overarching capability card that are attached to subordinate capabilities – without always having to go through reporting. The nicest thing would be if you could turn this option on and off for each relationship. Alternatively, a calculated field would be fine for me as well. That, in turn, brings me to a second point: calculations can only write to fields, not to relationship fields, where I would also welcome further fields for description or costs in the relationship. Workflows would of course also be an alternative for inheritance ;)

[vincentmakes]

Hi Frauke

Thank you - maybe I don't fully understand but here's few pointers:

1. The layered dependencies view diagram at card detail level has a couple of options on the left side tool bar to expand levels in general or drill down in children or to parents. When there's either, a little chevron on top or bottom of the card is indicating this. That will give you a good overview already.

2. Calculated field have now (recently) a way to get parent and some properties - have a look at the examples.

Otherwise I think everything is in the reports. I really try to keep the app simple and that means keeping a certain unicity (as much as practical) in the features to not bloat the app. Same principles when doing an app rationalization exercise but at feature level.
Duplicating features between reports and card details would mean for instance that there's a greater risk that the next change is going to introduce a bug by missing the proper ramification. Hope that helps

[FraukeBAG]

Hi Vincent,
thanks for the quick reply :)

1. yes, I know you can see it below, but I still find the handling of the viewer a bit clunky. But that might also be because I'm not used to it. I would find it more useful to see it directly under the relationships without having to scroll down a lot. But I get your point.

2 That's already good, but I still can't write into the relation or create new ones. Is it planned some Day to read any attributes of the children cards? That would be great.
For example I do protection requirement on each App, when I could read the attributes of the children I could automaticli put the highest grade on the parent card.

But don't get me wrong it is still amazing what you did, so it's all good as it is!

[vincentmakes]

For your second point that should already be feasible

If the field key is 'rating' for instance, your formula to surface the max of all direct children at parent level is this, in a dedicated calculated field:

MAX(PLUCK(children,"attributes.rating"))

Or if rating is a select field:

`scores = [MAP_SCORE(c.attributes.rating, {"low": 1, "medium": 2, "high": 3}) for c in children]

MAX(scores)
`

not tested but please give it a try.

The two constraints to be aware of: it's for direct children only and the calculated field is not being updated automatically if a children gets updated

[vincentmakes]

I also spent some time on the inheritance topic: I think I found a way to surface the data without bloating the current relationship section via a simple clickable chip indicating how many descendants have that type of relation. On click, a side panel displays the details. It's primarily a UI change

[FraukeBAG]

Thank you for investing time in that! Thats an great idea :) I'll have an update done and give feedback again.

[FraukeBAG]

Looks good, works, and is actually sufficient for me. Thanks!