Create a shortcut in the Runtime [editor]

Shortcuts can be used for running a project with specific settings with a user friendly URL. A shortcut refers to a project that is available in the runtime. The following chapter describes how to create a shortcut.

For security reasons we advise you to use shortcuts in a production environment. This can be enabled via the blueriq.production.shortcuts-only in application.properties.

Create a shortcut

There are multiple ways to configure a shortcut.

Development dashboard

You can configure a shortcut via the settings menu of the dashboard

Select Settings
Select the general tab
Select shortcuts
Press the add button
A pop up window will appear
Select the project, branch, flow, language, UI and theme
Enter a shortcut name
Select Add
Select save
You can now test your shortcut with the following URL: http://HOSTNAME:PORT/Runtime/server/start/SHORTCUTNAME

Dynamic shortcuts

When the dynamicVersion property is set to true, the version property is ignored, and the version of the project to be used is looked up by comparing the version of the AQ_Dashboard_ProjectWidget or AQ_StartProject to the version of the project of the current session. If so, that version will be used, otherwise the version set with the version property will be used.

Properties

You can configure a shortcut via the application.properties file. This file is located in your

spring.config.additional-location

directory. The properties contain the name of the shortcut

### Shortcuts - Shortcuts can be started via the URL: http://YOURSERVER:PORT/ROOT/server/start/SHOTCUTNAME ###
blueriq.production.shortcuts-only=false
blueriq.shortcut.ChildSupport.flow=Start
blueriq.shortcut.ChildSupport.languageCode=en-GB
blueriq.shortcut.ChildSupport.project=export-Kinderbijslag
blueriq.shortcut.ChildSupport.theme=forms
blueriq.shortcut.ChildSupport.ui=mvc
blueriq.shortcut.ChildSupport.version=0.0-Wetwijziging
blueriq.shortcut.ChildSupport.dynamicVersion=true
blueriq.shortcut.ChildSupport.privateAccess=false
blueriq.shortcut.ChildSupport.securityEnabled=true

When working with shortcuts for the AQ_StartProject service, you need to think of security. On a production server you set the runtime to blueriq.production.shortcuts-only=true so that end users can not start any flow themselves. As you need to create a shortcut for the application to be called, you do not want that end users could guess the shortcut name and start the flow themselves. For this reason, you should set the property blueriq.shortcut.[name].privateAccess=true for the shortcuts that are only used for the AQ_StartProject service, and which are not started by end users.

It is possible to leave the version of the application out of the URL or shortcut, in which case the latest version of the application is started.

The latest version is determined as follows:

first the major version is compared
then the minor version
then the branch name

Example: 0.0-Wetwijziging

Major version: 0
Minor version: 0
Branch name: Wetwijziging

As all studio exports always have major and minor version equals to 0, only the branch name is the discriminating factor. It is sorted in ascending order, meaning that a branch name starting with 'z' is considered later as a branch name starting with 'a'. In order to make effective use of this mechanism, we advice to use branch names which start with numbers, e.g. 001_4_FeatureBranch.

It is possible to leave the name of the application out of the URL or shortcut, in which case the default application is started.

The default application is determined in Java as being the shortcut that has name 'default'.

Only one default application should be created as multiple defaults could lead to unexpected behavior or errors.

Space shortcuts

Page tree