Fix SET-Event Problem UUID Pattern

Description of the bug:

Das im SET-Schema 1.2.1 verwendete UUID Match Pattern für die Problem Instance verhindert die korrekte Validierung von UUIDs. Beim Pinning für die Version der UUID fehlen die Kleinbuchstaben.

Match pattern: ^(data|metadata|attachment:[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[4][0-9A-Fa-f]{3}-[89AB][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}|reply|submission|other)$

Current behavior:

Es werden bei der Erstellung der Instance für bspw. attachment:{UUID} nicht alle UUIDs korrekt erkannt was zu einem Schema-Validierungsfehler führt (bspw. bei der Erstellung des SET-Events innerhalb eines auto-rejects im JavaSDK).

dev.fitko.fitconnect.api.exceptions.internal.ValidationException: $.events.https://schema.fitko.de/fit-connect/events/reject-submission.problems[0].instance: does not match the regex pattern ^(data|metadata|attachment:[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[4][0-9A-Fa-f]{3}-[89AB][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}|reply|submission|other)$

Expected behavior:

UUIDs werden korrekt gematched. Das Hinzufügen der Kleinbuchstaben mit [89ABab] sollte das Problem beheben. Das soll sowohl für Submission als auch Reply behoben werden (reject-* -> problems -> instance)

Environments:

• Zustelldienst (alle Envs)
• Java-SDK (alle Envs)

Additional Information:

Siehe Instance UUID match Pattern in der Spec: https://git.fitko.de/fit-connect/event-payload/-/blob/main/spec/problems.schema.json?ref_type=heads

Dependency / relationship to other issues:

Responsible person / team:

Contact persons including contact details:

Screenshots / Logs / Requests:

Checklist:

• Add Severity label
• Add team label
• Related/affected issues/stories/epics linked and explained in the bug issue
• Creation of an automated test
• Bugfix deployed on DEV
• Bugfix tested on DEV
• Bugfix deployed on TEST
• Bugfix tested on TEST (possibly also by the connection project itself)
• Successful fix reported to Team Operations (Teams channel)
• Bugfix deployed on STAGE
• Bugfix tested on STAGE if necessary
• Bugfix deployed on PROD
• Bugfix tested on PROD (possibly also by the connection project itself)
• Final communication by Team Operations if necessary
• Internal documentation was checked and updated if necessary
• External documentation has been checked and updated if necessary
• Updated changelog if necessary

Approach/Solution:

Release version of the artifact:

added team::SDK type::Bug labels

changed the description

mentioned in commit event-payload@7e8b380a

removed team::SDK label

added team::ZSD label

mentioned in merge request event-payload!17 (closed)

changed the description

marked this issue as related to #1675 (closed)

changed milestone to %S-1 (PI-7 / Q-1)

changed milestone to %S-1 (PI-8 / Q-2)

mentioned in issue #1521

added Epic::Attachment-Ergonomie label

added component::ZSD label

added workflow::Backlog label

added workflow::Ready for Refinement label and removed workflow::Backlog label

changed milestone to %S-2 (PI-8 / Q-2)

changed the description

added time estimate of 2mo

added workflow::Ready label and removed workflow::Ready for Refinement label

assigned to @Severin_Kistner

added workflow::In Progress label and removed workflow::Ready label

mentioned in commit event-payload@e9ac569c

added workflow::PO Review label and removed workflow::In Progress label

assigned to @hendrik_kamp and unassigned @Severin_Kistner

PO Review OK, bereits auf Main (SET Version noch zu aktualisieren)

added workflow::Ready for DEV deployment label and removed workflow::PO Review label

• Neue Version ist öffentlich verfügbar
• Zustelldienst angepasst und auf DEV

removed Epic::Attachment-Ergonomie label

added Epic::None label

added env::DEV label and removed workflow::Ready for DEV deployment label

added env::TEST label and removed env::DEV label

added env::STAGE label and removed env::TEST label

added env::PROD label and removed env::STAGE label

closed