You are viewing the documentation for Blueriq 13. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

The development properties only apply when the profile development-tools is added to the Spring.active.profiles

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

SubjectPropertyExplanationExample
Development


logging.file.name=C:/Deployments/logs/runtime.logThe file in which to write the log

application.properties

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)

application-development-tools.properties

blueriq.development.showToolbar=trueDevelopment Toolbar on/off. default is true

application-development-tools.properties

blueriq.development.usePasswordEncryption=trueWhen editing properties encrypt passwords before saving them.

application-development-tools.properties

blueriq.development.settingsExternallyManaged=falseWhen properties can not be managed by the Blueriq 'development-tools' this can disable the settings menu and reload settings button.

application-development-tools.properties

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/

application-development-tools.properties

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


The combined URL will be expanded in development dashboard.

/flow/{project}/{flow}/{version}/{languageCode}

application-development-tools.properties

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
- name of the shortcut to start


The combined URL will be expanded in development dashboard.
/shortcut/{shortcut}

application-development-tools.properties

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}

application-development-tools.properties

  • No labels