Alon Moscovitz
Currently, if we have blueprints with relations as follows A -> B -> C, it is not possible to reference C from A using jq since only B is defined in A's entities YAML. This limitation creates issues in scenarios where we have a relations hierarchy such as Team -> Group -> Department. We would like to create an SSA (Self-Service Application) that accepts a team as an input and then references and auto-populates the team's group and department from the provided team, making this data available to downstream systems. We would like this capability to be available across all Portal areas, not just for SSA, but also for dashboards, etc.
Current Workarounds:
  1. Create Form Inputs for All Variables: This approach is tedious and results in a poor user experience.
  2. Use Mirror Properties to Create Direct Relations Between Indirect Relations (e.g., A -> C): This workaround is not ideal because:
* It is a high-maintenance solution that requires altering the model (blueprints) each time indirect data is needed, even though it is defined and logically accessible. This would necessitate defining each such property multiple times, impacting our velocity and time to market.
* This approach would make the related entities graph view effectively unusable, as each entity would have direct relations to every other entity.
Request:
We request the implementation of a feature that allows dynamic referencing of nested entity relations, enabling us to reference and auto-populate nested entities without the need for cumbersome workarounds or loss of functionality of other areas as the graph view.