New Feature

Access to Additional Item Fields for Label Printing

(CRD 303056 / FSD 303056)

New Feature

Access to the Unit Size and Unit Size Desc fields in Receiving

(CRD 303099 / FSD 303099)

New Feature

Automation Support for Importing Specific Files with General Import

(CRD 303218 / FSD 303218)

New Feature

Changing the Default Unit in Inventory Management Applications

(CRD 303229 / FSD 303229)

New Feature

Reprinting a Store Transfer Ticket

(CRD 337456 / FSD 337456)

New Feature

Filtering Expired and Applied Batches in the Batch Manager

(CRD 356273 / FSD 356273)

New Feature

5 Digit Item Number Entry in Screen Item Maintenance

(ER RBO09191203W / CRD 356279/ FSD 356279)

New Feature

Access to Item Last Received Date and Quantity

(ER RBO02061301W / CRD 356284/ FSD 356284)

New Feature

Handheld Access to Item Movement and Next Cost Information

(CRD 356285/ FSD 356285)

New Feature

Querying and Reporting on Items Counted or not Counted in Stock Count

(CRD 401364/ FSD 401364)

New Feature

Importing Suppliers using General Import

(CRD 410416/ FSD 410416)

New Feature

Centralized Batch Logging

(CRD 440073/ FSD 440073)

New Feature

Top (x) Reports

(CRD 440166 / FSD 440166)

WD 303041

WD 303049

A user-defined sort in the Batch Manager application is not maintained.

Scenario:

1. Double-click on one of the header field names in the Permanent or Temporary view to change the order in which batches are listed. 

2. Perform an action in the Batch Manager such as:

- staging, releasing, or deleting a batch

- running a full stage

- moving columns in the view

- adding, removing, or moving columns using the Column Settings window

Expected Results: The current sort order is maintained.

Actual Results: The sort order reverts back to the default: by Status and Batch Number.

WD 303095

Some reoccurring BackOffice tasks are not getting scheduled for the next run datetime when they run

Scenario1:

1. Schedule a re-occurring daily task.

2. An interruption occurs that affects the service from being able to access/run the .cs file at the scheduled time.

Actual Results: The .cs_log indicates that the task failed and the task is not automatically rescheduled to run the next day at the same time. It will not run again without being rescheduled.

Expected Results: The .cs_log and syslog indicate that the task failed and the task is automatically rescheduled to run the next day at the same time.

Scenario2:
1. An interruption occurs that affects access to the Common database while the Retalix Control Strings service is running.

Actual Results: The Control Strings service appears to continue to run as displayed in the Services window but it is stuck in a non-functional state trying to re-connect to the Common database.

Expected Results: The Control Strings service recognizes that there is an issue and tries to re-connect to the Common database.  It continues to try until a connection is re-established and then it re-schedules any reoccurring tasks that were missed while the connectivity was unavailable.

WD 303097

Reoccurring BackOffice tasks that are scheduled to run hourly fail when the clock is moved forward one hour for Daylight Savings.

Scenario:

1. Schedule a re-occurring hourly task to run within the next 59 minutes.

2. Move the clock forward 1 hour (beyond the scheduled task time).

Actual Results: The task does NOT run and is not rescheduled to run. It will not run again without being rescheduled.

Expected Results: The task is automatically rescheduled to run the next hour when the system detects that the scheduled time has been missed (effectively skipped over).

WD 303115

The Price Start and End Date fields are incorrect when generating labels for a batch in Item Maintenance and from the Release Manager.

Scenario:
1. In Parameter Maintenance, choose the Label Printing option: Output Label Info to a Text File and save the changes.

2. Create a Temporary Batch in Screen Item Maintenance.

3. Enter a Sale price for an item.
3. Choose 'Export Tags'.

Expected Results: The exported begin_date and end_date fields in the export file match the batch start and end dates respectively.

Actual Results: The exported begin_date contains the item's last price change date and the exported end_date is blank.

WD 398198

RBO Setup should not list ACS as an install option since it is no longer supported.

Scenario:
1. Run setup for a new RBO Server install.

Expected Results: The options to choose ACS or ACS-IR are not listed in the POS selection window.

Actual Results: The options to choose ACS or ACS-IR are listed in the POS selection window.

