ESCom's ExposureScenario type knows an IdentificationString (type UUID), the ExposureScenarioName (one or more phrases) and the ExposureScenarioOrder (which is an integer).
Current registrations are typically showingexposure scenario titles like ES<n>: <name>, where would map to ExposureScenarioOrder and would map to ExposureScenarioName. But some registrations show the pattern of ES<ttt>: <name>, where could be numeric, but could also be "4a" or "5b+c". The options I see are:
- Those are not correct. Registrations should be updated. ESCom decides not to support this.
- It does not matter what the registrations are numbered like. For communication in the supply chain, the titles should have just a numeric ordering. (N.B. This is not what customers like, to our experience.)
- We should introduce an additional field to cover the "printable" aphanumeric numbering.
Please advise.
ESCom's ExposureScenario type knows an IdentificationString (type UUID), the ExposureScenarioName (one or more phrases) and the ExposureScenarioOrder (which is an integer).
Current registrations are typically showingexposure scenario titles like
ES<n>: <name>, where would map to ExposureScenarioOrder and would map to ExposureScenarioName. But some registrations show the pattern ofES<ttt>: <name>, where could be numeric, but could also be "4a" or "5b+c". The options I see are:Please advise.