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

Table of contents

Subpages

By clicking the  icon in runtime, which is accessible via Runtime toolbar > Profile > Entity, a decision requirements graph (DRG) will be shown. This icon is only shown in case of default set and system set attributes; not on user set attributes. An example of such a runtime DRG is shown below.

Elements

Every decision is built up of the following parts:

  1. The first cell shows the name of the decision, which in fact is the attribute name that is derived, e.g. Verzekerde.Kinderbijslag.
  2. The cell containing 'Expression' is the name of the business knowledge model, which is the logic element used. The text 'Expression' indicates that the calculation is performed by an expression which is put as default on the attribute. In case of a decision that is inferred by a decision table and this decision table contains a functional name, that functional name will be shown here. Otherwise, the technical name is shown.
  3. The first row of the two-column table, which is shown in dark grey, is the name of the attribute and the value of the result.
  4. The grey lines are:
    • references to input data. This is data which is necessary to infer the decision.
    • references to input from other decisions. These decisions are shown as child decisions (Kind.RechtOpKinderbijslag and Kind.BasisKinderbijslagBedrag).
  5. At the bottom the description is shown of the decision. In fact, this is the justification text which is attached to the attribute.

Interaction

To interact with the decision requirements graph, a user can use the following functionality:

  • Clicking a dark grey 'title' box will open it and will show all details. Clicking the '-' will bring the decision back to its small size and grey background.
  • Clicking the '+' sign will show the child decisions.
  • Clicking the  sign will set this decision as the main decision on top of the screen. By clicking 'Select previous' in the top left corner, it is possible to return to the previous diagram.
  • Clicking and moving will move the complete diagram.

Traceability

There could be a need to store a decision. This is appropriate if someone wants to find out, how and with which data and rules a decision was made. To do this see also traceability.

  • No labels

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