WD 400141

The RBO setup program launches each time a different Windows user logs into the system after an update.  This occurs on Windows7 and 2008 Server.

Scenario:
1. Set up a Windows user that is in the Administrators Group on a system running Windows 7 or 2008 Server.

2. Verify that the default RBO services are running (Retalix Service Monitor, Retalix Message Router, etc.).

3. Run the RBO setup.exe logged in as the Administrator user.
4. Choose 'Yes' to reboot the system when prompted by the setup program which is required before the Update can proceed.
5. After the reboot, perform the required steps to complete the Update and then reboot the system when prompted.

6. Log onto the system as the user created in step 1.

Expected Results: The setup program does not restart for this user since it was already completed by the Administrator.

Actual Results: The setup program restarts for this user indicating that it is going to 'Reinstall' RBO.

WD 400385

The RBO setup should fail with a recognizable error when trying to do an installation with a "Named Instance" of SQL Express 2008 and no "Default Instance".

Scenario:
1. Install SQL Express 2008 R2 using the installer: SQLEXPRWT_X86_ENU (which is Express with Tools) but choose 'Named Instance' instead of 'Default Instance', and enter 'SQLExpress' for its name.
2. Install RBO Server.

Expected Results: The installation should fail quickly (since the RBO and Common databases cannot be built) and with an error message indicating that there was an issue connecting to SQL Server and to refer to the install log for details.

Actual Results: The installation takes a long time because of SQL Server login timeout and eventually fails with the following errors returned: QueryService returned a status of -2, Setup failed to create the Common Database'.  

WD 412323

Cannot Update RBO to 4.08.02-050 because of the error: 'Setup is unable to locate the Retalix BackOffice database.  The database must exist in order to perform an update'.

Scenario:
1. Update RBO to 4.08.02-050 on a system where the RBO database is stored in another location other than the default: \Retalix\BackOffice\InStore\Database.

Expected Results: The Update should be successful.

Actual Results: The Update stops almost immediately with the error: 'Setup is unable to locate the Retalix BackOffice database.   The database must exist in order to perform an update'.

WD 412500

Item File Sync can cause a temporary price to overwrite the Regular price if an item is on sale in RBO and not on file on the POS.  This occurred inadvertently during a V8/RBO upgrade to a new server.

Scenario:
1. Create 1 or more current temporary batches with items that are on the low end of the item number range (i.e. 1 - 100) because they are deleted first during a slow 'Send to POS'.

2. Stage and Release the temporary batches.

3. On V8, add the hidden system parameter with Key Name = 'Host', Value Name = 'OverridePLUBatch', and Value Setting = 'Y' to enable the slow Item File Send functionality which first deletes the Item File on the POS.

4. Start an Item File Send but exit the application while it is deleting the Item File from the POS after it has deleted some items.  NOTE: After killing the application, you can check the progress of the delete in sql using select * from PLU order by ITM_ID.

5. Run an Item File Sync.

6. Review the Item File Sync batch.

Expected Results: The items in the Item File Sync batch don't contain any current information for the items that are on sale.  If this batch is applied, the Regular and Current price for the sale items will not change in RBO and the Current Price will be sent to the POS.

Actual Results: The Sync batch contains the Dept Number Description, and the Current Price for the items that are on sale.  If this batch is applied, the Current/sale Price will become permanent in RBO because the Sync batch is a Permanent batch.

WD 412711

The Storeline/V8 Communications Uninstall does not remove the 'BackOffice$' share.  So, if it is being reinstalled to a new location, the new 'BackOffice$' share does not get created.

Scenario:
1. Install RBO on the D drive under D:\Retalix.

2. Install POS Communications accidently on the C drive under C:\Retalix.

3. Uninstall POS Communications.

4. Install POS Communications on the D drive under D:\Retalix.

Expected Results: The BackOffice$ share is assigned to: D:\Retalix\BackOffice\BackOffice (right click on Properties - Sharing - Advanced Sharing).

Actual Results: The BackOffice$ share does not get assigned to D:\Retalix\BackOffice\BackOffice.

WD 412907

Getting the error: 'PROGRAM MOVED OR SITEKEY BAD PASSWORD' occasionally after a reboot on Windows7 and 2008 systems which prevents access to RBO applications.  It occurs on systems with multiple internal SATA drives.

