Waring MBB520 Datasheet download pdf (Page 79)

Release Notes - New Features included in Release 2.4.0

Page 79 of 89

5. Customisation and Screen Changes

5.1 New Features at 2.4.0

Some parts of the TROPOS system may be customised, for example TROPOS screens and

scrolling displays. Many users will also write software and use utilities that interface to the

TROPOS product, for example SDK’s and Batch Load Update’s.

At previous releases, Customisation and Screen Change Information was supplied in a ‘report’

format with the Upgrade CD. At Release 2.4.0, the information will be presented via the SSI Web

Site. This will enable dynamic investigation of the changes that SSI has made to the TROPOS

product.

As the information will be on the Web Site, it will be available independently of the Release CD

itself. Thus, you will have more opportunity to determine the impact of the changes ahead of

receiving the release pack. This will be especially useful when planning your upgrade schedule.

Additionally, you will be able to run a report that will determine more detail of the impact of screen

(cct file) changes against your own system. See System Request 4359, Impact Analysis of ‘cct’

File Changes. Please note, this utility may only be available to you after you have installed the

2.4.0 Upgrade CD. On receipt of future releases, the impact assessment can be performed before

the release has been installed.

You will be informed of what steps to take during the upgrade, and how and when you can

interrogate the information.

5.1.1 cct Enhancements

5.1.1.1 Customised cct files (SR4198)

Changes have been made to ease the task of global customisation of cct files to reflect changed data

dictionary labels.

This covers a new utility – labupd that may be used to extract all dataname labels to a sequential

text file. This text file may then be changed using a standard editor to change the required dataname

labels. Once changed the program may be rerun to update these new values to the database.

WARNING – These changed values may be overwritten by the next software release, so the

changes made may need to be reapplied.

The cct files then need to be regenerated. paa020_mt has been changed to give an option to

produce customised versions of cct files – where they are different to the existing values. This

option will only be invoked on a production database (variable SSISYSDEVELOPMENT not set),

and the files will be created based on the previous version rather than directly from the standard

template. This will increment the global customised version number.

These files will be created in the default directory, and once checked should be moved to the

CCT_CUST directory.

Following a software release, any cct files changed will need to either have the changes reflected

into these customised versions, or the previous version deleted and re-created as above.

1 2 ... 74 75 76 77 78 79 80 81 82 83 84 ... 88 89

No comments

Waring MBB520 Datasheet Page 79