...

Flow

When modeling a flow you should always include a page before and after this service. This is due to browser behavior and security reasons in handling opening popups and/or new tabs.

Security

As a project, you need to be aware of security when communication is involved. The communication between the starting and started application is done with server internally in code. This means that it is perfectly secure as no data can be intercepted or changed.

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.

Example

The above service uses an attribute with a value list of possibly case types. Depending on the type of subsidy, a different application is opened that is responsible for handling that type of subsidy cases. The application is opened as new tab, and important information is passed to the other application. This information is the subsidy ID and a string to indicate what dashboard page to open. The flow in the other application has a split node in the flow, which uses this string to determine to what page to flow.

Known issues