Scenario:
1. Reboot an RBO Server that has more than 1 internal SATA drive.
 

Expected Results: RBO applications can be opened as expected.
 

Actual Results: Sometimes, you receive the error: 'PROGRAM MOVED OR SITEKEY BAD PASSWORD' which prevents access to RBO applications and requires one or more reboots and in some cases, a system re-license to correct.

WD 413505

The values in an Item File Sync batch should not overwrite the values applied at the same time as another current Permanent batch.

Scenario:
1. Create a permanent batch with one or more price changes for items that don't currently have any temporary pricing in effect.
2. Change the price of those items on the POS so that they are different than the values in the Permanent batch and are out-of-sync with the values in RBO.
3. Run an Item File Sync.
4. Turn off the Ignore Flag on the Sync batch.
5. Stage and Release both batches.

6. Query the same items in RBO.

Expected Results: The prices from the Permanent Batch created in step 1 have become the new permanent prices.

 
Actual Results: The prices do not appear to have changed.  They match the values in the Sync batch.

WD 413531

The Supplier List report doesn't support the export of all the main supplier, contact, delivery, and accounting fields and is not schedulable.

Scenario:
1. Open the Supplier List Report and choose View - Export Options from the menu.

2. Choose 'Export Columns' in the New Report window

Expected Results: All of the main supplier, contact, delivery, and accounting fields in the report are in the Selected Columns list.

Actual Results: The fields: City, State, Supplier Description, Supplier ID, and Zip Code are not included by default in the Selected Columns list and many of the main supplier, contact, delivery, and accounting fields in the report are not available for export.

WD 418117

The horizontal scrollbar in the Item Maintenance Grid View is not in full view on Windows 7 systems. 

This is also an issue in the: Bill Back, Stock Count, Supplier, Inventory Management, Store List, and Department Maintenance applications.

Scenario:
1. Open Item Maintenance in Grid View.
2. Choose Edit Column Setting to select or build a view that contains enough fields that will force the horizontal scrollbar to be displayed.

Expected Results: The horizontal scrollbar is in full view at the bottom of the screen.

Actual Results: The horizontal scrollbar is cut-off at the bottom of the screen so that only half of its width is displayed.

WD 421943

A 'Set to Regular' batch is getting created unexpectedly sometimes when an item has already returned to its "regular' state.  This is misleading.

Scenario:
1. Create a Permanent batch with Start Date = today.

2. Change item 1, save, and close the batch.

3. Stage the Permanent batch but don't release it.

4. Delete the Permanent batch (i.e. mark it and permanently delete it).

5. Create a Temporary batch with Start Date and End Date = today.

6. Change item 1 and save.

7. Change item 2, save, and close the batch.

8. Run Full Stage.

9. Release the Temporary batch.

10. Move the system date forward.

11. Run Full Stage.

12. Release the 'Return to Regular' items.

13. Run Full Stage.

Expected Results: A 'Set to Regular' is not created that includes item 1 because the 'Return to Regular' that included it was previously just released.

Actual Results: A 'Set to Regular' is created which includes item 1 even though the 'Return to Regular' that included item 1 was previously released. Further, a 'Set to Regular' will be unexpectedly created again if the same item is introduced in another temporary batch and the same sequence of steps (5-13 above) occur before the item appears in a Permanent batch that is staged and released.

WD 426134

Could not pull V8 movement to RBO with POS Communications installed in a different root directory than RBO in 4.8.2. 

Scenario:
1. Install RBO on the D drive under: D:\Retalix.
2. Install POS Communications on the C drive under C:\Retalix.
3. Ring up some items on the POS and run an EOD.
4. Choose Pull POS Movement in RBO Item Utilities.

Expected Results: The movement should pull successfully into RBO.

Actual Results: A file not found message is received and no movement is pulled.

WD 428955

The frequent shopper fields (fs_per_amt and fs_pm_qty) are not supported by the label_info_storeline table.

Scenario:
1. In Parameter Maintenance, choose the Label Printing option: Output Label Info to Database Table and save the changes.

2. Query an item in Item Maintenance.
3. Choose 'Export Tags'.

Expected Results: There are fields in the label_info_storeline table that are populated with the Freq Shopper - PM and Price (x for y) from the item record.

