Datasheet

Release Notes - New Features included in Release 2.4.0
Page 71 of 89
This transaction deals with the whole text entry; first extracting all the text; allowing change to the
text; and then replacing or adding all text. The text is maintained in an editable 'scrolling' region.
TECH performs no validation on the contents or format of the text, so any visible character may be
used.
At this release, this transaction is only available on the TROPOS Browser Interface and SDK
applications.
Use of this transaction is interchangeable with the existing transactions; although, due to changed
validation rules, maintenance of a specific text entry should be restricted to one method, to prevent
un-necessary validation errors when returning to the TEDY transaction set.
Manual Set-Up Procedures
Those SDKs which require to use this new functionality need to be upgraded.
There is no change to the contents or format of the MAA040 text table at this release. It is
anticipated that this table will be replaced at the next TROPOS release (2.5.0), so direct access of
this table should be removed from all SDKs prior to this next release.
4.3.5.8 MAA170 log file (SR4180)
The MAA170 log file has been moved into the database, and is now the MAA170 table. The design
of this is such that the Background Queue information (MAA130) and the Alternative log file
(MAA420) details are also held on this table. This table will also contain rows required for
incoming events and outgoing events required to support the TROPOS Active processing.
The following software has been changed to support this change:
DATA transaction group
This will now handle a maximum column size of 4000 characters.
Background queue
In addition to the existing background and tonight queues, there is now a ‘low priority’ queue.
Transactions from this queue will be processed by a background process whenever there are no
suitable background queue records outstanding. The same transaction dependancy will be applied to
these transactions.
QUEU transaction
This has some extra functionality, allowing all records on the MAA170 table to be processed. This
is by means of a record type field, and also by a transaction code field. In addition, a 2nd date / time
field is present which will allow for records to be selected for a specific time period.
As before, unless using the QUEM transaction, it is only possible to see data that you have inserted.
Logqueue subroutine
This will allow insertion of the new ‘low priority’ queue records. This is by specifying a log type 6
record.
Logrename utility