UPOS 1.15 FTF Avatar
  1. OMG Issue

UPOS — Scale: Inconsistency in MaximumWeight and MinimumWeight description

  • Key: UPOS-8
  • Status: closed  
  • Source: Diebold Nixdorf Global Solutions B.V. ( Mr. Denis Kuniss)
  • Summary:

    Both property descriptions, MaximumWeight and MinimumWeight, contain the following sentence.

    Changing the WeightUnit property will also cause this property to change.

    This sentence is wrong as the property WeightUnit is defined as read-only.

  • Reported: UPOS 1.15b1 — Mon, 27 Aug 2018 11:01 GMT
  • Disposition: Resolved — UPOS 1.15
  • Disposition Summary:

    Replace by a consistent sentence

    Diebold Nixdorf proposes to replace the wrong sentence

    Changing the WeightUnit property will also cause this property to change.

    in properties MaximumWeight and MinimumWeight by the sentence

    The value held by this property must be processed considering the value returned by the WeightUnit property.

    The reason for this is that we have encountered the need to change the WeigthUnit property value from inside the service implementation even after the device has been enabled (what is not forbidden explicitly and therefore considered it as allowed). So, the value may not be fixed during the life time of the service instance. Therefore it is important for an application to process both properties, MaximumWeight/WeightUnit and MinimumWeight/WeightUnit, always together to get correct results.

  • Updated: Mon, 1 Apr 2019 18:20 GMT