End-User Reporting

Thats correct. Wanted to explore that option. As part of this first I updated the constant with my application name.
Then updated my records by linking Application via Application dropdown value.

After this went ahead and created a new report and observed that report entry created in table was missing application field value.

Let me know if this is not the right sequence of steps.

This is hopefully resolved in the newest version. Just make sure to also deploy the Oracle patch on top of the deployment to make sure the CDTs match up with the Oracle column types.

I can fix that issue, but the normal usage of application specific dashboards should use a wrapper of the EUR_Home rule as mentioned in "How to Configure Application Specific Dashboards" article in the documentation.  This will handle the persistence of the application in the reports and dashboards.

Thanks.
Also tried to Configure Application Specific Dashboards, But having issue with this.

Able to save the records with Application. But when I tried to create the new report application value is not persisted in the database table (eurreport). After further debugging realized that logic in the interface EUR_ReportBuilder & EUR_ReportBuilderSetup should be updated to save the selected application value in the respective rule input.
pv!report.application

Thanks for the feedback, I will make these updates.