Umbrella Issue Validation

Umbrella case for all issues related to mandatory fields.

TODO Create case for following issues:

1) mandatory at document template level is the same as at document level. This causes problems. For example the password field requires mandatory data (which is a bug in itself). Using the password field in the template editor requires you to specify a default value.

2) jcr:data field is mandatory so the prototype must contain a (dummy) binary.

3) uniqueness on folder / document names within a single folder.

4) when you use x to close the tab, a popup appears asking to save changes. If you click yes, make sure that the constraints are checked and any error message is displayed.

5) it should be possible to have for example a date field with an (initial) null value and mark it as mandatory

6) fix the 'disabled' look of the required/mandatory attribute in the template editor

7) improve the visual feedback which fields are mandatory and improve the error message feedback, e.g. location of the error msg near the offending field
8) optional compound types with mandatory fields should be optional for the document