Page History
The development properties only apply when the profile
| Include Page | ||||
|---|---|---|---|---|
|
Since Blueriq 13.13 the development tools have been updated. The new toolset, which has been available to activate for a long time, has now been made the default.
We still support the old toolset, switching between the two version is described on page Switching between development toolsets
| Subject | Property | Explanation | Example | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Development | logging.file.name | Subject | Property | Explanation | Developmentblueriq.development.logresource | The name of the logresource (required for enabling logresource) | |||||||||||||
| Include Page | _PropertiesDevelopmentTools | _PropertiesDevelopmentTools | blueriq.development.logresource.file.logfile=C:/Deployments/logs/runtime.log | The file in which to write the log |
| ||||||||||||||
| blueriq.development.sessionStore.dir=C:/Deployments/SessionStore/ | Path to where the sessionstore file can be found.(if property is present, it will be enabled by default) |
| |||||||||||||||||
| blueriq.development.showToolbar=true | Development Toolbar on/off. default is true |
| |||||||||||||||||
| blueriq.development.usePasswordEncryption=true | When editing properties encrypt passwords before saving them. |
| |||||||||||||||||
| blueriq.development.settingsExternallyManaged=false | When properties can not be managed by the Blueriq 'development-tools' this can disable the settings menu and reload settings button. |
| |||||||||||||||||
| 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