Overview
Allows end users of the platform to construct their own grids, charts, and dashboards.
Key Features & Functionality
Note: Appian provides self-service analytics capabilities where end users can explore enterprise data and build their own custom reports. Before downloading this utility, refer to Appian Documentation to see if you can use the available self-service analytics capabilities.
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?
You can leave it blank. If you want to understand what it is used for, check the "Configure Application Specific Dashboards" article in the documentation in the app.
Hi,Can anyone please provide a hint what to put into the properties file for the ## Constant: EUR_APPLICATION_OPTIONS## Type: Text (Array)#### Multiple values can be specified. Use a semicolon between each value.There is nothing in the documentation mentioned to put in there. Maybe it is mentioned in the application, but it is notpossible to import it without the proper settings. Thanks
This is explained in the docs tab "Add a New Field to an Existing Record Type".
Hi Adittya,
That usually happens if your environment is not set to English (US) before importing. The application was built in that language setting and when importing PMs where not all possible languages have labels, these errors happen.
Hope that helps!
Best,
Kai
Hey all - does anybody have any experience with adding fields to records that already exist in EUR?
Hi all,
Facing the below error while deploying the application in 23.3 platform.
processModel 0002e68a-d619-8000-6684-014d98014d98 "": An error occurred while creating processModel [uuid=0002e68a-d619-8000-6684-014d98014d98]: com.appiancorp.process.validation.ValidationException: Process Model is not valid. The process model must have a valid name in the site primary language: English (GB).
Has anyone faced this issue recently. If so, let me know the steps to resolve or the workaround for this
It was the Appian version problem.
Following up here. Is there a workaround yet?