Chain Web 2.10.80-2.10.0

Chain Web v. 2.10.80

Released 3rd of September 2021

Report for showing bonus points

In order to report on bonus points we have created Bonus per store report. This report allows the user to see monthly bonus usage per store for last 12 months.

Report details Bonus per store
File name	0950_BonusPerStorePerEndOfMonth
Data source	Reporting Data Warehouse
*Selections*	*Comment*
Retail store	Default none, multiselection possible
*Columns* - Report is grouped per store, showing one row per month.
EndOfMonth	End of month
Earned bonus	Earned bonus
Used bonus points	Used bonus points
Balance	Balance
Expired bonus points	Expired bonus points

Automatic logoff in Chain Web

(RTC-15046)

Automatic logoff is defined by system parameters:

AutoLogoutWhenIdle - possible values True/False, defines if automatic logoff is enabled/disabled, default value False;
AutoLogoutWhenIdleTimeoutMinutes - defines (in minutes) after how long the user is logged out automatically , default value 30.

When the AutoLogoutWhenIdle=True and AutoLogoutWhenIdleTimeoutMinutes <=10, then the notification that user will be logged out soon is displayed when half of AutoLogoutWhenIdleTimeoutMinutes will pass, when user is idle.

When the AutoLogoutWhenIdle=True and AutoLogoutWhenIdleTimeoutMinutes >10, then the notification that user will be logged out soon is displayed when 5 minutes are remaining to the automatic logoff, when user is idle.

When the user is active in at least one tab, then the user will stay logged in all opened tabs.

Search for bank card number in receipt journal

(RTC-15074)

Searching for receipts paid with given bank card numbers:

1) Some payment providers save card number as ************0690 MASTERCARD. The user should then search for only 0690, or even better 0690 MASTERCARD to find the receipt.

NB! Due to technical searching limitations (in SQL Server) it is not possible to search with '' as this is removed from searching index. If the user pastes the whole card number *****0690 we remove ******* and use 'starts with' 0690 in the search.

2) Some payment providers save card number as xxxxxxxxxxxxxx6409-05. The user should then search with xxxxxxxxxxxxxx6409 (the whole string before '-'), with all the 'x' characters. If the users adds to few x, for example with xxx6409-05, the receipt will not be found.

NB! The the search technology saves the whole card number including 'x' as this is interpreted as a word, and the search uses 'starts with' to find the searching words in the index. The character '-' is removed, and also leading zeros are removed, so the user cannot in above example search for 6409-05, only for 6409.

Improvements


Balance	Balance summary (RTC-9741) After registering all balances for selected day, user will see a summary for all cashiers. This summary is available from Financials menu section called Balances summary.
Customer	Maximum credit limit when updating customers through ARTS Customer import (RTC-15225) The default credit limit on credit customers in Chain Web is set in the system parameter DefaultCustomerCreditLimit. When updating or creating customers through ARTSCustomerImport the maximum credit limit must be less than three times the DefaultCustomerLimit or the update will be rejected. If the system parameter is blank, the default value of 50 000,- is used and the maximum credit limit when updating is 99 999,-. Import of customer with invalid mobile number (RTC-9100) If customer's phone/mobile number is invalid (contains illegal characters) then customer is exported with empty phone number. *Requirement:* BackOffice batch generator 1.5.3
Customer order	Search for offers (RTC-14959) In Offers' view there is a simple search option. User can narrow and customize results by entering key word in the simple search window. Search for orders in Package deliveries (RTC-14960) In Package Deliveries view there is a simple search option. User can narrow and customize results by entering key word in the simple search window. Fix for refund (RTC-7054) The refunded lines are properly displayed in the Refund summary/ Credit Note.
Invoices	Search for invoices (RTC-13704) In Invoices' view there is a simple search option. User can narrow and customize results by entering key word in the simple search window (the search result is improved in this version).
Receipt journal	POS unit filtering (RTC-9114) Fixed a problem where POS unit filter field were not removed as it should. Fix for timeout when searching in large receipt journals (RTC-15143) After entering Receipts Journal view receipts are properly displayed and no timeouts occur. User is able to customize and narrow the shown results by using filters. Filter for stock adjustment transactions (RTP-13122) In receipt journal the user can filter displayed results only to stock adjustment type of receipt. This type is in group of types named item transactions, so if user filters on all item transactions, receipts for stock adjustments are also shown. Open drawer transactions (RTP-11413) Open drawer transactions are displayed under System transactions and Other. Search for old receipts (RTC-7875) When searching for old receipts it is not possible to use all the standard filters. When 'date from' is older than defined in system parameter R_ceiptJournalOldReceiptsDate,_ a simplified filter is displayed. Please note that this system parameter is default blank.
Reports	Store users of report 0010 (RTC-14884) If user has store level access, report 0010 shows only results for the user's store. New reports, with interactive sorting (RTC-14253) We have made to new reports (0455, 0456). They are the same as 0110 and 0453, but now they have interactive sorting in all columns. Changes in report 0450_StoreSettlementPerOperator (RTC-14255) New row "Klarna" in 1701_subCurrency section. The row shows payments done with Klarna. New hidden parameter pKlarna - needs to be set to Klarna payment card number. Changes in report 0750_WetStock (RTC-14762) Now the report fits on A4 format when exported to PDF. Font was changed from 10pt -> 8pt. Width and Hight of cells were changed. Following column names was reorganized and changed: Water measure in tank -> Water Daily Variance, Daily Variance% -> Daily on two cells merged above and below: Variance and Variance% 5 Days Cumulative Variance,5 Days Cumulative Variance%,5 Days Cumulative Sales -> 5 Days Cumulative on three cells merged above and below: Variance, Variance% and Sales 31 Days Cumulative Variance,31 Days Cumulative Variance%,31 Days Cumulative Sales -> 31 Days Cumulative on three cells merged above and below: Variance, Variance% and Sales
Stocktaking	Minor improvements in user interface (RTC-14104) Sticky columns have been added in Overview tab and No active stocktaking header has been made more visible. Counted by column in Overview and Count Lists tabs has been upgraded. The change for Counted By is done in POSLogProcessingWorker. New Count Lists from POSLogs have userId set to "operatorId - operatorName", for old records the value isn't changed. Cleanup of old count groups (RTC-13902) There is a job named CountingGroupsCleanupJob which cleans old count groups for an inventory control. User is able to set number of days after which the count group should be removed. Default values is 90 days. If count group was used in already archived stocktaking and is old enough, CountingGroupsCleanupJob deletes it. Cleanup of old counting groups (http://RTC-15659) Delete Counting Groups and dependencies will be done in batches. Batch size is configurable by 'Delete batch size' job parameter. Default value is 50, but it could be increased to 1000. Exclude items with specific assortment codes when creating stocktaking (RTC-11066) System parameter AssortmentCodesToExcludeInStocktaking defines list of assortment codes, that will be excluded from the stocktaking basis. Created date in the count groups view (RTC-15733) Bugfix: All dates in the count groups' grid are displayed properly. Filter on supplier and brand when creating count groups (RTC-12666) User is able to select "Supplier" and "Brand" as an attribute in item filter when creating or editing count group.
User Management	Cashier permissions through cashier roles with system roles (RTC-12125) A predefined set of system roles for cashiers can be added to a cashier role (not directly to the cashier/user). When creating a new cashier or editing an existing one, System Roles are not displayed in dropwdown list. If user has a system role granted from previously, it is displayed only in Cashier roles window. After removing it, user isn't able to add System Role to the cashier again.

Chain Web v. 2.10.70

New Report based on EOD

(RTC-14247)

New report showing sales per item group where period is based on EOD (End of day). Made based on report 0600.

Report details Sales per item
Filename	0609_SalesPerArticleWithBreakage
Data Source	Lindbak POS Reporting DW and Lindbak POS Message Service
Selection	Comment
Date from	Default last available End of day
Date to	Default last available End of day
Relevant hidden parameters:
pRetailStore	Store, default 1001
pReasonCodesExcluded	Reasons codes which will be excluded from breakage fields. Default 14 and 15.
Columns - One row per item group
Article Group Key	Article group key
Article Group name	Article text
Quantity	Quantity sold
VAT Class	Shows 4 if VAT% is 8, Shows 3 if VAT% is 15, shows 2 if VAT% is 25, shows 1 on all other values.
VAT %	VAT percentage
Ex. VAT	Shows sales excluding VAT
VAT	Shows VAT amount
Sales w/VAT	Shows sales including VAT
Butikknr	Retail Store
Net Cost	Net cost
Breakage Quantity	Quantity of broken items
Breakage Net Amount	Net cost of broken items

New report showing top sales per item

(RTC-14251)

In order to follow up on sales, a new report is created, showing top x sold items, grouped by area, item group or store.

Report require POS Reporting version 69.

Report details Top sales item
File name	0454_TopSalesPerItemWithItemInfo
Data source	Analysis services (Cube) and Lindbak POS Reporting DW (Database)
Selections
Date from	Default today
Date to	Default today
Compare date from	Default same day in same week last year
Compare date to	Default same day in same week last year
Retail store	Default all
Article area	Default all
Article group	Default all
Grouping	Default area
Count	How many items to show - Default 10. Default valuye can be change in hidden parameter pCount
Sort type	If items sould be sorted by best or wors - Default best. Default value can be change in hidden parameter pSortType
Sort measure	What mesure to sort by. Available measures are Amount, Quantity, Net Cost, Gross profit or Gross profit %. Default Amount
Include VAT	If VAT should be included in sales amount or not. Default Yes. Default value can be changed in hidden parameter pIncludeVAT
Vendor	Default all
Subvendor	Default all
EAN list	Default empty
Columns - One row per item
Area	Article area
Grp	Article group
EAN	EAN
Item name	Item name
Article info	Label text 2
Date from	Date to
Quantity	Quantity sold
Turnover	Sales amount
Gross profit	Gross profit
Gr. prof. %	Gross profit percentage
Compare date from	Compare date to
Quantity	Quantity sold
Turnover	Sales amount
Gross profit	Gross profit
Gr. prof. %	Gross profit percentage

Sales Report per department/area based on EOD

(RTC-14074)

New report showing sales per department in 4 tables divided by Article group numbers. Period is based on EOD (End of day).

Report details Sales per department
Filename	0608_SalesPerDepartment
Data source	Lindbak POS Reporting DW database
Selections	Comment
Retail store	Store, default first store in list
Year	Default current year
EOD Date from	Default last available EOD
EOD Date to	Default last available EOD
Include nonsale	If nonsale is included in sale. Default true
Relevant hidden parameters
pArticleGroupList1	Add Article Group numbers for Articles to be displayed in first table (Fuels)
pArticleGroupList2	Add Article Group numbers for Articles to be displayed in second table (Retail goods)
pArticleGroupList3	Add Article Group numbers for Articles to be displayed in third table (Automatic Car Wash)
pArticleGroupList4	Add Article Group numbers for Articles to be displayed in fourth table
pIncludeNonsale	If Include nonsale should be default true or false
Columns - One row per distinct combination of Department, Article Area and Vat%
Department	Department number
Dept name	Department name
Area no	Article Area number
Area name	Article Area name
Quantity	Quantity sold
VAT class	Shows 4 if VAT% is 8, Shows 3 if VAT% is 15, shows 2 if VAT% is 25, shows 1 on all other values
VAT%	VAT percentage
Ex. VAT	Shows sales excluding VAT
VAT	Shows VAT amount
Sales w/VAT	Shows sales including VAT

Sales report per item/item group based on EOD

(RTC-14037)

New report showing sales per item / item group where period is based on EOD (End of day).

Report details Sales per item
Filename	0607_SalesPerItemInGroup
Data source	Lindbak POS Reporting DW database
Selections	Comment
Retail store	Store, default first store in list
Year	Default current year
EOD Date from	Default last available EOD
EOD Date to	Default last available EOD
Include nonsale	If nonsale is included in sale. Default true
Article group	Default All
Relevant hidden parameters:
pIncludeNonsale	If Include nonsale should be default true or false
Columns - One row per item. Group by Item group / VAT
EAN	EAN
Item	Article text
Quantity	Quantity sold
VAT class	Shows 4 if VAT% is 8, Shows 3 if VAT% is 15, shows 2 if VAT% is 25, shows 1 on all other values
VAT%	VAT percentage
Ex. VAT	Shows sales excluding VAT
VAT	Shows VAT amount
Sales w/VAT	Shows sales including VAT

Receipt Journal Access

(RTC-13766)

There is a new tab named Journal Access in user view. In this tab user is able to choose one of two options. This choice impacts to which stores user has access in Receipts Journal. After selecting the first option, available stores
match permissions given in User tab. When second option is chosen, user has access only to stores which are included in the selected configuration group. If user has "Manage receipts for all stores" access role, all stores are
available in Receipts journal view. If user has access to the configuration group which has become empty or inactive, available stores match permission from User tab.
Journal access tab in editing user view will be visible only if configuration parameter JournalAccessStoreConfigurationGroup is set to True (default value is False)

Password requirement when changing password in POS and Chain Web

(RTC-12019)

New system parameter CashierPinCodeLength has been added. It defines the minimal length of the cashier password. Default value of this parameter is 6. When cashier's password is changed, it will be validated if it is shorter than the value defined in CashierPinCodeLength parameter. Additionally, the current password cannot be reused as the new cashier password.

Improvements

Module	Description
Accounts receivable	Manual adjustment of credit balance (RTC-8235) User with permission is able to correct customer credit balance. There is also a possibility to check the balance history. Corrections of the balance will be saved in the balance history as a recharge or as a deduction of funds.
Balance	Receipt Journal requires store to be selected (RTP-12435) Receipt Journal requires store to be selected When a HQ user filter receipts in Receipt Journal and does not select a store filter - receipts for all stores will be shown by default. Refund (RTP-12075) When an active campaign price is lower than the originally paid price of an item it is refunded without errors. Add permission for edit balance older than x hours (RTC-9862) New system parameter "EditBalanceNotPermittedIfOlderThanHours" which defines time (in hours) after which the editing of balance will not be permitted if user is not HQ user or does not have proper permission. New role "Edit balance older than x hours" which allows user to edit balances older than time defined in "EditBalanceNotPermittedIfOlderThanHours" parameter. The user without this role is not able to edit old balances (this applies to the shift balances too).
Customer Orders	Editing a row in Customer Order (RTC-10476) Net cost field has been renamed to Weighted net cost. This field's working principle didn't change - Weighted net cost is equal to the result of multiplying the UnitNetCost by the QuantityOrdered. There is also a new field named Net cost and it's equal to net cost field in the database. Deleting and Updating C&C orders (RTC-13761) When a click & collect order is deleted in EG POS, the order will be marked as deleted and also the picking order details with lines will be deleted from Chain Web. The picking order will be correctly marked in Chain Web with the PickingOrderStatus = Delivered after the picking will be finished in EG POS.
General	Simple search (RTC-14386) Improvements were made to the "simple search" in the Items grid, in customer search of sales/ orders/ grids and and in the other Chain Web areas where the simple search is used.
Gift card	Migrate all data (RTC-8096) New job AllGiftCardsExporter has been added to the GiftCards Integration package. It exports all giftcards (both active and inactive) with transactions to the blob GiftCardUpdated2 (contract in gifcardservice version 2). This job should be enabled only when giftcard service version 2 is used. The job send message to the cloud service bus, where the GiftcardsImport job reads it and insert data (giftcards, transactions) to the Lindbak GiftcardService database. Resend digital gift card (RTC-14111) There is a DigitalGiftcardEnabled in System Parameters. It decides which button to show in Gift cards view. If this parameter is set to true, user has the possibility to resend gift card. If this parameter is set to false, user has possibility to remind PIN. These options work for gift cards with or without email address/phone number assigned. If both a mobile number and an email address are assigned to the gift card, then information automatically will be sent only to the email.
Item	Search for items per store (RTC-13062) User is able to see items for each store when using "Search for item" (simple search) in the Items' grid.
Order Dispatch	Returning order lines (RTC-11715) It is not possible to return more order lines than allowed - for example, when user is trying to return the same order line in two separate browser windows. The proper message is visible in three languages - English, Norwegian and Swedish:
Reports	Bestseller report (RTC-13118) We have changed name of "sum" column to clarify that amounts are in thousands Changed report: Bestseller (0041_BestSellerPerStorePerArticle) Sales statistics report (RTC-10886) Some improvements have been made in report Sales statistics. In some cases, values for gross profit % excluding campaign would show n/a insetead of percentage value. Changed report: 0714_SalesStatisticsWithDrill Report 8002 - Credit Sales (RTC-12775) Deleted receipts are no longer shown in report 8002. Selection on price channel in reports (RTC-13892) To improve reporting on sales from different channels, we have added Price channel as selection in following reports: Top sales per item with compare date (0454_TopSalesPerItemWithItemInfo) Sales by product area (0456_SalesByPRoductAreaOrGroupWithInteractiveSorting) Cashier statistics report (RTC-13893) To improve following up cashiers, we have created new report. The report is identical to Cashier statistics (0018_CashierStatistics) with two new columns for manual discount. This shows data for all Line discounts given manually in POS. Amount - Manual discount in amount for Line discount. Percent - Manual discount in percentage for Line discount (discount / amount * 100) Translation: "No reports available" (RTC-14193) If there aren't any reports in the Reports view, following message is displayed: "Ingen rapporter tilgjengelig".
Shift Balance	Balance date is set to "End Shift" date (RTC-14353) When balance is configured to use shift, the balance date in shift balances is equal to the date of End Shift. Expected values on tenders while doing edit balance operation (RTC-14602) The proper expected values for tenders are displayed while editing shift balance or new cashier balance registration. One label "Counted" has been renamed to "To bank" in shift balance creation process in register bag step for a better user experience.
Stocktaking	Stocktaking improvements (RTC-8023, RTC-7724) The following changes are implemented in the stocktaking module: The delete button is hidden in more button (...). The count list button is grey and the refresh button has been renamed to refresh stock level. For finished stocktakings (for all types), statistics have been changed. If it took 0s to finish the stocktaking, there is no information about the duration in the statistics on stocktaking dashboard. There are some changes in stocktaking's area. In some grids there are new columns: Created by, Modified Date and Modified by. Those columns are hidden by default. Also, Date column is renamed to Created Date. Grids affected by those changes: Count lists, Stocktakings, Count lists in given stocktaking and Archive.
System	Logging in Integration Platform (RTP-12974) A logging issue with LIP in cloud where disconnected users was logged as exceptions is corrected.
User Management	Filter on modified date (RTC-9094) User is able to filter modified date column in the User view.

Chain Web v. 2.10.65

Released 12th of January 2022

Improvement

Missing shift settlement (RTC-18432)

Shift settlements from one cash register did not show in Chain Web when shifts with a Shift-ID that already existed from another cash register in the same store. This is improved.

Shift ID is no longer unique per store. The same shift ID within the same store can be used, but only once per cash register.

Chain Web v. 2.10.64

Released 21 September 2021

Improvement

Fix for permissions (RTC-15672)

When parameter UsersCanOnlyAssignRolesTheyAreAssignedTo is active and some user is editing the other one, the added/removed are changed only for that user (not for the user that are editing as well).

Chain Web v. 2.10.62

Released 8th of July 2021

New report - Sales per item

(RTC-14247)

New report showing sales per item group where period is based on EOD (End of day). Made based on report 0600.

Report details Sales per item
Filename	0609_SalesPerArticleWithBreakage
Data Source	Lindbak POS Reporting DW and Lindbak POS Message Service
Selection	Comment
EOD Date from	Default last available End of day
EOD Date to	Default last available End of day
Relevant hidden parameters:
pRetailStore	Store, default 1001
pReasonCodesExcluded	Reasons codes which will be excluded from breakage fields. Default 14 and 15.
Columns - One row per item group
Article Group Key	Article group key
Article Group name	Article text
Quantity	Quantity sold
VAT Class	Shows 4 if VAT% is 8, Shows 3 if VAT% is 15, shows 2 if VAT% is 25, shows 1 on all other values
VAT %	VAT percentage
Ex. VAT	Shows sales excluding VAT
VAT	Shows VAT amount
Sales w/VAT	Shows sales including VAT
Butikknr	Retail Store
Net Cost	Net cost
Breakage Quantity	Quantity of broken items
Breakage Net Amount	Net cost of broken items

Improvement

Expected values on tenders while doing edit balance operation (RTC-14602)

The proper expected values for tenders are displayed while editing shift balance or new cashier balance registration.
One label "Counted" has been renamed to "To bank" in shift balance creation process in register bag step for a better user experience.

Chain Web v. 2.10.61

Released 30th of June 2021

New user interface for handling stores in Dispatch rules

(RTC-13056, RTC-13053)

The overview section in Dispatch rules consists of general information regarding current Web shop store, how many central warehouse stores, Dispatch stores or Pay & Collect stores are set:

The edit button in the overview section redirects user to the Stores grid:

User can filter the selected store/stores, set one or more stores as warehouse, P&C store or Dispatch store. In the grid there is a possibility to filter the stores and its current settings.

It is possible to set one or more stores as Warehouse, P&C store or dispatch store by using particular buttons - or to use new popup where the user can add/remove the settings for single store:

Additionally, user can save settings without activating or save + activate settings. Furthermore, it is possible to export store grid to Excel to get a complete overview of all stores and which store category they fall under.

Configuration of sub menu in PLU Board in POS Configuration

(RTC-13695)

The configuration of PLU Boards (convenience sales mode) supports sub menus.

Sub menus are added like this:

Enter button title and upload the desired image for the button.

Sub menus are displayed like this in the parent page (arrow top right corner of the button):

Sales Report per department/area based on EOD

(RTC-14074)

New report showing sales per department in 4 tables divided by Article group numbers. Period is based on EOD (End of day).

Report details Sales per department
File name	0608_SalesPerDepartment
Data source	"Lindbak POS Reporting DW" database.
*Selections*	*Comment*
Retail store	Store, default first store in list.
Year	Default current year.
EOD Date from	Default last available EOD.
EOD Date to	Default last available EOD.
Include nonsale	If nonsale is included in sale. Default True.
*Relevant hidden parameters:*
pArticleGroupList1	Add Article Group numbers for Articles to be displayed in first table (Fuels).
pArticleGroupList2	Add Article Group numbers for Articles to be displayed in second table (Retail goods).
pArticleGroupList3	Add Article Group numbers for Articles to be displayed in third table (Automatic Car Wash).
pArticleGroupList4	Add Article Group numbers for Articles to be displayed in fourth table.
pIncludeNonsale	If Include nonsale should be default True or False.
*Columns* - One row per distinct combination of Department, Article Area and Vat%.
Department	Department number
Dept name	Department name
Area no	Article Area number
Area name	Article Area name
Quantity	Quantity sold.
VAT class	Shows 4 if VAT% is 8, Shows 3 if VAT% is 15, shows 2 if VAT% is 25, shows 1 on all other values.
VAT%	VAT percentage.
Ex. VAT	Shows sales excluding VAT.
VAT	Shows VAT amount.
Sales w/VAT	Shows sales including VAT.

Sales report per item/item group based on EOD

(RTC-14037)

New report showing sales per item / item group where period is based on EOD (End of day).

Report details Sales per item
Filename	0607_SalesPerItemInGroup
Data source	"Lindbak POS Reporting DW" database
*Selections*	*Comment*
Retail store	Store, default first store in list.
Year	Default current year.
EOD Date from	Default last available EOD.
EOD Date to	Default last available EOD.
Include nonsale	If nonsale is included in sale. Default true.
Article group	Default All
*Relevant hidden parameters:*
pIncludeNonsale	If Include nonsale should be default True or False.
*Columns* -One row per item. Group by Item group / VAT
EAN	EAN
Item	Article text.
Quantity	Quantity sold.
VAT class	Shows 4 if VAT% is 8, Shows 3 if VAT% is 15, shows 2 if VAT% is 25, shows 1 on all other values.
VAT%	VAT percentage.
Ex. VAT	Shows sales excluding VAT.
VAT	Shows VAT amount.
Sales w/VAT	Shows sales including VAT.

Daily report for fuel sales

(RTC-13540)

This report will allow the user to gain insight on the fuel sales per day and view the stock, and stock variance per day.

Report: 0751_DailyWetStock

Report for showing fuel and sales

(RTC-12690)

In order to report on fuel stock and sales we have created a wet stock report. This report allows the user to monitor whether the actual fuel stock is correct compared with the amount of fuel sold.

Report details Wet stock
File name	0750_WetStock
Data source	Reporting cube (Olap)
*Selections*	*Comment*
Date from	Default 1. of previous month.
Date to	Default last day of previous month.
Retail store	Default all
*Relevant hidden parameters:*
pVariance	Threshold when to color columns for Daily Variance orange. Default 200.
pVariancePrc	Threshold when to color columns for Daily Variance %. Default 0,75%
*Columns* - Report is grouped per fuel tank group, showing one row per day in selection.
Date	Date
Opening Stock	Stock from automatic or manual reading. If not available it will be calculated. If calculated values will be shown with pink color.
Deliveries	Delivery transactions (from Chain).
Sales	Sales for tank group (from POSLog)
Adjustments
Book Stock	Opening stock + Deliveries - Sales.
Actual Stock	Stock from reading.
Water Measure In Tank	Water in liters, if value is not 0 it will be colored red.
Daily Variance	Difference between actual and book stock in liters. If value exceeds value from pVariance it will be colored orange.
Daily Variance %	Daily variance divided by sales, in percentage. If value exceeds value from pVariancePrc it will be colored red.
5 Day Cumulative Variance	Difference between actual and book stock in liters, last 5 days.
5 Day Cumulative Sales	Sales for tank group, last 5 days.
5 Day Cumulative Variance %	Daily variance divided by sales, in percentage, last 5 days.
31 Day Cumulative Variance	Difference between actual and book stock in liters, last 31 days.
31 Day Cumulative Sales	Sales for tank group, last 31 days.
31 Day Cumulative Variance %	Daily variance divided by sales, in percentage, last 31 days.

Improvements


Balance	Shifts receipts in Receipt Journal (RTP-11724) New shift and end shift receipts are displayed in Receipt Journal in the same way as in printed receipt
Customer	Import of item list in customer group discount (RTC-13360) A loading indicator is displayed when importing item list or item group list to a customer group (for discounts). When the import has finished, a green notification is displayed to inform that the import was successful, or an orange notifications to inform that an exception occured.
Dispatch rules	Automatic Reassign: Issue with Delivery Method Configuration (RTC-11608) It is possible to configure automatic reassign for delivery methods defined in CustomerOrderDeliveryMethods system parameter. That means delivery methods for reassign order are expanded to include all delivery methods available in CustomerOrderDeliveryMethod system parameter and are possible to be set in Dispatch Rules -> Reassigning Order as an option for automatic reassign. Additionally, Reassign Order Delivery Methods are no longer dependent on Delivery methods selected in Delivery Methods section.
Invoicing	Date when adding payment of invoice (RTC-13609) When adding payment to the invoice, payment date from date picker is displayed and processed in correct format, according to user settings. When for example the user has Norge as region, the date is displayed in Norwegian date format.
Gift card	Resend digital gift card (RTC-8266) There is a DigitalGiftcardEnabled in System parameters. It decides which button to show in Gift cards view. If this parameter is set to true, user has the possibility to resend gift card. If this parameter is set to false, user has possibility to remind PIN. These options work for gift cards with or without email address/phone number assigned. If both a mobile number and an email address are assigned to the gift card, then information automatically will be sent only to the email.
Order dispatch	Handle lack of delivery suggestions from DispatchService (RTC-13806) Dispatch orders are processed correctly even if there are no suggestions available from DispatchService. Issue deleting order lines with unsupported characters (RTC-10215) Order line in a dispatch order can be successfully removed even if it contains special characters like: '()", Fix validation of dispatch rules (RTC-12099) Dispatch rules correctly displayed and can be saved with default values. Error messages are displayed correctly when invalid values are entered fields. This is done to increase user friendliness of the dispatch solution, as previously the user would get no indication as to why they were unable to save the dispatch rules.
Reports	Deleted receipts in Store settlement report (RTC-12984) Previously, we did not show data for cashier if they only had deleted receipt and no sale. This is corrected and cashiers with only deleted receipts will also appear in the report. Changed report: 0450_StoreSettlementPerOperator. Report sales per profile (RTC-13527) In order to report sales per profile, Profile parameter is added to the following reports: 0100_WeekReport 0101_Monthreport 0103_TotalSales 0113_WeekReportNoEcommerce 0114_TotalSalesNoEcommerce
Shift balance	Fix for inbound amount (RTC-13861) The amount "Submitted to bank" for shift balances is calculated properly. The Inbound amount is not replacing drawer money when registering balance for shift. Balance date is set to "End Shift" date (RTC-14353) When balance is configured to use shift, the balance date in shift balances is equal to the date of End Shift.
Stocktaking	Item synchronization performance (RTC-10344) A new database index is added to improve general performance when synchronizing (deactivated/deleted) items from Chain Classic to Chain Web.
User Management	Create AD users (RTC-12968) We fixed a bug related to changes in AAD integration that broke the functionality in User Management for creating normal AD users. All AD users created during the period that the bug was present will have to be deleted.

Chain Web v. 2.10.55

Released 15th of October 2021

Improvements

Dispatch - Persist delivery status of order (RTC-16419)

Dispatch order grid and details view load under 1s.

Improvements Reporting (RTC-15732)

To make sure all reports using sub-report 1700_subSettlement and 1706_subStatistics, we have made sure reports will work with older versions of Reporting.

Shift balance - Expected values on tenders while doing edit balance operation (RTC-14602)

Chain Web v. 2.10.50

Released 31st of May 2021

Update POS with order line split

(RTC-10570)

Support for creating multiple picking store per one delivery line in customer order has been implemented. It is possible to a create dispatch order which could have one delivery line split into two or more lines to different stores with different quantities (according to the DispatchService suggestion). If one store are not able to deliver all items from one order line it will be split between one or more stores, so that the customer ultimately received the number of items ordered.

Shift Balance

(RTC-12255, RTC-12258, RTC-12259, RTC-12370, RTC-13386, RTC-12366)

Balance registration for retailers using shifts is available in menu Financials → Shift balances.

The grid shows created shifts sorted by newest on top, with standard functionality for filtering and sorting. User can create a new balance or edit an existing one for the selected shift. All changes are handled as a standard balance, which are displayed in Balances.

The user can preview document with details of given shift, and download the document as PDF:

Furthermore, access controls are available which allow granting or revoking permissions from users for Viewing, Creating and Editing Shift Balance. When POS Configuration for ReceiptStatistics is set to True, the receipt statistics are fetched and saved in Shift balance. Ingoing balance information is shown in the balance header. Shifts are sorted by Started Date descending in shifts' grid. Additionally, the user can see shifts' starts and ends in Receipt journal. They are located in Receipt type filter in System transactions -> Other.

When the task "StartEndShift" is enabled in POS Services worker, Shifts' tasks are created. Then the shifts are created in Retail database by balance service. Update EnabledTasks parameter in config of POS Services Worker with new value "StartEndShift".

New report for payment types per shift

(RTC-11492)

New report showing relevant statistics related to payment for selected shifts (0851_PaymentTypesPerShift). This will allow retail chains using shifts to monitor and follow up on the transactions and events during specific shifts.

Report details
File name	0851_PaymentTypesPerShift.rdl
File name sub-reports:	1700_subSettlement.rdl, 1706_subStatistics.rdl
Data source	Analysis services (Cube)
*Selections*	*Comment*
Date from	Shows all shifts with stated date between Date from and Date to - Default today.
Date to	Shows all shifts with started date between Date from and Date to - Default today.
Retail store	Choose store.
Workstation	Default all.
Shift	Default all in chosen date range.
*Columns -* Report shows 2 sub reports.
Settlement: (1700_subSettlement.rdl). 1 row per payment type:
Received	Sum of received payments for payment type.
Balance	Sum of counted amount for payment type. This is only shown for Cash, Finance, Check and Total all coupons and Gift cards.
Difference	Difference between received amount and counted amount for payment types that have counted amount.
Quantity	Number of payments.
Statistics (1706_subStatistics.rdl):
Description	1 row per Cancelled receipts, Receipts with return, Returned items, Deposit refund received 12%, Deposit refund received 25%, Deleted items, Price change and Nullsale
Amount	Sum amount, only for Returned items, Deposit refund received 12%, Deposit refund received 25%, Deleted items.
Quantity	Quantity
Share	Share of the sale. Only for Returned items, Deposit refund received 12%, Deposit refund received 25%, Deleted items.

Improvements


Customer	Import customer in ARTS XML format (RTC-13193) When customer data is importing from ARTS Customer format, customer type is updated (employee etc.)
Gift card	Synchronizing gift cards to cloud (RTC-13372) Gift cards are exported to the cloud also when there are committed transactions with amount =0. Fix for regive of gift cards (RTC-12236) When regive operation is done, ownerClaimType is set if it previously was empty. Requirement: Giftcards Integration package 1.4.0.
Invoicing	Fix for resend of EHF (RTC-12240) When opening Resend EHF, list of not sent EHFs are displayed properly, without timeout. User can customize results by using filter in column sent.
Receipt journal	View workstation startup transaction (RTC-12756) User can see workstation's starts in Receipt journal. They are located in Receipt type filter in System transactions -> Other.
Stocktaking	Check if update of stocktaking is completed (RTC-13035) It is possible to enable/disable checking check if update of stocktaking is completed during creation of new stocktaking. System Parameter: CheckForCompletedPosLogsInChainEnabled True/False that decide if we are checking the last POSLog in Chain Classic or not. The main functionality was implemented in RTC-776. The Inventory transactions (POSLogs) that are cancelled (when the processing of all items will fail), will be excluded from check for the last processed transactions in Chain Classic during stocktaking creation. New column SourcePosLogCancelled was added in the StockAdjustmentBatch with the information if the POSLog was cancelled during the adjustment. If all lines failed, then the receipt is cancelled, if there is at least one not failed line, then POSLog is not cancelled and the StockAdjustmentBatch will be marked with the default value False in SourcePosLogCancelled column.

Chain Web v. 2.10.40

Released 26th of May 2021

Cashier statistics

(RTC-11456)

In report for cashier statistics (0018) three new columns are added.

Changed report: 0018_CashierStatistics_std / Cashier statistics

New columns:

Waste - Shows values for transaction type Breakage. It is possible to set up Report to show only Breakage with spesific Reason code. This is done by setting ReasonCode in parameter pReasonCodeWaste.

Discount - Shows number of articles with discount.

Scan % - Shows percentage of scanned articles (Scanned articles / Sum quantity articles).

Support shifts when counting per cash register

(RTP-4895)

Previously, drawer balance has been registered and validated per date and either per register/workstation, cashier or store. New parameter has been created to support shifts when counting per cash register.

POS Configuration

New parameter:
BalancePeriod - Defines the balance period type. Parameter can be set to "Date" (default) or "Shift".

Existing relevant parameters:
BalanceTransactionType - Can currently be set to Cashier, Workstation or Store. When BalancePeriod is "Shift", counting will always be done per cash register.

New report for shift statistics

(RTC-11449)

New report showing key statistics for retail chains working per shift.

Report details for Shift statistics
File name	0850_ShiftSatistics.rdl
Data source	Analysis services (Cube)
*Useful hidden parameter*
pDeletedStatuses	Which deleted statuses to include for column "Deleted Amount" and "Deleted quantity".
*Selections*	*Comment*
Date from	Shows all shifts with stated date between Date from and Date to - Default today
Date to	Shows all shifts with stated date between Date from and Date to - Default today
Retail store	Default all.
*Columns -* one row per shift.
ShiftID	Shift ID
Start	Start time for shift.
Stop	Stop time for shift.
Cashier	Cashier name.
Customers	Number of customers for shift.
Nullsale	Number of nullsale and drawer openings for shift.
Deleted amount	Amount of deleted items.
Deleted quantity	Number of deleted items.
Avg amount	Average transaction value (sold amount / customers).

Cashier statistics report

(RTC-794)

A new cashier statistics report is created to analyze and investigate cashier behavior. In order to create this report, the following changes are implemented in Reporting:

Order history is stored in new table: FactOrderHistory
Order history data is added to Olap.

Report requires Reporting v. 67

