Enhancement or Fault Number

Item  Description

New Feature

Add support for ULinkPlus Extract.

(ER RBO01011001 / CRD 303226 / FSD 303226)

New Feature

SIL needs to allow a datatype to be declared and used as a NUMBER in a SIL file that is defined in the SIL dictionary as a CHAR.

(CRD 303231 / FSD 303231)

New Feature

Need Host system parameter to allow host defined values in SIL header Fields: H14 and H15.

(CRD 303232 / FSD 303232)

New Feature

Need SIL Host parameter to allow Order Codes to be trimmed of spaces and left-zero filled.

(CRD 303233 / FSD 303233)

New Feature

Add support to RBO SIL for the PRICE_DCT table.

(CRD 306628 / FSD 306628)

New Feature

Add support for the RBO FM emulator running on a Falcon X3 with Window Embedded CE 6.0.

(CRD 306629 / FSD 306629)

New Feature

Need to move the SIL Batch Export parameters to a new tab so that there is enough room on the Host tab for new SIL parameters.

(CRD 309362 / FSD 309362)

WD 303086

Batch Mgr Auto Delete does not always work correctly on temporary batches in release 4.5.2 and 4.5.3.

There are 2 issues - first, Batch Mgr does not show Auto Delete checked for Temporary Maintenance, even if the option is checked in the Batch Dialog box when the batch is created. As a result the customer does not know if the batch is set to be purged by the system. The Auto Delete option may be manually checked through Batch Mgr, but when saved appears to go back to unchecked. However, the value in the database is often being changed.
The second issue has to do with attempting to change Auto Delete on a temporary batch through Batch Mgr. Sometimes when changing the auto delete option through Batch Mgr on a single batch, the keep_flag column in batch_mnt_dir will change to Y for all other temporary batches. This appears to affect all temporary batches including SIL batches and is resulting in temporary batches not being automatically purged from the system.
When a batch is created Auto Delete is by default checked in the Batch Dialog window. The option can be unchecked at that time (is not controlled by a parameter) and the keep flag in batch_mnt_dir will contain the correct corresponding value - Auto Delete checked is Keep Flag = N / Auto Delete unchecked is Keep Flag = Y. The problem occurs when Auto Delete is clicked through Batch Mgr. A customer may assume none of the temporary batches are set for Auto Delete, as the column is not checked and in Permanent Maintenance some or all of the batches may have Auto Delete checked. If a batch is created with Auto Delete turned off (unchecked) - keep flag in the db is set to Y - and Auto Delete is turned on (checked/saved) through Batch Mgr, the keep flag will become N in the db, but the keep flag value will become Y for all other temporary batches. If Auto Delete is checked in Batch Mgr on multiple batches and then a single "save" is done, those batches will have keep flag set to N and the remainder of the batches on the system will be Y.

WD 303179

Purge function (clock icon) within batch manager doesn't remove temporary batches in question.

WD 303216

Fast PLU maintenance batches created by RBO will not import into V8 when running SQL 2008.

WD 303225

Surface parameters on Host Extract tab.

Need to update Parameter Maintenance - Host Extract tab to include the new parameter: Ulink Extract Path and the existing parameter: Cost Extract Path that is currently a hidden parameter.

The Cost Extract Path is used for the location of the output file generated during the movement process when the parameter: Generate Daily Cost Extract is set. We need to update the documentation and Help for this since the current Help says that the file always goes to the Outbox.

WD 303230

SIL should not always reject the maintenance in an Insert when a Key field that is listed in the header contains a null value in the Insert statement.

SIL should error if the the whole Primary key is NULL (i.e. ALL of the fields that make up the key are NULL) or if a field that it requires to be in the key is NULL as described in the RBO SIL Programmer's Guide. Currently, RBO SIL is checking the individual fields that make up the Primary key and if any are NULL, an error is thrown without consideration as to whether it is supported or important to RBO. This is too strict. There is no evidence in the SIL Spec that nulls are not permitted in the individual fields that make up part of what it defines as the Primary Key of a SIL table. Removing this restriction will make RBO's handling of SIL keys more consistent with ISS45 and ScanMaster SIL.

WD 314538

An MU should be prevented from being applied to an earlier major release of RBO.