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

General 

In this screen you will find all the general settings for the features who are not specified for a specific Blueriq component. 

Studio exports

You can define the studio export paths here. Typ the folder that you want to use within the 

spring.config.additional-location
 directory, you can also define the specific files within this directoy, but this is not required.

Table of contents

Shortcuts

 You can create shortcuts for running a project with specific settings with a easy URL, for example lap-1010:8041/server/start/Hospital. You can easily select a project from the list, set the settings you prefer and give the short name to run from the URL.

Timer 

Here you can change the timer interval for the timers used in the proces engine. You can set the timer every hour, every minute or never.

These settings will be stored in the 

spring.config.additional-location
\application.properties file, under the entry blueriq.timer.interval.

The never setting, that in version 9.9 and earlier can only be set directly in the properties, has its use when running on a multi-node environment. It is advised to only let one node evaluate the timers, and set the others to never. When multiple nodes evaluate the same timer in parallel, unexpected behavior such as a doubling of tasks can occur.

Connections 

All the Blueriq connections can be managed in the settings screen, the settings will be saved in 

spring.config.additional-location
\application.properties file.

 

The following connections can be configured: 

  • SQL
  • SOAP HTTP
  • Email
  • Resource  

Authentication & Autorization 

In this screen you can map the Roles defined in Blueriq Studio to the Users created in Runtime.

The roles can be added by typing the role names for each user and use the comma as separator. These settings will be saved in 

spring.config.additional-location
\users.properties file. After saving you have to restart the runtime service.

 

Blueriq provides an out-of-the-box authentication and autorization mechanism for development / demo use only. Passwords are stored plain text in the users.properties and this is not secure enough to use in a production environment.

 

Development

The settings below will be saved in in 

spring.config.additional-location
\application-development-tools.properties file. 

Studio Projects

When you start the runtime for the first time, only the studio exports will be available. In this section you can connect the studio models to the runtime. The URL can be found in Blueriq\Studio\Studio.exe config file (management services).

Passwords are not shown for security reasons. Leaving this field empty will not change the already saved password.

 

Saved sessions

Within the Blueriq application it is possible to save documents/data on the session, this data can be used later on during this session for example to store a uploaded document in the DMS (Document Management System). You can set the directory where to save these files on your computer.

Log Location

Give the location where you would like to save the log data, this will be used by Blueriq Runtime and various widget data. The default location from the Blueriq root directory: logs\log.txt 

Global messages

In this screen the deloperer can change the global messages for each language that is defined for the projects. The globale messages are shown on the screen when you are running the project in Runtime.

The folowing global messages can be edited:

  • Default validation messages
  • Container - Instance Selector messages
  • Service - Service result messages
  • Masks - Boolean, Currency, Date and Number messages
  • Other - Case, document, Event and Task messages
  • No labels

Didn't find the answer you were looking for? Try the advanced search!