versioned reference is not always desired

Submitted by bard on Thursday, 13 February, 2014 - 11:11
Issue ID
142
Component
Methodology
Category
Feature request
Priority
Normal
Status
Fixed
Source
Datex stakeholder
Description

The reference from one situation to another is now only feasible by refering to a version of a versioned identifiable of another situation. This is not nice as it generates a lot of traffic which does add unnecesary complexity

Found Version
{"changeLogs":[{"date":1527783402409,"componentOLD":"- Select a value -","component":"Methodology","categoryOLD":"- Select a value -","category":"Feature request","priorityOLD":"- None -","priority":"Normal","statusOLD":"- None -","status":"Fixed"},{"date":1537268973439}]}

Posted by Josef Kaltwasser on August 14, 2023 Permalink

Allowing unversioned references to "VersionedIdentifiable" classes is possible but requires the "version" attribute of the "VersionedReference" type to be optional. This would break backwards compatibility. Hence, the fix cannot be done before version 3.0.