Page History
The development properties only apply when the profile
| Include Page | ||||
|---|---|---|---|---|
|
| Subject | Property | Explanation | Example | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Development | logging.file.name=C:/Deployments/logs/runtime.log | The file in which to write the log |
| |||||||
| blueriq.development.usePasswordEncryption=true | When editing properties encrypt passwords before saving them. |
| ||||||||
| blueriq.development.configuration.sanitize-keys | A comma-separated list of strings. Any keys of OS Environment Variables and Java System Properties that contain any value in this list will be sanitized before being displayed in the Blueriq Runtime Development Dashboard, meaning that they will be replaced by '******'. Default: | |||||||||
| Studio | blueriq.studio.description | description that is used in the development dashboard flow starter. default via installer = Studio Projects |
| |||||||
| blueriq.studio.prefix | The prefix in front of the studio project when started. default via installer = studio |
| ||||||||
| blueriq.studio.authentication | Method of authentication that the Blueriq Studio uses. Its value always is |
| ||||||||
| blueriq.studio.url | url where the management service of the Blueriq Studio can be reached. default via installer = http://HOSTNAME:PORT/Studio/Server/Services/ManagementService |
| ||||||||
| blueriq.studio.domain | Network domain where the studio is in. default via installer = empty |
| ||||||||
| blueriq.studio.username | Username for the studio management service. default via installer = runtime |
| ||||||||
| blueriq.studio.password | Password for the studio management service default via installer = runtime |
| ||||||||
| External | blueriq.external.themes.[name].baseUrl | URL where the external theme is can be reached. When using a custom made them which is not configured via the Runtime using an STG, but rather via a CDN or reverse proxy. An external theme can be configured so that the development dashboard can create URL's to the corresponding targets. | https://example.com/ |
| ||||||
| blueriq.external.themes.[name].template.flow | RFC-6570 URI template for creating a start flow request. By combining the baseUrl and template.flow properties a full URL is formed. The variables which can be used in the URI template are: flow - name of the flow to start project - name of the project to use version - project version to use languageCode - code of the language to use testPath - name of the test path to use The combined URL will be expanded in development dashboard. | /flow/{project}/{flow} With test path: /flow/{project}/{flow} |
| |||||||
| blueriq.external.themes.[name].template.shortcut | RFC-6570 URI template for creating a start shortcut request. By combining the baseUrl and template.shortcut properties a full URL is formed. The variables which can be used in the URI template are: shortcut | /shortcut/{shortcut} |
| |||||||
| blueriq.external.themes.[name].template.session | RFC-6570 URI template for creating a continue session request. By combining the baseUrl and template.session properties a full URL is formed. The variables which can be used in the URI template are: sessionId - id of the session to continue The combined URL will be expanded in development dashboard. | /session/{sessionId} |
|
Overview
Content Tools