Datasheet

Release Notes - New Features included in Release 2.4.0
Page 61 of 89
>FOOTER
Warning – note the looping-risks which would be involved in triggering database access on $sd
(i.e. a new DETAIL section) and storing the data in a ‘nd$’ field, which will then trigger a new
DETAIL ... etc.
4.3.1.4 TROPOS Form Error Handling (SR3476)
It is now possible to specify whether syntax errors in TROPOS Form format files should result in
system errors or simply display error details.
The wppxxxx.out formatting files which are used by TROPOS Form to generate print files, e-mail
files (etc) are, in effect, small interpreted programs. It is expected that these files will be customised
to create different document formats as required. In this process, it is possible that syntax errors are
introduced by typing errors etc. Such errors have previously been displayed by TROPOS Form – to
the event log if it was running in the TROPOS environment – and it has continued processing as
much as possible. This could result in expected documents not being produced or produced in the
wrong format, with no explanation except on the event log.
TROPOS Form has been amended to optionally generate a system error in the event of such a
syntax error or other processing error in a wppxxxx.out file, in order to create a visible notification
of the problem. In this event, the event log should be checked, and the reported errors in the
wppxxxx.out file should be corrected.
By default, syntax errors now generate system errors. This may be adjusted to allow minor or all
errors to simply be reported instead.
A default error level for all documents may be set by including one of the following lines in a
customised generic wppdefhdr file preferably in the binsite directory to retain its contents across
TROPOS releases:
error=none simply displays details of errors
error=display displays minor errors and generates system errors for major errors
error=syserr generates system errors for all errors (the default setting).
Different error levels may be applied per document by including one of these lines in the document-
specific wppxxxx.out file, in the ‘CONTROL’ section, below the line which reads and processes the
contents of wppdefhdr.
Manual Set-Up Procedures
This change can produce system errors within wpp processing which previously appeared to run
successfully. Although no error was reported to the user, errors were displayed on the operint log
file that prevented the document being successfully processed. It is thus necessary to check all wpp
printing functions on the handover database prior to making the new software live. This change was
actually introduced at release 2.3.0; but these details were omitted from the release notes.