Codification validation

Authorization field definitions (=rows) in the codification need to be validated before the authorization lookup engine will take them into account.
The validation also does some constraint and consistency checks.

Note: The status of an existing codification row (field definition) is only placed invalidated when you modify field, module or the indicator restrictions in the codification sheet.

Validate codification

Codification > Mass changes > Validate

The available options that you can choose when validating a codification workbook are as follows:

• Do fast codification validation: this option only checks not validated rows.
• Simulate codification validation: this option will keep invalidated rows as invalidated.

Press the "Validate" button to start validation.

Validation checks

The validation will validate the rows to certain rules:

• Checking main sheet rows
  This checks if the rows in the buffer table are equal with the already defined rows. Moreover missing records and removed records in a buffer table are checked too.
• Checking sub sheet rows
  This checks if the rows in the buffer table (sub sheets) have a link from another sheet and if all links have the representing rows on the sub sheet.
• Checking for invalid values
  This checks if the values in the cells for domains or for fields are valid values.
• Checking invalid link values
  This checks if a link in a sheet to a sub sheet is valid.
• Checking floating values

Look for values that are listed as link values, but have no link with a domain, field, workbook combination.


• Checking field groupings
  This checks if a group field has at least two field definitions and that these come from the same module and have the same object. Moreover all divided domains must exist for the selected field definitions. (See "Field Groups")
• Checking indicator restrictions
  This checks the length of an indicator is correct and if there are any unused indicators. (See "Naming convention")
• Validating rows
  This checks a list of restrictions:
  • The field is an organizational level and object is an asterisk “*” .
  • The field and the object combination is unique in a module.
  • If you placed restrictions on one of the role name indicators, we suggest that you don't place restrictions with wildcards or question marks in other role name indicators.

   

Note:
In some cases if the row encountered an error with a certain rule your can manually validate the row.
The validation does not take into account all possible combinations and therefor sometimes relies on the end user to validate a row.

Example:
After validating the codification there is an indication of two authorization field definitions that are not validated.
If you check the codification you'll see that there is a restriction difference in the role name indicator restriction "Action".
So you know that it is going to be a unique hit in the authorization lookup, you can manually validate these rows by either clicking the "Validate" button for each row or clicking the "Validate all" button.

Validation overview

You can have a view of all rows in all codifications that are validated (or not) and by whom.

Codification > Views > Validations

Note:
You can only invalidate rows here, validating rows is always done through the validation engine.

This document is up to date with version 11.1.10.20 of CSI Accelerator