This chapter discusses what to do when working with lots of (logic) elements.

When projects grow bigger, the need to neatly organize the model grows accordingly, especially concerning logic elements. Dealing with large numbers of decision tables, business rules etc. can become a challenge. It is possible to use labels. One or more labels can be assigned to one or more elements. 

Examples of meaningful labels are "Housing benefit eligibility" and "Housing benefit amount" in a housing benefit model or at a more specific level "Income", "Rent" and "Savings". A label has no function other than representing a logical group of elements. Labels are not present in the project export and have therefore no effect in the runtime. Labels can be created from various perspectives, like a logical functional unit, a specific task, a specific product or a specific decision.

Labels appear in the lists of module elements as expansion panels.

All module elements can be labeled. 

  • No labels

3 Comments

  1. It was my understanding Clusters would be removed as of Blueriq 11. Might be a good idea to inform the reader when explaining they could use clusters as a solution.

    1. Thanks! I corrected it.
      I will re-write this section to the use of labels (on my todolist)

      1. I've just rewritten the page so that it is up to date again with the newest version of Blueriq.