Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-639

Workbench: Support auto-definition of ScoreHolder global variable based on selected Score type

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 7.0.0.Beta2
    • None
    • optaplanner-wb
    • None
    • NEW
    • NEW

      ATM constraint match needs to be specified in the Guided rule editor (GRE) manually, e.g.

      scoreHolder.addHardConstraintMatch(kcontext, - (1 + l.getCourse().getCurriculumList().size()));

      It's important the user doesn't have to specify the scoreHolder global variable anywhere. This should be ideally performed behind the scenes, based on the selected score type in PlannerDataObjectEditor (see solution_type.png). In the first iteration investigate the possibility to generate a .drl file containing the definition of the scoreHolder each time the score type changes.

              mcimbora_jira Matej Čimbora (Inactive)
              mcimbora_jira Matej Čimbora (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: