You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
Table of contents
Project validation
In Blueriq studio, you can check your model for errors and warnings.
What is it for?
Errors or warnings in your model can lead to unwanted behavior in the runtime. Or you won't even be able to start your project in the runtime, if it contains an error in the (exposed) flow or a fatal error.
Just below the Start button in the runtime dashboard, the number of (fatal) errors, warnings and use of deprecated elements is displayed.
How to validate a project?
When you have opened your project, you can validate it by choosing File > Validate.
That will open a tab in your studio labeled Validation that displays the results.
When you already have a Validation tab open in Studio, you can press the 'Refresh' button in the bottom-left corner to run the validation again.
What is validated?
The Validate function only validates the project that is currently open, including all modules of included libraries that are actually used in your project structure.
Other modules that are not part of the project structure, are not validated.
Project validation results
If all is well, the message "Project is valid!" appears.
Otherwise, the validation consists of two consecutive runs:
Studio errors
The first run looks for studio errors, i.e. errors that were already displayed when you saved (or tried to save) an invalid Blueriq element.
All errors that are found in this run, are displayed in one or more tree structures:
- The root of each tree is the project or library name.
- Its children are the modules containing at least one error or warning.
- The leafs are the errors and warnings themselves.
When you click on one of the leafs to see the error message, often an Open button is displayed that may give you immediate access to the corresponding element (if it is in the module that you are currently working in).
If you have a large amount of errors, they might be alike and a single fix could solve multiple errors. So do not be discouraged immediately if there are many errors.
Runtime errors
Only if no errors were found in the first run, then a second validation run is started to look for a different type of errors, e.g. errors in a flow that could cause problems in the runtime.
Any errors of this type are now displayed as a flat list. Unfortunately, it is not possible to access the corresponding element directly from the error message (no Open button or Ctrl-click option), so you have to navigate to it yourself.
Project validation via the Management Service
It is also possible to validate a project from outside the studio, via the Management Service method ValidateProject.
Overview
Content Tools