Report details for Cashier statistic
File name	0904_CashierStatistics
Data source	Lindbak POS Reporting cube (Olap).
*Parameters*
pCustomerGroupPersonell	Which customer group personell belongs to. Default value = 100.
pDiscountReasonCodeType	Which reasoncodetype to include in Manual discount - Default LineDiscount.
pManualDiscount	Which discount type to include in Manual discount - Default Line.
*Filters*	*Comment*
Date from	Default today.
Date to	Default today.
Retail store	Default all.
Operator	Default all.
*Columns -* one row per operator.
Cashier
No	Cashier number
Name	Cashier name
Returns
Qty	Quantity of returned articles.
Amount	Amount of returned articles.
Deleted receipts
Qty	Quantity of deleted receipts.
Amount	Amount of deleted receipts.
Deleted item lines
Qty	Quantity of deleted item lines
Amount	Amount of deleted item lines
Manual discount (discounts filtered by parameter pManualDiscount and pDiscountReasonCodeType )
Qty	Quantity of manual discounts
Amount	Amount of manual discounts
Diff settlement (difference between tender cash and balance cash)
Amount	Difference in amount.
Deleted web orders (orders with order type "WebShop Order" and order status "Deleted")
Qty	Quantity of deleted web orders.
Amount	Amount of deleted web orders.
New customer orders (orders with order type "Store Order" and status "Created")
Qty	Quantity of new customer orders
Amount	Amount of new customer orders
Offline coupons (tender coupons with coupon type = "O"
Qty	Quantity of offline coupons.
Amount	Amount of offline coupons.
Personell discount (discount with customers from customer group in parameter pCustomerGroupPersonell)
Qty	Number of receipts containing personell discount.

Support for hiding homepage dashboard

(RTC-8234)

System parameter KpisEnabled is correctly handled and kpis's on home page are hidden when parameter is set to False.

Required Configuration

System parameter KpisEnabled = True kpis are visible on home dashboard

System parameter KpisEnabled = False kpis are not visible on home dashboard. Only reports and favorites should be visible.

Measure SLA fulfillment in hours not days

(RTC-9698)

The option that measures the SLA fulfilment in hours has been added to CustomerOrderDeliverSlaType in CustomerOrderDeliveryMethod config. To enable configuration of hours value for CustomerOrderDeliverSlaType_, the DeliverySlaValue was added to CustomerOrderDeliveryMethod config too. To ease providing appropriate value, the descriptions for CustomerOrderDeliverSlaType have been added to the system parameter.

Required configuration:

In System parameters-> CustomerOrderDeliveryMethod:

Possible values for DeliverySlaType are:

"1" - Today,
"2" - Tomorrow,
"3" - Days 3 to 4,
"4" - Days 3 to 10,
"5" - Hours (was added)

When Hours is set as DeliverySlaType (was added) , the DeliverySlaValue has to be set to the number of hours.

Improvements


Balance	Historical exchange rate in Balance (RTC-12275) If parameter UseCalculatedExchangeRateInBalance is set to True in POS Configuration for POS WCF, the correct historical exchange rate is used when registering Balance in Chain Web.
Customer	Import of customers without SSN (RTC-12873) When creating or updating customer by using import of customers in ARTS XML format. Social Security Number is not set on customer in Lindbak Retail database if it is not present in import file.
Customer order	Deleting an order line in payment mode in POS should not delete order line in Chain Web (RTC-12235) Lines deleted in payment mode in POS are properly processed in Chain Web and are not deleted from the order.
Dispatch orders	Dispatch Orders - Performance improvement (RTC-11645) Loading of rows in Dispatch Orders grid has been optimized. The loading time is not significantly visible for the user when opening the Dispatch Orders grid or when scrolling through the Dispatch Orders list.
Dispatch rules	Order line split (RTC-10889) "Allow splitting line in web order" checkbox added to the Dispatch Rules configuration. It allows enabling/disabling of splitting order lines in the web order. The functionality for order line split will be released in 2.10.50.
Item	Performance improvement in Item grid (RTC-10402) When opening Items grid, list of items is displayed. User can narrow and customize results by using filters in columns or write key word in simple search window to find a specific item.
POS Configuration	"English text" on menu buttons (RTP-11379) The field for "English text" has been added to menu buttons in ButtonConfig parameter.
Reports	Sales per department (RTC-12048)To make PDF print look better we have made minor adjustment to column widths. The formatting of some columns are improved to only show two decimals. Changed report 0453_SalesByProductAreaOrGroup.

Chain Web v. 2.10.35

Released 17th of September 2021

Improvement

POS unit filtering in Receipt journal (RTC-9114)

Fixed a problem where POS unit filter field were not removed as it should.

Chain Web v. 2.10.34

Released 8th of September 2021

Improvements

Date when adding payment of invoice (RTC-13609)

When adding payment to the invoice, payment date from date picker is displayed and processed in correct format, according to user settings. When for example the user has Norge as region, the date is displayed in Norwegian date format.

Date when adding payment of invoice (RTC-13609)

POS API - Refund of active campaign items in Chain Web (RTP-12075)

When returning items in Chain Web and an active campaign price is lower than the originally paid price of an item, it can be refunded without errors.

Receipt Journal requires store to be selected (RTP-12435)

When a HQ user filter receipts in Receipt Journal and does not select a store filter - receipts for all stores will be shown by default.

View workstation startup transaction (RTC-16118)

User can see shift's starts/ends, workstation's starts and signing in/out in the Receipts journal. They are located in Receipt type filter in System transactions -> Other.

Chain Web v. 2.10.33

Released 11th of June 2021

Improvements

Support for hiding homepage dashboard (RTC-8234)

System parameter KpisEnabled is correctly handled and kpis's on home page are hidden when parameter is set to False.

Required Configuration:

System parameter KpisEnabled = True KPIs are visible on home dashboard.
System parameter KpisEnabled = False KPIs are not visible on home dashboard. Only reports and favorites should be visible.

Create AD users (RTC-12968)

We fixed a bug related to changes in AAD integration that broke the functionality in User Management for creating normal AD users.

All AD users created during the period that the bug was present will have to be deleted.

Chain Web v. 2.10.32

Released 02nd of June 2021

Improvements

POS Configuration - Configuration group - stores without PrivateStoreGroup triggers errors (RTP-11908)

Correct stores are properly returned and can be added in the store group configuration section without errors/ warnings. The stores which doesn't contain PrivateStoreGroup will not be available in this view, and will be unlinked from the configuration group after save of it.

Synchronizing gift cards to cloud (RTC-13372)

Gift cards are exported to the cloud also when there are committed transactions with amount =0.

Fix for regive of gift cards (RTC-12236)

When regive operation is done, ownerClaimType is set if it previously was empty.

Requirement: Gift cards Integration package 1.4.0.

Chain Web v. 2.10.31

Released 28th of April 2021

Improvements


Account Receivable	Validation of payment date (RTC-10893) When adding payment to invoice, payment date cannot be earlier than invoice creation date.
ChainToCloud Integration	Add support for new file types (RTM-236) Added support in ChainToCloudJob to support new file types which are sent to cloud. New supported file types: budsjett (budget), vareliste (item list), stock. Required: ChainToCloudIntegration package version 1.6.
Customer	Importing item list to customer group (RTC-9646) When an item does not have a price in selected store during import of item list to customer group, an error message is displayed to inform the user of what the problem is. Import of customers with SSN (RTC-11762) When creating or updating customer by using import of customers in ARTS XML format, Social Security Number is updated properly on customer in Lindbak Retail database. Default invoice by email to customers with email address (RTC-9742) When customers (private and credit) are created with email address in POS, the customer will default be updated with the flag checked for 'Invoice by email'. Inactive customer groups are default hidden (RTC-10439) When opening Customer Groups, inactive groups are default hidden. In order to see hidden groups, user needs to change filters in Inactive column. User can also narrow and customize search results by using filters in columns.
Customer order	Bugfix: Calculation of gross profit (RTC-11944) When adding new items to customer order and changing the unit price and net cost, gross profit is calculated according to the new values. Offer expiration date (RTC-9887) When creating new offer, "Valid to" field is set by default to the expiration date (14 days from today's date). User can change it by date picker. It is also possible to change the default value under the "DefaultOfferExpirationDays" parameter in Chain Web system parameters. When viewing already created offer, "Date" and "Valid to" fields are set according to the offer's creation date and expiration date. Disable the order locking functionality by default (RTC-11511) The Customer Order locking feature is disabled by default, the user need to change the value of Chain Web system parameter "CustomerOrderLockingEnabled" to True, to enable it. Parameter description: If set to True Customer Orders will be blocked from being handled in POS and Chain Web at the same time. Customers blocked for credit (RTC-11586) When opening a Customer Order with status Draft, Changed or Active, or when creating a new order directly from customer view, a message is shown to user when the customer is blocked for credit. Preventing simultaneously changes to a customer order (RTC-908) When a customer order is being changed from POS, it will be locked for simultaneously changes from both POS and Chain Web to prevent loss of data. Information is shown in the order details view when the order is locked. Any update/change of the order is not allowed when the order is locked. Users that want to edit the order must wait and try again later. Additional technical information: Order locking feature will work with versions EG POS 3.0.0.12401 or newer. For more information about changes in POS, please read release notes related to "Don't allow editing the same order in POS and Chain Web".
Homepage dashboard	Refresh data automatically when changing store (RTL-133) Data in Homepage dashboard is refreshed automatically when the store is changed to another one. Additionally, when 'View for all stores' is checked, the data in Homepage dashboard is refreshed automatically. Wrong Mapping For Sales Per Hour (RTC-3144) The mapping for sales per hour was corrected and presents correct values for customers per hour and sales per hour. Both comparison and main date are correctly loaded and return correct results. Furthermore, setting the comparison date greater than the main date and main date lower than the comparison date is impossible, and dates are automatically changed into the greatest or the lowest one possible. When setting the comparison date greater than the main date, it is automatically changed into the greatest one possible equal to the main date. The same happens when setting the main date lower than the comparison date.
Invoicing	Summation per receipt (RTC-9721) When the invoice contains multiple receipts, there is an additional line with summation per receipt of total excluding VAT and total including VAT.
Item	Performance improvement in Item grid (RTC-10402) When opening Items grid, list of items is displayed. User can narrow and customize results by using filters in columns or write key word in simple search window to find a specific item.
Order dispatch	Partially delivered dispatch orders (RTC-10302) When dispatch order is partially delivered, after removing the item line from the not-delivered order, the freight item is reassigned to the delivered line with correct quantity delivered amount (should be 1). This previously did not work as intended and has now been corrected. Update picking order with shipment number when delivered from AutoStore (RTC-7709) The picking order's ShipmentNumber is updated by Chain Web based on ShipmentTrackingNumber from POSLog provided by AutoStore. This gives the ability for the tracking link to be included in the email sent to the customer.
Order Management	Rejected order lines (RTC-10838) In order to display number of rejected order lines, Reporting imports this status from Retail database. This is done by existing package FactOrderRetail. This package require Retail database version 2.10.0.7 or higher because of new procedures. Note: There are some limitations to this functionality: To get rejected status we need to fetch changes in Retail db and changes in POSLog. In some cases this can result in incorrect status for Order lines. Case1: We update changes in Retail database in one Rt-job, but not changes from POSLog. Status for order line will be ONLY Rejected. Before we update POSLog we will not have assign status for new store. Case2: We update changes in POSLog in one Rt-job, but not changes from Retail db. In this case Rejected lines will have status "Reassigned" before we update correct status from Retail db. Case3: We create order, reject it in Chain Web. If we update changes from Retail db before all POSLogs, we will only have reassigned status in Reporting.
Reports	Swedish translations (RTC-12047) Swedish translation corrected for "Subvendor" in reports 0013, 0110, 0452.
Stocktaking	View and filter stocktaking's (RTC-12540) User can edit and view all types of stocktaking's. Additionally, when viewing selected stocktaking, it's possible to filter results in Out Of Scope column.

Chain Web v. 2.10.24

Released 29th of April 2021

Improvements

Fix translations for Order Dispatch (RTC-12098)

Translations in Dispatch Rules has been improved and English and Norwegian version is working as expected.

Swedish translations (RTC-12047)

Swedish translation corrected for "Subvendor" in reports 0013, 0110, 0452.

Sales per department (RTC-12048)

To make PDF print look better we have made minor adjustment to column widths.

We have also improved formatting of some columns to only show two decimals.

Changed report 0453_SalesByProductAreaOrGroup.

View and filter stocktaking's (RTC-12540)

User can edit and view all types of stocktaking's. Also, when viewing selected stocktaking, it's possible to filter results in Out Of Scope column.

Chain Web v. 2.10.23

Released 13th of April 2021

Improvements

Customers blocked for credit (RTC-11586)

When opening a Customer Order with status Draft, Changed or Active, or when creating a new order directly from customer view, a message is shown to user when the customer is blocked for credit.

Partially delivered dispatch orders (RTC-10302)

When dispatch order is partially delivered, after removing the item line from the not-delivered order, the freight item is reassigned to the delivered line with correct quantity delivered amount (should be 1). This previously did not work as intended and has now been corrected.

Chain Web v. 2.10.22

Released 19th of March 2021

Include Order Documents in SMS

(RTC-10169)

When sending an SMS with the order confirmation, receipt or credit note to the customer, it is possible to include a downloadable link. When the customer clicks the link they will be able to download a PDF of the respective order document. The user can include the order document in the SMS by using a new SMS variable in the SMS templates configured in Dispatch rules.

Required configuration:
Order Message Integration 1.4.0

CustomerOrderIntegration (from CustomerOrderService) jobs:

GenericImport - Default configuration
OrderMessageJanitor - Default configuration
OrderMessageProcess - Default configuration
StagingCleanup - Default configuration

Update picking order with shipment number when delivered from AutoStore

(RTC-7709)

The picking order's ShipmentNumber is updated by Chain Web based on ShipmentTrackingNumber from POSLog provided by AutoStore. That gives the ability for the tracking link to be included in the email sent to the customer.

Improvement


Customer order	Disable the order locking functionality by default (RTC-11511) The Customer Order locking feature is disabled by default, the user need to change the value of Chain Web system parameter "CustomerOrderLockingEnabled" to True, to enable it. Parameter description: If set to True Customer Orders will be blocked from being handled in POS and Chain Web at the same time. Preventing simultaneously changes to a customer order (RTC-908) When a customer order is being changed from POS, it will be locked for simultaneously changes from both POS and Chain Web to prevent loss of data. Information is shown in the order details view when the order is locked. Any update/change of the order is not allowed when the order is locked. Users that want to edit the order must wait and try again later. Additional technical information: Order locking feature will work with versions EG POS 3.0.0.12401 or newer. For more information about changes in POS, please read release notes related to "Don't allow editing the same order in POS and Chain Web".
Order Management	Rejected order lines (RTC-10838) In order to display number of rejected order lines, Reporting imports this status from Retail database. This is done by existing package FactOrderRetail. This package require Retail database version 2.10.0.7 because of new procedures. Note: There are some limitations to this functionality: To get rejected status we need to fetch changes in Retail db and changes in POSLog. In some cases this can result in incorrect status for Order lines. Case1: We update changes in Retail database in one Rt-job, but not changes from POSLog. Status for order line will be ONLY Rejected. Before we update POSLog we will not have assign status for new store. Case2: We update changes in POSLog in one Rt-job, but not changes from Retail db. In this case Rejected lines will have status "Reassigned" before we update correct status from Retail db. Case3: We create order, reject it in Chain Web. If we update changes from Retail db before all POSLogs, we will only have reassigned status in Reporting.
System	Upload RIGAL files to Cloud (RTC-849) DirectoryListnerJob job in FileListener Integration package can upload any files to FileService based on a list of predefined content type or a list of Regex'es. The job can be configured to upload Chain/POS files (butikk, vpi, pris and so on), RIGAL files (V, K, M, Varetran and so on) or custom files types based on Regex. Detailed documentation on how the job works and how to set it up can be found in the documentation tab in Integration Platform Management App.

Customer order

Disable the order locking functionality by default (RTC-11511)

The Customer Order locking feature is disabled by default, the user need to change the value of Chain Web system parameter "CustomerOrderLockingEnabled" to True, to enable it.

Parameter description:

If set to True Customer Orders will be blocked from being handled in POS and Chain Web at the same time.

Preventing simultaneously changes to a customer order (RTC-908)

When a customer order is being changed from POS, it will be locked for simultaneously changes from both POS and Chain Web to prevent loss of data. Information is shown in the order details view when the order is locked. Any update/change of the order is not allowed when the order is locked. Users that want to edit the order must wait and try again later.

Additional technical information:

Order locking feature will work with versions EG POS 3.0.0.12401 or newer.
For more information about changes in POS, please read release notes related to "Don't allow editing the same order in POS and Chain Web".

Order Management

Rejected order lines (RTC-10838)

In order to display number of rejected order lines, Reporting imports this status from Retail database.

This is done by existing package FactOrderRetail.

This package require Retail database version 2.10.0.7 because of new procedures.

Note: There are some limitations to this functionality: To get rejected status we need to fetch changes in Retail db and changes in POSLog. In some cases this can result in incorrect status for Order lines.

Case1: We update changes in Retail database in one Rt-job, but not changes from POSLog. Status for order line will be ONLY Rejected. Before we update POSLog we will not have assign status for new store.
Case2: We update changes in POSLog in one Rt-job, but not changes from Retail db. In this case Rejected lines will have status "Reassigned" before we update correct status from Retail db.
Case3: We create order, reject it in Chain Web. If we update changes from Retail db before all POSLogs, we will only have reassigned status in Reporting.

System

Upload RIGAL files to Cloud (RTC-849)

DirectoryListnerJob job in FileListener Integration package can upload any files to FileService based on a list of predefined content type or a list of Regex'es.

The job can be configured to upload Chain/POS files (butikk, vpi, pris and so on), RIGAL files (V, K, M, Varetran and so on) or custom files types based on Regex.

Detailed documentation on how the job works and how to set it up can be found in the documentation tab in Integration Platform Management App.

Chain Web v. 2.10.20

Released 12nd of March 2021

Tracking number as SMS variable

(RTC-10875)

When defining the SMS template for Shipping Confirmation and Split Order Shipping Confirmation it is possible to include [tracking number] as an SMS variable.
It allows for messages generated in OrderMessage SMS to contain short tracking link or tracking number to track ordered packages. The tracking number will appear as a link that the customer can click to see the progress on the shipment.

Required configuration:
OrderMessage Integration 1.3.0.

CustomerOrderDeliveryMethod system parameter should contain "TrackingUrl", for example: "TrackingUrl": "http://www.postnord.no/nb/vare-verktoy/pakkesporing?searchquery=SHIPTMENTID#dynamicloading=true&integration=TrackAndTraceById&shipmentid={0}”-> the {0} at the end is to display tracking link where {0} will be replaced with tracking number.

Example of fake configuration that would display tracking number, but direct the customer to Google:

SMS templates for order documents

(RTC-727)

SMS templates for order documents, such as Receipt, Order Confirmation and Credit Note are been added to “Confirmation Messages” in Dispatch rules. Support for {first name}, {last name}, {order number} and {document link} as SMS variables are added as well, which enables messages generated in OrderMessage SMS to contain customer's first name, customer's last name, order number and short link to respective PDF document in SMS messages (See “Document Link SMS variable for more information).
It is only possible for user to get SMS messages if one of the communication channels is set to SMS.

Document link SMS variable

(RTC-10170)

Support for {document link} in Order Dispatch confirmation messages is introduced the SMS templates for: Receipt, Order confirmation and Credit Note.
It is possible for SMS messages generated in OrderMessage to contain short link to a PDF document that the customer can click when receiving the SMS in order to view a PDF of the receipt, order confirmation or credit note.

Required configuration:
OrderMessage Integration 1.3.0

New status form AutoStore

(RTC-7951)

When a picking order is assigned to the central warehouse, the picking order gets the status “In Progress” in Chain Web after receiving a message from AutoStore that picking has started. Picking Orders do not have status “New” all the time until the order is paid. Instead, after Picking is started, Dispatch Orders gets status “In Progress”. This change is implemented in order to be able to easily distinguish between dispatch orders from AutoStore and other Dispatch orders.

Export of data from Count group view to Excel

(RTC-10606)

The user is able to export the data from count groups view to Excel (from count groups and status tab). The user can choose which data to export to Excel by filtering the grid beforehand. This makes it easier to for example, check which stores that are not completing their daily counting and which groups that are often excluded from counting.

Deletion of yesterday’s count lists and stocktakings

(RTC-838)

When store staff forget to finish the Random stocktaking with at least one activated count list which contains count group link, then the unfinished/not completed stocktakings will be be deleted, during night job execution, so store staff can start on a new, empty stocktaking the next day. Not activated countlists which contains count group link will be deleted as well.

Requirements: Enable and configure new job StocktakingEraserJob placed under BackOfficeIntegrationSubscriber

Filter on vendor, subvendor and EAN list

(RTC-9806)

We have extended three existing reports with new filters for vendor, sub vendor and EAN list.

EAN lists is created and maintained in Report. This is not item lists created in Item management module.

Changed reports:

Sale statistics / 0013_SaleStatisticsWithDrill
Sale statistics / 0110_SaleStatistics
Top sales per item with compare date / 0715_TopSalesPerItemWithCompareDate

Update of name for workstation types in Report

(RTC-9822)

In reports for cash register frequency the names of workstation types are updated. This will make it easier for the user to know which workstations the report is printed for. It is also possible to maintain the list of available price channels.

Changes in following parameters:

pPriceChannels - Comma separated list of price channels available in selection. Price channels customer is not using can be removed from list.
pWorkstationISA (ISA) -Renamed from pWorkstationITAB, default value = 98

pWorkstationTypeSCO (SCO) - Renamed from pWorkstationTypeSO, default value = 41,42,43,44,45,46,47,48,49,61,62,63,64,65,66,67,68,69

pWorkstationTypeWebshop (WebShop) - New, default value = 91,92

pWorkstationTypeOther (Other) - New, default value = empty.

(Note that translation of price channel names are done in RTP-4265)

Report for breakage and waste items

(RTC-9812)

To be able to report broken items to supplier, a report which lists item transactions are created.

Report details for Item transaction list
File name	0452_BreakageAndWasteTransactions
Data source	Analysis services (Cube)
*Relevant parameter*
pTransactiontypesToExclude	List of transaction types not to be included in Report. Default following transaciton types are excluded: ArticleService, StockAdjustment, Shrinkage, Inventory, InternalUse, InternalTransfer and DockingArea
*Selections/filters*	*Comment*
Date from	Default today.
Date to	Default today.
Retail store	Default all. If store user, store.
Subvendor	Default all.
Article area	Default all.
Article group	Default all.
Transaction type	Default all (does not show types excluded in pTransactiontypesToExclude).
Reason code	Default all.
*Columns -* one row per transaction. Grouping per store / supplier / EAN.
Item name	Item name.
Item number	Item number.
Number	Operator number.
Transaction type	Transaction type.
Reason code	Reason code used for transaction.
Date	Date for transaction.
Net amount	Net amount for transaction.
Quantity	Quantity for transaction.
Amount	Amount for transaction.

Sales by product area or group

(Jira link: RTC-9810, RTC-10022)

Report 0453_SalesByProductAreaOrGroup has been created for customers to be able to report on sales per item area and item group over a period compared to a previous period.

Report details for Sales by product area / Sales by product group
File name	0453_SalesByProductAreaOrGroup
Data source	Analysis services (Cube)
*Selections/filters*	*Comment*
Report type	If report should be based on article area or article group - Default area.
Date from	Default today.
Date to	Default today.
Comparable date from	Default same day in same week last year.
Date to comparable	Default same day in same week last year.
Article area	Default all (does not show if report type is Group).
Article group	Default all (does not show if report type is Area).
Retail store	Default all.
*Columns -* one row per article area / article group
Item area	Item area number and name
Date 1, based on sales between Date from and Date to
*Sales*
Sales Incl. VAT	Sales including VAT for Date 1.
Sales ex. VAT	Sales excluding VAT for Date 1.
Records
Quantity	Number of sold items for Date 1.
Price pr. Art	Average price per article for Date 1.
Gross profit
Amount	Gross profit amount for Date 1.
%	Gross profit percentage for Date 1
Date 2, Based on sales between Comparable date from and Date to comparable.
*Compare incl. VAT*
Sales incl. VAT	Sales including VAT for Date 2.
Diff.	Difference in sales amount (including VAT) for Date 1 and Date 2.
Diff %	Difference in sales between Date 1 and Date 2 in percentage.

Improvements


Customer	Remove reference text demand from local EHF (RTC-9743) When the customer is marked to "Save electronic invoice locally" , the checkbox "Reference number required" is editable. When "Reference number required" is set to False, reference number and reference text are not required when creating credit sales and customer orders. This feature makes the sales process more efficient when invoicing is done in a 3rd party system.
Customer order	Customer with credit blocked (RTC-9880) When creating customer order and adding customer with credit blocked, a warning message is displayed. Order can be saved but it is not possible to pay it by credit. For such customers credit sales cannot be created. Autosave for customer orders that are not submitted (RTC-3503) The integration job OrderSubmitter, included in the BackOfficeIntegrationSubscriber package, is responsible for submitting orders with statuses Draft and Changed which have not been submitted within a defined number of minutes. By default the job is executed every hour.
Invoicing	Invoice text "Foretaksregisteret" (RTC-10601) Field name on top of the invoice was changed in English and Norwegian version to "Foretaksregisteret" to align with legal requirements. Text in Swedish is previously defined according to Swedish legal requirements.
Reports	Translations in Report (RTC-10828) The Swedish translations of the price channel names in the dropdown list of parameter pPriceChannels (used in reports 0705/0706 and others) are updated with the following Swedish translations: Chain Web Manuell kassa InStore App Självscanning (SU) Mobilsjälvscanning Självbetjäning (SCO) Additionally, parameter pWorkstationType two values has new translations (“ITAB” is now changed to “ISA” and “SU” is now changed to “SCO”). Furthermore, pWorkstationType has two new items in the list (Web shop and Other). Translations (RTC-10894) The Swedish and Norwegian translation of the workstation type name "Other" in the dropdown list of parameter pWorkstationType (used in reports 0705/0706 and others) is updated with the following values: Swedish: Övriga Norwegian: Andre Additionally, the text "Web shop" is changed to “Webshop”, according to requirements. Translations (RTC-10988) The Swedish translations of two price channel names in the dropdown list of parameter pPriceChannels (used in reports 0705/0706 and others) are updated with the following: ShopAndGoCheckOut - Självbetjäning (SCO) ShopAndGoCheckTerminal - Självscanning (SU)
Stocktaking	Count group status (RTC-10659) When logging into Chain Web as a store user and navigating to the Count groups, only count groups available in the grid will be count groups that should be counted in the given store. The column "#items in stock" will display the number of items in the count group that the given store is expected to count. Improved transparency in count group grid (RTC-10793) When the counting of a count group has not yet started (including when counting was cancelled), the following fields will be blank: counted at, counted by and modified by. This was previously not the case and was confusing for the user. A modified date will be added for the count group with status "Not started", when the counting was cancelled, in order to show the user when it was cancelled. Show items added outside the count group (RTC-948) Added column “Out of scope” to the Count list view to show items that is added outside of Count group in InStore App.

Chain Web v. 2.10.14

Released 18th of March 2021

Improvements

Translations (RTC-10894)

The Swedish and Norwegian translation of the workstation type name "Other" in the dropdown list of parameter pWorkstationType (used in reports 0705/0706 and others) is updated with the following values:

Swedish: Övriga
Norwegian: Andre
Additionally, the text "Web shop" is changed to “Webshop”

Translations (RTC-10988))

The Swedish translations of two price channel names in the dropdown list of parameter pPriceChannels (used in reports 0705/0706 and others) are updated with the following:

ShopAndGoCheckOut - Självbetjäning (SCO)
ShopAndGoCheckTerminal - Självscanning (SU)

Chain Web 2.10.13

Released 2 March 2021

Export of data from Count group view to Excel

(RTC-10606)

Improved transparency in count group grid

(RTC-10793)

When the counting of a count group has not yet started (including when counting was cancelled), the following fields will be blank: counted at, counted by and modified by. This was previously not the case and was confusing for the user. A modified date will be added for the count group with status "Not started", when the counting was cancelled, in order to show the user when it was cancelled.

Improvement

Translations in Report (RTC-10828)

The Swedish translations of the price channel names in the dropdown list of parameter pPriceChannels (used in reports 0705/0706 and others) are updated with the following Swedish translations:

Chain Web
Manuell kassa
InStore App
Självscanning (SU)
Mobilsjälvscanning
Självbetjäning (SCO)

Additionally, parameter pWorkstationType two values has new translations (“ITAB” is now changed to “ISA” and “SU” is now changed to “SCO”).
Furthermore, pWorkstationType has two new items in the list (Web shop and Other).

Chain Web v. 2.10.12

Released 25th of February 2021

Update of name for workstation types in Report

(RTC-9822)

Changes in following parameters:

pPriceChannels - Comma separated list of price channels available in selection. Price channels customer is not using can be removed from list.

pWorkstationISA (ISA) -Renamed from pWorkstationITAB, default value = 98

pWorkstationTypeSCO (SCO) - Renamed from pWorkstationTypeSO, default value = 41,42,43,44,45,46,47,48,49,61,62,63,64,65,66,67,68,69

pWorkstationTypeWebshop (WebShop) - New, default value = 91,92

pWorkstationTypeOther (Other) - New, default value = empty.

(Note that translation of price channel names are done in RTP-4265)

Improvement

Count group status tab (RTC-10659)

When logging into Chain Web as a store user and navigating to the Count groups, only count groups available in the grid will be count groups that should be counted in the given store. The column "#items in stock" will display the number of items in the count group that the given store is expected to count.

Chain Web v. 2.10.11

Released 18th of February 2021

Create CustomerManagementToBatch2 job publishing JsonLines

(RTC-10471)

In BackOfficeBatchGenerator package new CustomerManagementToBatch2 job, using the same contract as CustomerManagementToBatch job, publishes JsonLines batches. This job replaces the previous "CustomerManagementToBatch" job, if all subscribers (e.g. POS Import) are up-to-date and support JsonLine format.

Required version: BackOfficeBatchGenerator 1.4.1

Create Customer2 job publishing JsonLines

(RTC-10388)

In BackOfficeBatchGenerator package new Customer2 job, using the same contract as Customer job, publishes JsonLines batches. This job replaces the previous "Customer" job, if all other subscribers are up-to-date and support JsonLine format.

Required version: BackOfficeBatchGenerator 1.4.0

Deletion of yesterday’s count lists and stocktakings

(RTC-838)

When store staff forget to finish the Random stocktaking with at least one activated count list which contains count group link, then the unfinished/not completed stocktakings will be be deleted, during night job execution, so store staff can start on a new, empty stocktaking the next day. Not activated count lists which contains count group link will be deleted as well.

Requirements: Enable and configure new job StocktakingEraserJob placed under BackOfficeIntegrationSubscriber

Improvement

Default price channel should be "None" (RTC-10067)

When creating new user, default price channel is not set by default.

Chain Web v. 2.10.10

Released 18th of February 2021

Version Requirements is located on the menu to the left.

User-friendly Item Texts

(Jira links: RTC-812, RTC-697, RTC-981)

Web shops often display user-friendly item texts. When front-end includes item text, color and size in the web order sent to POS API, these texts will be used in order messages (Order/Delivery confirmation) sent to consumer. When front-end does not include the user-friendly texts the order messages will use standard texts, usually provided by supplier. This functionality is created for the order dispatch module.

Required configuration

OrderMessageIntegration package 1.2.0installation package available at:
\\nas_install\LRS\Lindbak Integrations\3.0\OrderMessageIntegration

POSServices 2.37.126.0

Automatic Reassign

(Jira links: RTC-715, RTC-3836, RTC-740, RTC-859, RTC-827)

The Chain Web parameter "InStoreRejectedPickingOrdersStoreNumber" is used to determine to which 'fake store' the order will be reassigned.

The dispatch orders can be reassigned automatically if no picking store is available or maximum number of automatic reassigns has exceeded the set value (configured in the dispatch rules - see below).

The user can find the configuration of automatic reassign in the dispatch rules grid. Configuration includes:

Select the delivery methods that can be reassigned automatically.
Default time before order is assigned to a new store.
To limit the max number of reassigns - this number only applies to number of automatic reassigns. Orders can be manually reassigned infinite times.

Reassigned orders are logged with from store/to store, time stamp of when the reassign occurred and reason code called "time limit expired", which tell the user why it was reassigned automatically. For orders that cannot be reassigned, shall be logged with the reason code ‘No store available’. These orders will automatically be reassigned to the fake store defined in system parameter, to allow HQ users to handle them manually.

In the picking order history in Chain Web grid, new column has been added. In the picking order history, it is possible to check the reassign actions made by the user or automatic reassigns, reason for reassign and time stamp.

Note: Dispatch orders from central warehouse will never be automatically reassigned.

Cloud authentication for cashiers

(RTC-730)

For mobile devices using store local Wi-Fi (or VPN), a 'Proxy' can be installed OnPrem with Chain Web to provide login to Mobile Apps/cloud modules with cashier number/pin code. This requires implementation in each app, and for now it is only planned for Mobile POS app to make it possible for multi-user devices.

Improvements


Accounts receivable	Roundings in EHF files (RTC-9092) The PayableAmountRounding field is saved in EHF files only when there is a rounding amount (different than 0). Rounding of credit sale (RTC-7089) In some instances, the rounding of items was wrongly calculated when creating a credit sale, causing a subtotal rounding of 0,01. This issue has been resolved.
Balance	Registered balances can be edited (RTP-4041) It is possible to edit balances after registration when system parameter "NewBalanceRegistrationEnabled" is True.
Cashiers	Export e-mail for cashier to POS (RTP-4001) Cashier e-mail will be exported to POS when updating cashier info in Chain Web and when mass exporting cashiers from Chain Web.
Customer order	Preventing simultaneous changes to a customer order (RTC-832) When a customer order is being changed from POS, it will be locked for simultaneous changes from both POS and Chain Web to prevent loss of data. Information is shown in the order details view when the order is locked. Any update/change of the order is not allowed when the order is locked. Users that want to edit the order must wait and try again later. Slow processing of customer orders (RTC-9676) Performance when updating customers is much faster after improving code related to handling of communication channels.
Order dispatch	Not possible to delete "last not delivered" item (RTC-7099) Corrected an issue related to removing last line from "in picking". Error handling of CompletePickingCriticalExceptions (RTC-10050) An issue with storing the DeliveryReceiptID caused internal transfers to not be performed correctly for some dispatch orders. This is corrected and values like DeliveryReceiptId and ShipmentNumber are stored correctly in the database.
POS Configuration	Config changes for "Self-service on customer (secondary) screen" (RTP-349) Function "Start self service" (START_SELF_SERVICE) has an option to set its argument "Run self-service on customer screen" to True or False when adding a button in ButtonConfig. After fixes function enabling the argument is called "Start self-service", the function in which we do not choose parameter is called "Start self-service (primary screen)". Configuration: ButtonConfig, function START_SELF_SERVICE Changes only in BackOffice. The functionality will be done and tested in the scope of this Product Backlog Item 188595: Self-service on customer (secondary) screen.
Stocktaking	Store number and store name in count group view (RTC-791) Stocktaking results can be filtered on counted/not counted counting groups per store per day. Splitting count groups which exceed 50 items (RTC-902) Import of count groups with more than 50 items per department will be split into several count groups so that more store staff can be involved in the stocktaking of a department. This is configured in the integration job CountingGroupImportProcessor in the parameter splitCountgroupsEnabled (default value False - splitting is disabled) and maxItems (default value 50).
System	Default region/language for cashiers (RTC-800) When creating a new cashier the region and language is based on the user who are creating the cashier.

Chain Web v. 2.10.08

Released 15th of December 2021

Improvements

Fixed changing password (RTC-16616)

User is able to change password of the cashier in "cashiers" and in "users". Changing ManageUsersAndCashiersIndependently setting has no impact.

Chain Web v. 2.10.06

Released 27th of April 2021

Improvements

Slow processing of customer orders (RTC-12567)

Performance when updating customers is much faster after improving code related to handling of communication channels.

Import of customers without SSN (RTC-12873)

When creating or updating customer by using import of customers in ARTS XML format, Social Security Number is not set on customer in Lindbak Retail database if it is not present in import file.

Chain Web v. 2.10.05

Released 22nd of April 2021

Improvement

Import of customers with SSN (RTC-11762)

When creating or updating customer by using import of customers in ARTS XML format, Social Security Number is updated properly on customer in Lindbak Retail database.

Chain Web v. 2.10.04

Released 18th of March 2021

Improvement

Configuration group - can't find store (RTP-3652)

Stores are properly returned and can be added in the store group configuration section.

Chain Web v. 2.10.03

Released 21st of January 2021

Improvement

Registered balances can be edited (RTP-4041)

It is possible to edit balances after registration when system parameter "NewBalanceRegistrationEnabled" is True.

Chain Web v. 2.10.02

Released 21st of January 2021

Improvements

Edit counted amount for weight items (RTC-713)

When editing the counted amount of item in stocktaking results view, weight items can be saved with decimals.

Performance and retry mechanism for export of large stocktakings (RTC-733)

Performance when exporting stocktaking results to 3rd party (inventory control) is improved for large stocktakings (>300K items). If something fails, a retry mechanism will wait a configured number of seconds before the next retry execution for this stocktaking.

Chain Web v. 2.10.01

Released 22nd of December 2020

Exporting cashiers to POS

IsActiveDirectory flag is included in the batch generated on CashierUpdatedEvent and CashierBatchExportEvent when exporting cashiers from Chain Web to POS. Previously, there was no support for exporting cashiers belonging to an Azure AD user.

Dependencies to another products:
BackOfficeBatchGenerator package in version 1.2.15 or higher required.

Chain Web v. 2.10.0

Released 21st of December 2020

ELMA Integration

(TFS: 185340)

The ELMA validation button has been added to the customer details view. It can be found in Invoicing tab when customer is a business customer and address is set in Norway.
The user can validate the organization number of Norwegian business customer against ELMA just by pressing 'Check if customer can use electronic invoice' button.

New balance registration

(TFS: 189541)

A new way of registering balance, where the user can see expected amount and difference on each tender, has been implemented. This balance is submitted without a bag, so there is no Bag registration step. After submitting tenders amount the balance is finished and the user can immediately create next balance for next active cashier. When there are no more active cashiers for the selected date, then a new balance registration cannot be created for this date.
In the new balance registration, editing of finished balance registration is disabled.

To use new balance registration, set up value of the new system parameter NewBalanceRegistrationEnabled to True. When value of NewBalanceRegistrationEnabled is equal to False, then the old balance registration will be present Chain Web.

Requirements: Reporting v.65, POS Services 7.77.03801

Stocktaking report with item area

(TFS: 189521)

New report showing stocktaking results divided by item area.

Inventory per item area
File name	0451_StockTakingItemAreaLevel.rdl
Data source	Lindbak Retail (database)
*Selections*	*Comment*
Date from	Default today.
Date to	Default today.
Retail store	Which store to run report for.
Stocktaking	Shows all stocktaking's for selected store within date from - to range.
Report shows inventory date and store number and name.
*Columns*, one row per item area.
Item area	Area number
Area name	Area name
Inventory value, Cost price	Sum cost price
Inventory value, Ex. VAT	Sum salesprice ex. VAT.
Inventory value, Sales amount inc. VAT	Sum salesprice inc. VAT.

Improvements


Customer	Line note in Customer Sales grid (TFS: 185458) When expanding the details on an item row, there is a column for Line Note. When searching for an item in the filter "Item name", the first 16 rows containing this item is automatically expanded. More rows can be expanded manually. This will enhance the user experience when looking through historical sales for a customer.
Invoices	Show the amount that is rounded in the invoice (TFS: 184868) Sum of rounding is visible on the invoice to make the rounding more transparant.
Reason codes	Reason codes for overridden price (TFS: 189485) The support for new reason code type "Change price" has been added. These reason codes can be created and maintained in Chain Web. Requirements: BackOfficeBatchGenerator 1.2.13, ChainIntegration 1.5.1
Report	Able to use hyphen when renaming reports (TFS: 189086) It is possible to use hyphen when renaming reports.
Stocktaking	Random count - refresh stock status in count lists (TFS: 184420) The stock level in a new count list can be refreshed when a count list is added to a stocktaking or activated. To refresh the stock level, the checkbox "Get stock level again for items in selected count lists" must be checked. The stocktaking status will then be "Creating" while the stock levels are being updated for the count list. If the stock level is not refreshed, the stock level for when the count list was submitted, is kept. New configuration parameters: SynchronousUpdateCountListMaximumSize - counted based on sum of all lines (unique SkuNumber) from all used count lists - default value: 1000 ReuseStockLevelExpiryTimeInMinutes - it is relevant, only for a small count lists (if sum of count lists lines < SynchronousUpdateCountListMaximumSize) - default value: 60 Don't allow creating new stocktaking if last stocktaking is not updated in Chain Classic (TFS: 189347) The user will not be able to create a new stocktaking in Chain Web (also with the refreshed stock level for the assigned count lists) inside the same store, until the last POSLog related to previous stocktaking (previous stock results) will be processed/ updated in Chain Classic. Related Chain Classic PBI with the requirements: Product Backlog Item 190077: 2.1.1: Sport1: Stocktaking: New proxy for checking that last stocktaking is finished