| DESCRIPTION OF ENHANCEMENTS |
Changes were made to 10 Document Definition routines fixing minor errors
2. If user entered a name like AGE (which happens to be the abbreviation
of an object) as a new Document Definition, say, under option Sort
Document Definitions, it was not accepted. This was to prevent entering
ambiguous objects, but was too restrictive since the user may plan to make
AGE say, a Title, in which case it doesn't create an ambiguous object. AGE
is now accepted except under option Create Objects.
3. If user entered Document Definition using Fileman with name like DOB
(which happens to be the abbreviation of an object) and no other fields,
and closing a small loophole which permitted users to edit objects and
user could edit it under Basics from the Sort option, and give it type
Object. This creates an ambiguous object (if DOB is in boilerplate text,
code doesn't know whether to use original object PATIENT DATE OF BIRTH, or
new object DOB). User can no longer edit type of DOB to object.
4. When using hidden action Print List (PL), neither P-MESSAGE nor
BROWSER worked as a device. They work now.
possibly make them ambiguous.
Problems fixed:
1. Messages "Deleted" and "NOT Deleted" wrapped when user deleted entry
from Document Definition file. Messages are now written on following
line.
|