Skip to content

Missing AwardCriterion threshold Constraint linkage #154

@schivmeister

Description

@schivmeister

Problem

This occurs due to an unwarranted connection to Constraint from SelectionCriterion and missing AwardCriterion TriplesMap for ND-LotAwardThresholdCriterionParameter number-threshold. Affects BT-5423-Lot and BT-541-Lot-ThresholdNumber. Issue can be observed in notice 775926-2023 (CN v1.10).

There is also a missing linkage for the ND-LotAwardFixedCriterionParameter number-fixed counterpart, affecting BT-5422-Lot and BT-541-Lot-FixedNumber, due to duplicate connection for the ND-LotAwardWeightCriterionParameter number-weight counterpart. This is not evident in the above notice but may be in others.

Potential Fix

A fix would involve a thorough analysis of the root caus(es), but in general, the solution would likely revolve around creating the right TriplesMaps to accommodate the relevant predicateObjectMaps so that the right connections are established.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdeferred

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions