References

GitHub

• Backend: https://github.com/Strongminds/kitos/releases/tag/13.2.1

• Frontend: https://github.com/Strongminds/kitos_frontend/releases/tag/13.2.1

JIRA

API ændringer

It System Usage - GDPR - new field validation rules

Starting from this version, to update any properties in a given group the deciding property (e.g. riskAssessment or userSupervision)must be set to “Yes”

Risk Assessment

• If you set any of these fields to a non-null value:

  • riskAssessmentConductedDate

  • riskAssessmentResult

  • riskAssessmentDocumentation

  • riskAssessmentNotes
    then riskAssessment must be “Yes” (either already set or included in the same request).

• If riskAssessment is changed to “No,” “Undecided,” or null, all of the above fields are automatically cleared.

User Supervision

• If you set either userSupervisionDate or userSupervisionDocumentation to a non-null value, then userSupervision must be “Yes.”

  • Changing userSupervision to “No,” “Undecided,” or null will clear both fields.

Data Retention Evaluation

• If you set either nextDataRetentionEvaluationDate or dataRetentionEvaluationFrequencyInMonths to a non-null value, then retentionPeriodDefined must be “Yes.”

  • Changing retentionPeriodDefined to “No,” “Undecided,” or null will clear both fields.

DPIA

• If you set either dpiaDate or dpiaDocumentation to a non-null value, then dpiaConducted must be “Yes.”

  • Changing dpiaConducted to “No,” “Undecided,” or null will clear both fields.

Technical Precautions

• If you set either technicalPrecautionsApplied or technicalPrecautionsDocumentation to a non-null value, then technicalPrecautionsInPlace must be “Yes.”

  • Changing technicalPrecautionsInPlace to “No,” “Undecided,” or null will clear both fields.

These rules are meant to ensure consistency and coherence. For example, there should be no riskAssessmentConductedDate present without riskAssessment being “Yes.”