just a few browser dialog boxes to change over to K now.
Since you're in the process of tinkering with Aware message dialogs, you should also consider refining them to be really slick, by changing the source of the text string used in the message text for the attribute which has not been completed, etc.
So, instead of the message popup saying:
"Value of descriptionA must be provided" (where 'descriptionA' is the Attribute Name, it would instead use the Attribute Label as defined in the Presentation dialog, and so this message might instead say:
"Value of Primary Description must be provided" (where 'Primary Description' is the Attribute Label defined for the Attribute. If the Attribute Label is blank, then perhaps it would default back to using the Attribute Name.
This way the user would be able to more easily correlate the message in the popup dialog with the field on the form to which it pertains.
Additionally, spaces cannot be used in the Attribute Name (but can be in the Label), and so it is not possible to structure a well presented Attribute Name such that it 'flows' in the message string.
Additionally, having database table field names used in message boxes all throughout an application isn't really the norm.