Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

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

Include Page
_PropertiesFileJava
_PropertiesFileJava
.

Create a shortcut

There are multiple ways to configure a shortcut.

Development dashboard

You can configure a shortcut, and its testpaths, via the settings menu of the dashboard

  • Select Settings
  • Select the general tab
  • Select shortcuts
  • Press the add or edit button
  • A pop up window will appear



  • Select the project, branch, flow, language, UI and theme
  • Enter a shortcut name
  • Select save
  • You can now test your shortcut with the following URL: http://HOSTNAME:PORT/Runtime/server/start/SHORTCUTNAME

    Test paths

  • In the screenshot above the available test paths are also listed for the shortcut
  • When you click on the 'Add test path' button or edit button you get the following screen, where you can enter a test path name, and select the branch for the tes tpath.

         

Properties

You can configure a shortcut via the 

Include Page
_PropertiesFileJava
_PropertiesFileJava
 file. This file is located in your 
Include Page
_ConfigLocation
_ConfigLocation
 directory. The properties contain the name of the shortcut

Code Block
languagetext
titleapplication.properties
### 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

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.

Test Paths

From Blueriq 12.8, we added the concept of Test Paths in order to be able to test multi-repository applications. These are applications that span multiple projects, by using AQ_Dashboard_ProjectWidget or AQ_StartProject to start flows from different projects. One can imagine that when testing a feature branch of a project, you wouldn't want to have that same feature branch present in all other projects, especially when nothing has changed in those projects.

...