Ranking Rules

High-Level Use Case

Ranking rules introduces a matching system that allows users to compare and score records based on flexible criteria. For example, staff members can be matched to training sessions based on required skills (e.g., specific degrees) and nice-to-have attributes (e.g., experience with over 18s).
Similarly, rooms can be matched to training requirements based on features like available equipment or room size. The system will prioritise and order results based on how well they meet the required and nice-to-have criteria, giving users a clear and structured way to make optimal decisions. This should be used on top of conflict checking. So all conflict rules are first taken into account. Then all available can be prioritised/matched/sorted.

Getting started

As it’s in a first version, you first need to install our latest version 6.11 or later Install the latest GoMeddo version and GoMeddo needs to be enabled to use Conflict Rules

Creating and editing rules

Go to the "GoMeddo Rule" tab and click on "New Rule” or select an existing rule from the list.

Please provide a name for this rule. Optionally, link it to a dimension. Mark it as active or inactive. If inactive, the rule will not work or be validated upon save.
Type the formula itself here, using the function and operators in the formula editor.
If the formula is true, it will cause the related record ranking to be incremented/decremented by the weight specified. You can use the syntax checker to validate your rule.
The formula support the following operators and functions listed here, excluding the “dimension” specific ones.
Specify the conflict type: Is it a ranking type
Give it a weight, the higher the weight, the higher it shows up in the intelligent lookups and in the results of the API.
(optionally) Enter a validation message. For ranking rules, this is not currently shown anywhere to the user.
Save the rule. If the rule is marked as active, it will be checked for syntax and referenced fields again.

Currently supports:

Intelligent Lookups
Timeslot Endpoints
Timeslot Picker
Frontend Builder

Doesn’t work yet in
FindAvailableDimensionIds