Automatic Case Classification (Case Surveillance)

Below you have the 2 separate description on how the case classification mechanism works on Luxemburg compared to other servers.

• the “caseClassificationCalculationButton” is currently visible only on German servers.

Case classification description for all servers except Luxembourg

• there are 2 fields where the case classification value is stored

  • systemCaseClassification

  • caseClassification (this value is seen in UI by the user)

On case save:

• if the Automatic CaseClassification featureConfiguration is true then

  • if the value of the case classification is Not_A_Case then:

    • no changes will be saved on either systemCaseClassification or caseClassification fields

  • if the value of the case classification is NOT Not_A_Case then:

    • automatic classification is executed

    • if the automatic case classification differs from existing systemCaseClassification

      • then the value is changed and also the caseClassification is changed which is seen in the UI by the user no matter what the user sets in the caseClassification field

    • if the automatic case classification returns the same value as the one already existing on the systemCaseClassificationase field then

      • the new value set by the user in the case classification field is the one that is saved

• so in case other changes made on the case trigger changes in case classification it does not matter what the user sets manually on the case classification field the system will always save the automatic classification value

• if the user is not satisfied with the automatic case classification value can go and change it manually but only of no other changes that would trigger changes in classification are made

Case clssification description for Luxembourg users:

• there are 2 fields where the case classification value is stored

  • systemCaseClassification

  • caseClassification (this value is seen in UI by the user)

On case save:

• if the Automatic CaseClassification featureConfiguration is true then

  • automatic classification is executed

  • if the automatic case classification differs from the existing systemCaseClassification value

    • then the value is changed and also the caseClassification is changed which is seen in the UI by the user no matter what the user sets in the caseClassification field

  • if the automatic case classification returns the same value as the one already existing on the systemCaseClassification field then

    • the new value set by the user in the case classification field is the one that is saved

  • so in case the other changes made on the case trigger changes in case classification, then it does not matter what the user sets manually on the case classification field, the system will always save the automatic classification value

  • if the user is not satisfied with the automatic case classification value, then can go and change it manually but only if no other changes that would trigger changes in classification are made. In this case the manual set will be saved.