End-User Reporting

While updating from 2.8.0 to 3.0.0 found below issues with documentation and scripts

• MariaDB upgrade Script [line 80 in the 2.8.0 to 3.0.0.sql]:
  ALTER TABLE `eurtagging` ADD CONSTRAINT `eurtagging_tag` FOREIGN KEY (`tagId`) REFERENCES `eurtag`(`tagId`) ON DELETE CASCADE ACTION ON UPDATE CASCADE;
  [Action is not needed in the script]

• Application Properties file (2.8.0 to 3.0.0.properties):

            Properties file missing entry for newly created environment constants SHRD_APPIAN_API_KEY & SHRD_USE_CACHE

Thanks for the feedback, I will make these updates.

Thanks for the feedback, I will make these updates.

You can simply use the properties file from the new installation or copy the values from below.  The shrd_appian_api_key isn't used by this application (needed for other applications like Data Generator) so you can leave it as a placeholder.

## Constant: SHRD_APPIAN_API_KEY
## Type: Text
##
## Text values will be displayed in Appian exactly as they are
## specified here. No spaces are trimmed. Values do not need to be
## encased in quotation marks.
content._a-0000e8bf-9e14-8000-9c71-011c48011c48_10790867.VALUE=fakeApiKey

## Constant: SHRD_USE_CACHE
## Type: Boolean
##
## Boolean values must be specified as either the text TRUE or FALSE.
content._a-0000e97a-50e6-8000-4051-01ef9001ef90_11717.VALUE=TRUE

Hi Michael, I downloaded the App package this week to upgrade from 2.8.0 to 3.0.0, but I'm experiencing the same problems as manjunathb0904. I manually fixed the SQL script but I still need the updated PROPERTIES file. Can you provide me the updated package?

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.

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