Loading...

XML

Word

Printable

Instead of having to write

  scoreHolder.addHardConstraintMatch(kcontext, -1);

It should be a business analyst friendly way to express that action, for example just: "Reduce hard score by 1".

The solver configuration's scoreDefinitionType should be taken into account to decide whether there is a medium score etc.

incorporates

PLANNER-775 Workbench: Add scoreHolder global file to Planner kie-wb-playground projects

PLANNER-736 Workbench: Prevent user from creating multiple @PlanningSolution data objects

PLANNER-737 Workbench: scoreHolder global variable generation based on the PlanningSolution score type

is incorporated by

PLANNER-685 Workbench: Epic aggregate issue for mock designs of new features

is related to

PLANNER-704 Workbench: scoreHolder global can only be of org.optaplanner.core.api.score.holder.ScoreHolder type (or subclass)