Actual Results: The label_info_storeline table does not have the Freq Shopper - PM and Price (x for y) fields but all of the other Freq shopper fields are present in this table.

WD 432517

Batch Logging is not logging a 'Deleting Batch' action if the batch contains special characters in the description.

Scenario:
1. Create a batch that contains any of the following characters in the Description: &, >, <, ^, |.
2. Delete the batch in Batch Manager.

Expected Results: The batch log contains a 'Deleted Batch' entry which specifies the batch being deleted including its Description.

Actual Results: The batch log does NOT contain a 'Deleted Batch' entry which specifies the batch being deleted including its Description.  So, there is no indication that the batch has been deleted.

WD 432518

Batch Logging is not logging when a batch is 'Marked' or 'Unmarked' for deletion.

Scenario:
1. Select one or more batches in Batch Manager.
2. Click on the 'Delete' button and OK if prompted in the Confirmation dialog.

Expected Results: The batch log contains an entry indicating that the batch is 'Marked' for deletion which includes all of the fields recorded for other batch actions.

Actual Results: The batch log does NOT contain an entry that the batch is 'Marked' for deletion.  This is needed for tracing which user marked it for deletion.

WD 433796

The Pkg UOM Code, Pkg UOM Desc, and Batch Start Date (or Price Start Date) fields are not in the label_info_storeline table.

Scenario:
1. In Parameter Maintenance, choose the Label Printing option: Output Label Info to Database Table and save the changes.

2. Query an item in Item Maintenance.
3. Choose 'Export Tags'.

Expected Results: There are fields in the label_info_storeline table that are populated with the Pkg UOM Code, Pkg UOM Desc, and Batch Start Date (or Price Start Date) from the item record. These fields are documented in the label extract document: Label Tag Export Format.PDF located in the \Retalix\BackOffice\Documents\Label Extract directory.

 
Actual Results: The label_info_storeline table does not have the Pkg UOM Code, Pkg UOM Desc, and Batch Start Date (or Price Start Date) fields.

WD 434667

The cursor is intermittently moving to a new row in the Item Maintenance Grid when a key is pressed to enter a value into the last editable field in a row.

Scenario:
1. Enter a value into the Price field which is the last editable field in a custom Item Maintenance grid.

Expected Results: The value can be entered into the Price field.

Actual Results: Intermittently, when the key for the 1st digit of the Price is pressed, a new Grid row is inserted and the cursor jumps to the Item Number field of that new row instead of accepting entry into the Price field.

WD 435550

The Retalix Control Strings service sometimes holds a lock on the .cs file which prevents the associated BackOffice task from running in the future.  The file lock is not released when either of the following conditions occur:

-       There is a communications issue with the Retalix StoreLine Repository service when a task is started.

-       There is a communications issue with the Retalix Remote Agent service while the task is running.

 
Scenario 1:
1. Stop the Retalix StoreLine Repository service to cause a communications issue with this service when a task runs.

2. Schedule an export task to run in two minutes.

Expected Results: The task runs successfully.

Actual Results: The task starts to execute as noted in the cslog but the item.exe and CsSessionMgr.exe processes are left running and never close, and the associated .cs file is left locked so if another attempt is made to run the task after the POS Repository Service is available, it will fail. The Retalix Control Strings service must be restarted in order to retry running the task.

Scenario 2:

1. Schedule an export task to run in two minutes.

2. Stop the Retalix Remote Agent service after the task starts to cause a communications issue between the task and this service.

Expected Results: The task runs successfully.

Actual Results: The task starts to execute but does not complete and the associated .cs file is left locked. So if another attempt is made to run the task after the Retalix Remote Agent service is available, it will fail. The Retalix Control Strings service must be restarted in order to retry running the task.

WD 435556

Scrolling in the BackOffice Task Scheduling window sometimes doesn't refresh properly and shows a blank area where a task should be displayed.

Scenario:
1. Use the down-arrow of the scrollbar to scroll to the last task in the BackOffice Scheduling window.

Expected Results: All of the tasks at the bottom of the list are visible.

Actual Results: There is a blank area at the bottom of the list where tasks should be displayed.  If you click on the blank area, it will make one of the tasks that are currently hidden from view, visible.