Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Understanding report grids and extended use-cases #7148

Open
2 tasks
mcleo-d opened this issue Sep 23, 2024 · 1 comment
Open
2 tasks

Understanding report grids and extended use-cases #7148

mcleo-d opened this issue Sep 23, 2024 · 1 comment

Comments

@mcleo-d
Copy link
Member

mcleo-d commented Sep 23, 2024

The following question was raised by @nitin-bhagwat from NatWest Group below ...
#7098 (comment)

Question

Hi Team
We would like to have better understanding on report grids and its extended use-cases. Few queries are listed below:

  • How to add more subjects in reporting grid feature?
  • How can more data entity can be added into subjects in reporting grid?
@davidwatkins73
Copy link
Member

The report grid can render cells based on a fixed set of relationships it understands. For example, it can render any assessment rating value as the link from an app to an assessment is fairly simple to traverse (Assessment Def, Application, Assessment Rating, Rating Scheme Item). Similarly it supports all the base relationships seen in this screenshot:

image

To increase the coverage of these types would require changes to the report grid implementation code: org.finos.waltz.data.report_grid.ReportGridDao. This code basically looks at all the column definitions and groups them by their type (survey questions, involvement, assessments etc) and then constructs makes some bulk queries to fetch the data and rejoin tem (see the methods prefixed with fetch).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants