Page History
Shortcuts can be used for running starting a project with specific settings with a user friendly URL. A shortcut refers to a project that is available in the runtimeRuntime. The following chapter describes how to create a shortcut.
Note | ||||||
---|---|---|---|---|---|---|
For security reasons we advise you to only use shortcuts in a production environment. This can be enabled via the
|
...
- 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 saveClick '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 test path.
...
Anchor | ||||
---|---|---|---|---|
|
From In 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.
In Blueriq 12.9, we added support for test paths for Container type: AQ_ExternalFlow, AQ_RestServiceClient and AQ_SoapServiceClient.
...
When using this feature, keep the following in mind:
- Test Paths only work when the Runtime is in development mode
- Test Paths only work when using shortcuts to indicate the entry point of the project to start
- Test Paths only work for Studio projects, not for project exports or publisher exports.
...
This indicates that when the application is started with Test Path feature1
, the project should use 0.0-FeatureBranch1
instead if of the version indicated by blueriq.shortcut.ChildSupport.version
.
...
Selecting a Test Path will have this result in the following behavior:
- When the selected Test Path is defined for the shortcut, the corresponding version of the project is started instead of the default version.
- When the selected Test Path is not defined for the shortcut, the default version of the project is started.
- When the selected Test Path is defined, but the corresponding version doesn't exist in the project, an error is returned.
...
Info |
---|
When a feature is done and the corresponding branch is merged, the Test Path is not automatically deleted. As a maintainer of the shortcuts, you should remove Test Paths for these versions manually. |
Tip |
---|
When working with shortcuts for the AQ_StartProject service, you need to think of security. On a production server you set the runtime to |
UI Text Box | ||
---|---|---|
| ||
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:
Example: 0.0-Wetwijziging
As Since for all studio exports always have the major and minor version equals always are equal 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. |
UI Text Box | ||
---|---|---|
| ||
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 by the Runtime, as being the shortcut that has the name 'default'.
|
...