Determines the person type according to the birth number (BN, input "rc") and company registration number (CRN, input "ico"). If only one of the properties "rc" or "ico" is specified, then a string corresponding to a natural person or legal person, respectively, is stored in the property "personType". If both properties "rc" and "ico" are present then the quality of the property values determines the resulting "personType" value:

• Both BN and CRN are valid - a string defined by the property "personTypeWhenBoth" is stored in the property "personType".
• Both BN and CRN are in the same quality class (see below) and not valid - null is stored in property "personType".
• BN and CRN are in different quality classes (see below) - a string corresponding to the property in the better class is stored in the property "personType".

If the "personType" property is specified, then the value is validated, (in case of a conflict between the computed and input person type the scoring flag "PT_CONFLICT" is set) but the "personType" property remains unchanged.

Note: Input quality is determined by membership in one of the following classes (listed from worst to best):

missing, bad format, bad CRC, valid.

Bad format means that both BN and CRN have an incorrect number of digits. Bad CRC means that the last digit is incorrect for a CRN or for a 10-digit BN.

Assume the configuration in which L denotes legal person type, N denotes natural person type, LN denotes that both BN and CRN are present and valid (therefore undecidable) and that the property "personType" is not present:

<step id='alg' className='cz.adastra.cif.tasks.v1.clean.UpdatePersonTypeByIcoRcAlgorithm'>
        <properties>
                <rc>text</rc>
                <ico>text2</ico>
                <personType>dummy</personType>
                <personTypeWhenNatural>natural person</personTypeWhenNatural>
                <personTypeWhenLegal>legal person</personTypeWhenLegal>
                <personTypeWhenBoth>legal person</personTypeWhenBoth>
                <scorer explanationColumn='explanation'>
                        <scoringEntries>
                                <scoringEntry key='PT_OK_UNDECIDABLE' score='100' explain='true' />
                                <scoringEntry key='PT_NOK_UNDECIDABLE' score='200' explain='true' />
                                <scoringEntry key='PT_NOK_DECIDABLE' score='400' explain='true' />
                                <scoringEntry key='PT_BOTH_NULL' score='800' explain='true' />
                                <scoringEntry key='PT_CONFLICT' score='1600' explain='true' />
                        </scoringEntries>
                </scorer>
        </properties>
</step>