--- title: "Chain Web 2.10.220 - 2.10.141" slug: "chain-web-210220-210141" updated: 2026-08-05T05:38:38Z published: 2026-08-05T05:38:38Z canonical: "products.egretail.cloud/chain-web-210220-210141" --- > ## Documentation Index > Fetch the complete documentation index at: https://products.egretail.cloud/llms.txt > Use this file to discover all available pages before exploring further. # Chain Web 2.10.220 - 2.10.141 ## Chain Web v. 2.10.220 > [!TIP] > Released 1 February 2023 ### Bonus details - report ([RTC-28001)](https://jira.eg.dk/browse/RTC-28001) The new report lists changes in bonus balance and how much bonus is issued and used over a period of time. ![](https://confluence.eg.dk/download/attachments/50075166/image-2023-1-27_7-45-23.png?version=1&modificationDate=1675253650097&api=v2) | **Report details Bonus details** | | --- | | File name | 0117: Bonus details | | Data source | Lindbak POS Reporting DW | | **Selections:** | | Loyalty id | Loyalty program, default 1. | | Date from | Default today. | | Date to | Default today. | | Store | Default all. | | **Output:** Bonus checks overview. For each store sum of issued, redeemed, spent, expired and balance bonus checks with number of sales and members who got/used bonus. Next table with issued amount and member with bonus independent of chosen period. Total sum of each column for all selected stores. | | **Columns:** | | Members with bonus | Number of members with bonus amount balance greater than 0 (independent of chosen period). | | Issued amount | Total bonus amount issued (independent of chosen period). | | Store num | Store number. | | Store name | Store name (default sorted on this column). | | Total | The sum of issued amount in the selected period. | | Ordinary sales | The sum of bonus amount issued after purchases in the selected period. | | Manual checks | The sum of bonus amount issued manually in the selected period. | | Spent bonus | Total sum of redeemed amount in the selected period. | | Expired bonus | Total sum of amount that expires in the selected period (check expiration date is between date from and date to). | | Receipts paid with bonus | Number of sales (receipts) paid with bonus checks in the selected period. | | Members who used bonus | Number of unique members who have used bonus, redeemed transaction in the selected period. | | Member who got bonus | Number of unique members who got bonus, issued transaction in the selected period. | | Bonus balance | Sum of not-expired bonus amount at the end of the selected period. | > [!NOTE] > Clarifications > > - Receipts paid with bonus column shows count values selected on distinct member number and distinct transaction date, it resolves issues with the same transaction id at different web shops. > - All data is based on FactMemberTransaction. ### Bonus per store ([RTC-27636)](https://jira.eg.dk/browse/RTC-27636) Report shows information about issued, redeemed and balance for bonus checks, per month and store for the last 12 months. ![](https://confluence.eg.dk/download/attachments/50075166/image-2023-1-27_14-7-57.png?version=1&modificationDate=1675253650127&api=v2) | **Report details Bonus per store** | | --- | | File name | 950_BonusPerStorePerEndOfMonth | | Data source | Lindbak POS Reporting DW | | **Selections:** | | Loyalty program | Loyalty program, default 1. | | Team | Default all. | | Store | Default all available in selected teams | | **Output:** One page per store. For each month sum of issued, redeemed, balance and expired bonus checks. One sum for manual issued checks, checks issued from sales and total. First page of report is total for all stores. | | **Columns:** | | End of month | Shows last date in each month for the last 12 months. | | Bonus type | For each month there is one row for manual issues checks, checks issued from sales and total. | | Issued | Sum of bonus amount issued. | | Redeemed | Sum of redeemed bonus amount. | | Balance | Sum of not expired, not used bonus amount. | | Expiring | Expired Sum of bonus amount expired at the end of month. | | **Sorting:** Month | ### Reason code overview ([RTC-27768)](https://jira.eg.dk/browse/RTC-27768) Report lists all reason codes for all stores. Layout of the report makes it easy to export data to Excel. ![](https://confluence.eg.dk/download/attachments/50075166/image-2023-1-27_13-31-38.png?version=1&modificationDate=1675253650153&api=v2) | **Report details Item transaction reason code** | | --- | | File name | 0542_ItemTransactionReasonCode | | Data source | Lindbak POS Reporting cube (OLAP) | | **Selections:** | | Date from | Default today. | | Date to | Default today. | | Store | Default all (if HQ user) | | Transaction type | Default All types. It is possible to removed transaction types from list with hidden parameter pTransactionTypesToExclude, see relevant parameters for details. | | Reason code | Default all available codes. List shows only reason codes linked to selected transaction types. NB! Depending on Chain Web version. When you select transaction type, only first available reason code will be selected. Workaround for this is to de-select all reason codes before selecting transaction type(s). | | Absolute values | Default off. This will show all values as positive values. Used to get correct quantity when you have transactions with positive and negative values. Note that this will not affect sum of same item / reason code. Default selection can be changed in parameter pShowAbsoluteValues. | | **Relevant parameters:** | | pTransactionTypesToExclude | Comma separated list of transactions types not to show in list of transaction types. E.g. If customer never uses transaction type Article Service and Inventory, put in Normal,ArticleSerivce,Inventory in string (Normal should always be excluded) | | pShowAbsoluteValues | To change default value for 'Absolute values' selection | | pGrouping | To change default value for 'Grouping' selection | | **Output:** List of item transactions with reason codes. | | **Columns:** | | Store num | Store number. | | Store name | Store name. | | Transaction type | Transaction type. | | Reason code | Reason code (default sorted on this column). | | Net cost | Total net cost (cost price) for row. | | Quantity | Total quantity for row. | | Net amount | Total amount without VAT for row. | | Amount w / VAT | Total amount with VAT for row. | | GP% | Gross profit in percentage | > [!NOTE] > Clarifications > > - Action code is not supported, only reason code (action code not available in OLAP (reporting v77)) > - Report shows only item transactions from POSLog (no RIGAL) > - Showing absolute values for same item / reason code is not possible (reporting v77). Report will always show sum of same item / reason code even if there are positive and negative values. > - Example: > - ![](https://confluence.eg.dk/download/attachments/50075166/image-2023-1-27_13-51-31.png?version=1&modificationDate=1675253650183&api=v2) > - Without absolute values Report will show Quantity = -3 which is correct. > - With absolute values report will show Quantity = 3, ideally it should split this into two lines. ### System sound when order arrives in Kitchen Screen ([RTC-28203)](https://jira.eg.dk/browse/RTC-28203) Added sound indicating to cashier that a new order has arrived after it was added to the Kitchen screen. ****Web.config in BackOffice.Web**** Web.config in BackOffice.Web has to be configured to enable kitchen screen notifications: ** ** ** ** ** ** ** #### Improvements | | | | --- | --- | | **Balance** | **Error when opening Balance Summary** ([RTC-28251)](https://jira.eg.dk/browse/RTC-28251) Implemented fixes eliminated error occurring in Balance Summary view. | | **Customer Groups / Discount** | **Discounts imported from Item list and Item group list** ([RTC-21862)](https://jira.eg.dk/browse/RTC-21862) Providing the possibility to replace store and common discounts already existing in a grid (added from UI or imported from Excel file) with discounts imported from Item list and Item group list. If the item has both common and store discounts defined in the customer group discount grid, then the change of it's value is defined as Store value in the import pop-up screen. **Store and common level discounts** ([RTC-21860)](https://jira.eg.dk/browse/RTC-21860) Providing the possibility to create discounts at the store level and common level for the same item with overlapping dates. Adding the hierarchy of created discounts which means that store discount is taken into consideration even if there is a common discount. However, common discount is used for stores which don't have setup store-level discount. HQ user can see all created discounts, but for store user only their own store discounts and common are visible. Validation of overlapping dates is shown if the same item is added for the same store or common store multiple times with overlapping dates. | | **Customer Groups / Import** | **Import items into Customer group from Excel file** ([RTC-21854)](https://jira.eg.dk/browse/RTC-21854) Providing the possibility for store users and HQ users to import items into Customer group from Excel file with header (format .xlsx) that includes three expected columns: - Number (GTIN/EAN) - Price effect (number) - Value If the values in these columns are incorrect or out of range then the user is informed by appropriate notifications. Moreover if file contains more than three expected columns then the import is proceed and unnecessary columns are ignored. Changes to discounts done by HQ user is added as common discount, while changes done by a store user is added on store level. Additionally flag in database is added to the customer group while import is ongoing. As a result, other imports/ changes cannot be done using UI at the same time. Added button "Mark all" to select all lines and make it easier to delete them from customer group. **Discounts imported from large Item lists (more than 1000 items)** ([RTC-21430)](https://jira.eg.dk/browse/RTC-21430) Providing the possibility to import large item lists without timeout by both Store and HQ user. Users during import can work in Chain Web, change tabs and create Customer orders/sales/offers. Messages about starting processing and summarizing it have been added. | | **Database** | **Adding new field for Original ordered quantity** ([RTC-26642)](https://jira.eg.dk/browse/RTC-26642) Changes were implemented to store original ordered quantity in the retail database, so now it is possible for POS to check what quantity was ordered in the beginning. | | **Dispatch orders** | **Order from physical store without DispatchRuleID** ([RTC-28318)](https://jira.eg.dk/browse/RTC-28318) Only customer orders with a DispatchRuleId are considered for dispatching when created in physical store. Correctly handle dispatch orders with blank DispatchRuleId - fallback to web shop number. **Multiple lines with the same EAN** ([RTC-27648)](https://jira.eg.dk/browse/RTC-27648) Dispatch orders with multiple lines containing the same EAN are correctly dispatched (picking orders created) to the same picking store. **Confirmation messages for physical stores** ([RTC-26226)](https://jira.eg.dk/browse/RTC-26226) It is possible to send confirmation messages for dispatch orders from physical stores. The contents of the message will be decided by the assigned dispatch rule. It is possible to modify this message by going to the confirmation message tab inside the dispatch rule. If the dispatch rule is not specified the settings for the dispatch rule for web shop will be used. | | **Invoices** | **Remove hyphen from VAT** ([RTC-27450)](https://jira.eg.dk/browse/RTC-27450) After changes there is no longer hyphen displayed in VAT number, even if it occurs in organization number. **Can not set invoices to paid state because of very small remaining amount** ([RTC-26700)](https://jira.eg.dk/browse/RTC-26700) After fixes there is possibility to overpay a little bit (0,01) for invoices with 3 digits precision and very small amount left to pay (0,00x). While creating new invoice from internal transfer, the amount is now rounded, so the issue was eliminated. | | **Member campaign dashboard** | **Fix: Number of members in the target group** ([RTC-27198)](https://jira.eg.dk/browse/RTC-27198) The issue with all member campaign not showing number of members in target group was fixed. The member campaign dashboard should correctly show the number of members in the target group, regardless of the campaign type. **Fix: Mismatch between number of members in the target group** ([RTC-26469)](https://jira.eg.dk/browse/RTC-26469) The mismatch between number of members in the target group of the campaign shown in 'Details' and 'Dashboard' was resolved. | | **Offer** | **Old customer offers in state draft can not be handled in user interface due to deleted receipts** ([RTC-27856)](https://jira.eg.dk/browse/RTC-27856) After changes, OrderSubmitter is now also submitting offers. For fixing state of already broken offers there is SQL script attached to this story which can be done by EG-Support. | | **Receipt journal** | **Translations** ([RTC-28392)](https://jira.eg.dk/browse/RTC-28392) Deposit activities are properly translated in generated Excel files. | | **Reports** | **Top sales per item** ([RTC-27704)](https://jira.eg.dk/browse/RTC-27704) Small fix in query to get same amount of items for store when selecting specific store and grouping by item group. | | **Stock lookup** | **Lookup of stock failing CW 2.10.210** ([RTC-28202)](https://jira.eg.dk/browse/RTC-28202) Stock info is fetched properly - no popup "Error getting stockinfo" or similar occurs while adding item from Home page or Price Control. Correction of issue implemented in CW 2.10.210. | --- ## Chain Web v. 2.10.2191 > [!TIP] > Released 27th of September 2023 **Refund/ Return - fix for Not Paid status in dashboard** ([RTC-31261)](https://jira.eg.dk/browse/RTC-31261) The issue was only related to displaying Not Paid for completed orders on dashboard for the Orders where prices from order lines sum up to sum value with more than 2 decimals after comma. E.g. Total on order was 211,00 while lines sum up to 211,0002. --- ## Chain Web v. 2.10.218 > [!TIP] > Released 21 March 2023 #### Improvements **Refund/Return process** ([RTP-19382)](https://jira.eg.dk/browse/RTP-19382) The order should not be blocked for further refunds/ returns, if the process will fail on e.g. timeout, or payment. The returned/ refunded lines will be removed from order, or set as deleted and the started transaction will be cancelled - removed. **Refund/Return process** ([RTP-18663)](https://jira.eg.dk/browse/RTP-18663) The order should not be blocked for further refunds/ returns, if the process will fail on e.g. timeout, or payment. The returned/ refunded lines will be removed from order, or set as deleted and the started transaction will be cancelled - removed. **Editing rights on POS configuration parameters** ([RTC-30037)](https://jira.eg.dk/browse/RTC-30037) Users with 1-level/restricted access can no longer edit POS configuration parameters in Chain Web on common or "s-lag" level. **Configurable name of "External Loyalty Number"** ([RTC-29525)](https://jira.eg.dk/browse/RTC-29525) After adding new system parameter "ExternalLoyaltyNumberFilterOptions" it is now possible to configure name of the "External Member Number" field in sales filters in Receipts Journal. --- ## Chain Web v. 2.10.213 > [!TIP] > Released 20 January 2023 #### Improvements **Error when opening Balance Summary** ([RTC-28251)](https://jira.eg.dk/browse/RTC-28251) Implemented fixes eliminated error occurring in Balance Summary view. **Dispatch orders -** **Confirmation messages for physical stores** ([RTC-26226)](https://jira.eg.dk/browse/RTC-26226) It is possible to send confirmation messages for dispatch orders from physical stores. The contents of the message will be decided by the assigned dispatch rule. It is possible to modify this message by going to the confirmation message tab inside the dispatch rule. If the dispatch rule is not specified the settings for the dispatch rule for webshop will be used. --- ## Chain Web v. 2.10.212 > [!TIP] > Released 5 January 2023 #### Improvements | | | | --- | --- | | **Customer Groups / Discount** | **Discounts imported from Item list and Item group list** ([RTC-21862)](https://jira.eg.dk/browse/RTC-21862) Providing the possibility to replace store and common discounts already existing in a grid (added from UI or imported from Excel file) with discounts imported from Item list and Item group list. If the item has both common and store discounts defined in the customer group discount grid, then the change of it's value is defined as Store value in the import pop-up screen. **Store and common level discounts** ([RTC-21860)](https://jira.eg.dk/browse/RTC-21860) Providing the possibility to create discounts at the store level and common level for the same item with overlapping dates. Adding the hierarchy of created discounts which means that store discount is taken into consideration even if there is a common discount. However, common discount is used for stores which don't have setup store-level discount. HQ user can see all created discounts, but for store user only their own store discounts and common are visible. Validation of overlapping dates is shown if the same item is added for the same store or common store multiple times with overlapping dates. | | **Customer Groups / Import** | **Import items into Customer group from Excel file** ([RTC-21854)](https://jira.eg.dk/browse/RTC-21854) Providing the possibility for store users and HQ users to import items into Customer group from Excel file with header (format .xlsx) that includes three expected columns: - Number (GTIN/EAN) - Price effect (number) - Value If the values in these columns are incorrect or out of range then the user is informed by appropriate notifications. Moreover if file contains more than three expected columns then the import is proceed and unnecessary columns are ignored. Changes to discounts done by HQ user is added as common discount, while changes done by a store user is added on store level. Additionally flag in database is added to the customer group while import is ongoing. As a result, other imports/ changes cannot be done using UI at the same time. Added button "**Mark al**l" to select all lines and make it easier to delete them from customer group. **Discounts imported from large Item lists (more than 1000 items)** ([RTC-21430)](https://jira.eg.dk/browse/RTC-21430) Providing the possibility to import large item lists without timeout by both Store and HQ user. Users during import can work in Chain Web, change tabs and create Customer orders/sales/offers. Messages about starting processing and summarizing it have been added. | --- ## Chain Web v. 2.10.211 > [!TIP] > Released 23rd of December 2022 #### Improvements **Database - Adding new field for Original ordered quantity** ([RTC-26642)](https://jira.eg.dk/browse/RTC-26642) Changes were implemented to store original ordered quantity in the retail database, so now it is possible for POS to check what quantity was ordered in the beginning. **Order from physical store without DispatchRuleID** ([RTC-28318)](https://jira.eg.dk/browse/RTC-28318) Only customer orders with a DispatchRuleId are considered for dispatching when created in physical store. Correctly handle dispatch orders with blank DispatchRuleId - fallback to webshop number. **Stocklookup failing CW 2.10.210** ([RTC-28202)](https://jira.eg.dk/browse/RTC-28202) Stock info is fetched properly - now popup "Error getting stock info" or similar occurs while adding item from Home page or Price Control. Correction of issue implemented in Chain Web 2.10.210. --- ## Chain Web v. 2.10.210 > [!TIP] > Released 23rd of December 2022 ### Item transactions report ([RTC-26957)](https://jira.eg.dk/browse/RTC-26957) A new report showing item transactions has been created to get overview of item transactions from POSLog. This report will show all item transactions with reason code. **![](https://confluence.eg.dk/download/attachments/50075166/image2022-12-30_13-57-34.png?version=1&modificationDate=1673002877437&api=v2)** | **Report details Item transaction** | | --- | | File name | 0541_ItemTransactions | | Data source | Analysis services (Cube) | | **Relevant parameters:** | | pTransactionTypesToExclude | Comma separated list of transactions types not to show in list of transaction types. E.g. If customer never uses transaction type Article Service and Inventory, put in Normal,ArticleSerivce,Inventory in string (Normal should always be excluded) | | pShowAbsoluteValues | To change default value for 'Absolute values' selection. | | pGrouping | To change default value for 'Grouping' selection | | **Selections:** | | Date from | Default today. | | Date to | Default today. | | Store | Default all (if HQ user). | | Transaction type | Default all types. It is possible to removed transaction types from list with hidden parameter pTransactionTypesToExclude, see relevant parameters for details. | | Reason code | Default all available codes. List shows only reason codes linked to selected transaction types. NB! Depending on Chain Web version. When you select transaction type, only first available reason code will be selected. Workaround for this is to de-select all reason codes before selecting transaction type(s). | | Absolute values | Default off. This will show all values as positive values. Used to get correct quantity when you have transactions with positive and negative values. Note that this will not affect sum of same item / reason code. Default selection can be changed in parameter pShowAbsoluteValues. | | Grouping | Default Group. This will decide on which level of hierarchy report is generated. Report always shows item, it will also show total for group, area, department and store depending on selection. Default selection can be changed in parameter pGrouping. | | Department | To filter result on department. | | Article area | To filter result on article area. | | Article group | To filter result on article group. | | Columns *(sum for store and each level of hierarchy. Sum total on last row):* | | EAN | EAN of item. | | Item name | Item name. | | Item number | Item number. | | Transaction type | Transaction type. | | Reason code | Reason code. | | Date | Date of transaction | | Net price | Net price per unit. | | Price w/VAT | Price including VAT per unit. | | Quantity | Quantity. | | Net amount | Net amount (Net price * Quantity). | | Amount w/VAT | Amount including VAT (Price w/VAT * Quantity). | | GP% | Gross profit in percentage. | The full documentation of the report can be found at [List of reports](https://confluence.eg.dk/spaces/RTC/pages/125505883/List+of+reports), by clicking on report **0541_ItemTransactions** in the list. #### Improvements | | | | --- | --- | | **Customer order** | **Locking order** ([RTC-27093)](https://jira.eg.dk/browse/RTC-27093) Message displayed to user in Chain Web, when customer order is locked, was changed for more appropriate message in all languages. (English, Swedish, Norwegian). **Newtonsoft.Json.dll breaks web order export to 3.part** ([RTC-24801)](https://jira.eg.dk/browse/RTC-24801) Web orders export was fixed. There are no longer error messages occurring during processing of "ExportCustomerOrder" POSLogs related. | | **Dispatch orders** | **Sorting the Eldest Orders Ascending** ([RTC-28054)](https://jira.eg.dk/browse/RTC-28054) The default sorting of the dispatch order list is: orders containing missing items, then active orders with the status "new" or "in progress", then oldest to newest. **Order not reassigned from dummy store** ([RTC-27734)](https://jira.eg.dk/browse/RTC-27734) When considering if order line should be deleted automatic reassign gets dispatch suggestion for individual line instead of its available stock, which takes into account dispatch rules and stock reduction rules. **Order not deleted from POS when re-dispatched** ([RTC-27031)](https://jira.eg.dk/browse/RTC-27031) - When the last item line in a picking order is deleted by automated reassign, POS is informed about the aborted picking for the assigned store (and the picking order is not reassigned further). - When the whole picking order is reassigned to another store POS is informed about aborted picking for the previously assigned store **Support dispatching of orders from physical stores** ([RTC-23380)](https://jira.eg.dk/browse/RTC-23380) When DispatchRuleId (DeliveryDetails) is defined in POSLog then BackOffice service will use it to select dispatch rule used for dispatching picking orders. | | **Dispatch rule** | **Description in the popup for creating a new dispatch rule** ([RTC-26521)](https://jira.eg.dk/browse/RTC-26521) The Description for New Dispatch Rule creation has a clear and correct message: 'Rule applies for Web shop'. **Reassign limits in dispatch rules** ([RTC-26227)](https://jira.eg.dk/browse/RTC-26227) It is possible to modify reassign limits and opening days/hours for both Web shop rules and custom rules. | | **Fresh food scale integration** | **Export to Myhrvold scales** ([RTC-27273)](https://jira.eg.dk/browse/RTC-27273) FixedWeight in exported labels has a value from UnitPriceFactor in item details or 0 if there is no value there. | | **Invoices** | **Adjustment in color and size display** ([RTC-23994)](https://jira.eg.dk/browse/RTC-23994) When color and/or size has value "-" or field is empty, then there is no extra line with information about color and size, for all templates after fixes. **Adjustments to the invoice standard V1 and V2** ([RTC-23994)](https://jira.eg.dk/browse/RTC-23994) Adding color and size to the Invoice based on transactions using POS Services/ POSLog processing. If there are both color and size given during Customer order creation, these properties will be displayed on Invoice just below item text. If color or size is given then only one value will be presented on Invoice. If none of the properties are given, then there is no extra line with information about color and size. **Adjustments to the invoice layout standard V1 and V2** ([RTC-16646)](https://jira.eg.dk/browse/RTC-16646) Adding color and size to the Invoice based on transactions using POS Services/ POSLog processing. If there are both color and size given during Customer order creation, these properties will be displayed on Invoice just below item text. If color or size is given then only one value will be presented on Invoice. If none of the properties are given, then there is no extra line with information about color and size. | | **Invoice base** | **False warning displayed in the invoice base** ([RTC-26036)](https://jira.eg.dk/browse/RTC-26036) Fixes eliminated false warnings in the invoice base about internal transfers not being sent to credit. After improvements, warning occurs only when in the selected store is at least one internal transfer which was not sent to credit. | | **Receipt Journal** | **Inconsistent results and timeouts in Receipts Journal** ([RTC-26098)](https://jira.eg.dk/browse/RTC-26098) Process of free text searching in Receipts Journal was fixed and results are now consistent and timeout does not occur anymore. Process of searching for short date range has been improved. **External member number** ([RTC-23536)](https://jira.eg.dk/browse/RTC-23536) Processing of receipts was extended for "ExternalLoyaltyNumber" handling, the number will be stored in Journal database and it will be possible to use it in Receipts journal search. External member number field was added under the Sales filters in Receipts journal, it's visible if Chain Web system parameter "ShowExternalLoyaltyNumberFilter" is set to true. It is also possible to use External member number in quick search filter. External member number is visible next to member number (Loyalty number: xxxxxxxxx / **xxxxxxxxx**) on the receipt preview. | | **Reports** | **Campaign sales** ([RTC-25674)](https://jira.eg.dk/browse/RTC-25674) Selection for 'All campaigns, are removed from report 0042. It is only possible to select one campaign. | | **Stocktaking** | **Processing of basis files** ([RTC-27203)](https://jira.eg.dk/browse/RTC-27203) The processing of Basis files was improved, so now it is possible to setup additional scheduled trigger, which is independent of already existing directory content updated trigger. A new trigger should be started even if the standard trigger will be frozen. Additionally, the faulted basis file will be moved to subfolder with the date stamp, so there is no limit of how many files related to the same store could be moved + the retry mechanism was implemented to re-try the processing of not moved file 3 times. **BasisImport job** ([RTC-26498)](https://jira.eg.dk/browse/RTC-26498) The logs and processing of Basis was improved, so now more detailed error message - with the related line content will be thrown, if the processing of Basis file will fail and additionally the corrupted file will be moved to failedBasisFiles subfolder. Additional log message was added for CompletedWithNoEffect execution status. **Filtering in exported Excel file from stocktaking** ([RTC-26853)](https://jira.eg.dk/browse/RTC-26853) After fixes the value of the parameter ServerSideExportBatchSize does not limit the number of rows taken into account during filtration. All rows in the Excel file can be filtered. **Count list activation** ([RTC-26413)](https://jira.eg.dk/browse/RTC-26413) The process of count list activation was improved, for "Items Not Counted" and "Cycle stocktaking". Count list processing/ activation process should not be blocked anymore even if it's related to a default count group creation, or if the Items from related count list, already exist in stocktaking result with empty CountingGroupInStocktakingId. | | **User Management** | **Automatic logout** ([RTC-26407)](https://jira.eg.dk/browse/RTC-26407) Automatic logout was fixed and now time is counted since last activity in Chain Web instead of counting time since login like it was before fixes. | --- ## Chain Web v. 2.10.201 > [!TIP] > Released 31st of October 2022 **Inventory -** **BasisImport job** ([RTC-26498)](https://jira.eg.dk/browse/RTC-26498) The logs and processing of Basis was improved, so now more detailed error message - with the related line content will be thrown, if the processing of Basis file will fail and additionally the corrupted file will be moved to failedBasisFiles subfolder. Additional log message was added for CompletedWithNoEffect execution status. --- ## Chain Web v. 2.10.200 > [!TIP] > Released 31st of October 2022 ### New dispatch rule creation ([RTC-26045)](https://jira.eg.dk/browse/RTC-26045) - It is possible to create new dispatch rule with custom name. - It is possible to create new dispatch rule based on Web shop store. - Clicking create redirects the user to dispatch rule details were a draft of the dispatch rule is shown. ![](https://confluence.eg.dk/download/thumbnails/50075166/image2022-10-24_14-56-36.png?version=1&modificationDate=1667215587943&api=v2) #### Improvements | | | | --- | --- | | **Customer order** | **Creating new customer order** ([RTC-23460)](https://jira.eg.dk/browse/RTC-23460) By choosing "+1" icon on the customer order from customer menu a new window is opened where the user can fill in store, customer and project data, the same as during the standard order creation process. The same store as in store picker is selected by default. The focus is set in customer field when the window is opened. | | **Dispatch/** **Order picking status** | **New methods for updating picking status** ([RTP-17642)](https://jira.eg.dk/browse/RTP-17642) It is now introduced two new methods for updating picking status: - SetCustomerOrderPickingStatus - GetCustomerOrderPickingStatus The methods make setting and confirming the current picking status of an order possible. | | **Dispatch Orders** | **Dispatch rule details for physical stores** ([RTC-26047)](https://jira.eg.dk/browse/RTC-26047) It is possible to display and edit dispatch rules created for physical stores using a custom name/id. Changes are also made to the drop down list for "rule apply for Web shop" and "Central warehouse" making it impossible to select options that are not included in the list. **Order with shipping item only not cancelled** ([RTC-26291)](https://jira.eg.dk/browse/RTC-26291) DispatchOrderReassign job cancels customer order where there is only non-sale item left after removing other line(s). DispatchOrderReassign job removes line from picking order (assigned to dummy store) when there are still other lines left in picking order. | | **Invoice** | **Adjustments to the invoice standard V3** ([RTC-26113)](https://jira.eg.dk/browse/RTC-26113) Remove Reference text and number fields from invoice header and place them into invoice grid to avoid loosing information during consolidate invoice generation. If there is no reference text/ number added to the order, this fields are invisible on the invoice. Additionally, Payment terms and Our references fields have been added in invoice header and text "Reference" before the date in grid has been removed. During testing the previous assumptions (task: [RTC-22650](https://jira.eg.dk/browse/RTC-22650)) related to logo size and margins also have been checked. **Partially paid invoices** ([RTC-25823)](https://jira.eg.dk/browse/RTC-25823) EHF invoice's PayableRoundingAmount field is now taking PrepaidAmount into consideration as during calculation. | | **Receipt journal** | **Translation correction** ([RTP-18999)](https://jira.eg.dk/browse/RTP-18999) Proper Swedish translations have been added for activity "Deposit refund" in Receipt journal logs. | | **Reports** | **Customers without sale** ([RTC-25822)](https://jira.eg.dk/browse/RTC-25822) To get a better understanding of result in report, logic behind fetching data is changed. When we earlier listed all customers in the report, it showed last sale as '1900-01-01' for customers without sale after the selected date. Now, we are only listing customers without sales after selected date. For customers with no sales (ever), the last sales date will show a hyphen. | | **Stocktaking** | **Default configuration of "Activate the count lists automatically" checkbox** ([RTC-25220)](https://jira.eg.dk/browse/RTC-25220) When starting a new stocktaking, "Activate the count lists automatically" checkbox is now ticked based on the **ActivateCountListAutomaticallyCheckBoxOptions** system parameter value to avoid administration and support incidents. Moreover there is now possibility to set visibility and value of "Activate the count lists automatically" checkbox. **Activating count list** ([RTC-24681)](https://jira.eg.dk/browse/RTC-24681) When getting error message during activation of a count list, the user is no longer redirected to stocktaking window without having a chance to read the error message as of why it didn't activate. | | **Web.config/ Azure AD user** | **Fix related to sign in for Azure AD user (EG Cloud user)** ([RTC-26754)](https://jira.eg.dk/browse/RTC-26754) Providing configuration in BackOffice.Web.ActiveDirectory/Web.config to avoid duplicated references regarding Microsoft.Owin version. After fixes Azure AD user can login properly into Chain Web. | --- ## Chain Web v. 2.10.194 > [!TIP] > Released 13th of April 2023 **Comments on POS Configuration parameters** ([RTC-26752)](https://jira.eg.dk/browse/RTC-26752) Adding comments on parameters in Chain web works correctly now: the POS Configuration page is refreshed correctly and the "Activate" button on configuration set does not appear. --- ## Chain Web v. 2.10.192 > [!TIP] > Released 17th of January 2023 #### Improvements **Invoice - Adjustment in color and size display** ([RTC-23994)](https://jira.eg.dk/browse/RTC-23994) When color and/or size has value "-" or field is empty, then there is no extra line with information about color and size, for all templates after fixes. **Adjustments to the invoice standard V1 and V2** ([RTC-23994)](https://jira.eg.dk/browse/RTC-23994) Adding color and size to the Invoice based on transactions using POS Services/ POSLog processing. If there are both color and size given during Customer order creation, these properties will be displayed on Invoice just below item text. If color or size is given then only one value will be presented on Invoice. If none of the properties are given, then there is no extra line with information about color and size --- ## Chain Web v. 2.10.191 > [!TIP] > Released 4th of November 2022 #### Improvements **Partially paid invoices** ([RTC-25823)](https://jira.eg.dk/browse/RTC-25823) EHF invoice's PayableRoundingAmount field is now taking PrepaidAmount into consideration as during calculation. **Fix related to sign in for Azure AD user (EG Cloud user)** ([RTC-26754)](https://jira.eg.dk/browse/RTC-26754) Providing configuration in BackOffice.Web.ActiveDirectory/Web.config to avoid duplicated references regarding Microsoft.Owin version. After fixes Azure AD user can login properly into Chain Web. --- ## Chain Web v. 2.10.190 > [!TIP] > Released 6th of October 2022 ### Quick Stocktaking ([RTC-22174)](https://jira.eg.dk/browse/RTC-22174) In order to update stock inventory and receive refill for item which has low stock in the store shelf, it is possible to see stock balance. If it is wrong, employee is able to do a "Quick inventory" using the InStore App in a simple and fast way. 1. In stocktaking view in InStore App a new button called **Quick Stocktaking**" is available. ![](https://confluence.eg.dk/download/thumbnails/50075166/image2022-9-30_14-44-11.png?version=1&modificationDate=1665058361297&api=v2) ![](https://confluence.eg.dk/download/attachments/50075166/image2022-9-30_14-45-32.png?version=1&modificationDate=1665058361340&api=v2) 2. By scanning/searching item, it is added to quick stocktaking. In details the quantity may be changed (by scanning an item or typing the amount of counted items). ![](https://confluence.eg.dk/download/thumbnails/50075166/image2022-9-30_14-49-41.png?version=1&modificationDate=1665058361390&api=v2) 3. By scanning/searching the same item multiple times, counted quantity increase by 1. 4. In "More" options display total bar can be shown. ![](https://confluence.eg.dk/download/thumbnails/50075166/image2022-9-30_14-53-23.png?version=1&modificationDate=1665058361437&api=v2) ![](https://confluence.eg.dk/download/thumbnails/50075166/image2022-9-30_14-54-11.png?version=1&modificationDate=1665058361483&api=v2) 5. After finishing quick stocktaking, in confirmation view total quantity and number of scanned items is shown. ![](https://confluence.eg.dk/download/thumbnails/50075166/image2022-9-30_14-56-29.png?version=1&modificationDate=1665058361530&api=v2) 6. After confirmation, the inventory deviation is received in Chain Web and it is flagged as inventoried. ![](https://confluence.eg.dk/download/attachments/50075166/image2022-9-30_15-0-58.png?version=1&modificationDate=1665058361577&api=v2) ### Inventory on store without stock control ([RTC-22792)](https://jira.eg.dk/browse/RTC-22792) User will get the Item related information like UnitPrice, CostPrice, VatRate, Stock, Stock flag, even if the 'Inventory' flag is False in Chain Web or Chain Classic. Meaning the User can see all important values of the counted items during and after stocktaking. When 'Inventory' flag is set to False on the store: - Item related information will be fetched from Chain Classic via proxy or basis file. Basis file should contain only not stocked items. - 'Get stock level again for items in selected count list' should be visible if 'HideGetStockLevelCheckBox' configuration parameter is set to False. When 'Inventory' flag is set to True on the store: No changes, works as before. > [!NOTE] > Breaking changes > > Chain Web changes needs to be delivered with Chain Classic changes in [(RTC-23050)](https://jira.eg.dk/browse/RTC-23050) Stocktaking: Create stocktaking basis for non "stock control" stores. ***Requires Chain Classic version 2.1.1.0.31!*** #### Improvements | Module | Description | | --- | --- | | **BackOffice** **Integration Subscriber/ BackOffice** **Import** | **Processing JSON files with POS Configuration in FileService** ([RTP-18340)](https://jira.eg.dk/browse/RTP-18340) Support for importing POSConfigImport blobs from cloud to the on-premise Lindbak Retail database has been added to the BackOfficeImport package (GenericImport job). In order to process POSConfigImport blobs, a new POSConfigImportProcessor job has been added to the BackOfficeIntegrationSubscriber package. ***BackOfficeImport 1.3.4 or higher******!*** | | **Customer** | **Discount** ([RTC-25643)](https://jira.eg.dk/browse/RTC-25643) Correction on visibility of customer discount when adding discount from Arts XML. After changes, the discount now shows on the customer card in Chain Web. | | **Customer order** | **Refund and return** ([RTP-16124)](https://jira.eg.dk/browse/RTP-16124) Providing correct refund/return of discounted items from Customer order regarding Aera payments. **Adding order to Project** ([RTC-23876](https://jira.eg.dk/browse/RTC-23876)) Small change in how the system add customer orders to projects. | | **Dispatch order** | **Automatic Reassign Job - Rework** ([RTC-25150)](https://jira.eg.dk/browse/RTC-25150) Previously assigned store is excluded from possible dispatch locations. That means automatic reassign does not assign orders to a store from which they have been previously rejected. **Reassign order lines** ([RTC-23733)](https://jira.eg.dk/browse/RTC-23733) - Non-sale lines are not considered for removal when performing automatic reassign from the dummy store. - Normal automatic reassign doesn't handle picking orders owned by a fake store. - Removal of a line from dispatch order results in the line being removed from the previous picking order. - After removing the unavailable items when reassigning them, the order is successfully delivered. | | **Dispatch** **Service** | **Chain Web Capture ShippingCSID to improve nShift integration** ([RTC-24728)](https://jira.eg.dk/browse/RTC-24728) Chain Web now pulls data from DispatchService when picking order is finished with additional attribute shippingCSID. After finishing picking order, a new field called shippingCSID is created in the table, and the value is save in customerOrder.pickingOrder table. | | **Fresh food scale integration** | **Export to Myhrvold scales** ([RTC-24620)](https://jira.eg.dk/browse/RTC-24620) Item and price information (Labels) that are exported and sent to a blob are converted to Myhrvold format and put on a specified (configurable) folder. Every MyhrvoldXml file is named after StoreID, by which labels inside XML are grouped. **Fix: Export to Myhrvold** ([RTC-26255)](https://jira.eg.dk/browse/RTC-26255) Convert label to Myhrvold On-Premise job is correctly processed when there is no value in UnitPriceFactor field in the label. | | **Reason Codes** | **Reason Codes** ([RTC-20779)](https://jira.eg.dk/browse/RTC-20779) Removed possibility to edit reason codes in Chain Web user interface. | | **Receipt Journal** | **Receipt Journal Log - New data lines** ([RTC-23833)](https://jira.eg.dk/browse/RTC-23833) New data lines are available in receipt journal log: - cancellation of the receipt; - manually registered deposit; - scanned deposit refund; - currency in payments logs; - article discounts - contains type (percent/amount), reason of the discount and the amount that is subtracted from the price of the item. | | **Reports** | **Subscriptions** ([RTC-26043)](https://jira.eg.dk/browse/RTC-26043) Correction on bug that occurred when user select option "Upcoming week" and after that change default value in "Apply date filter to". Now subscription is properly created. **Sale per hour and cashier** ([RTC-25988)](https://jira.eg.dk/browse/RTC-25988) New report is optimized to use in cash register. Report shows graphic sales per hour and sales per cashier. See documentation in confluence: [0540_SalesPerHourAndCashier_std](https://confluence.eg.dk/display/RTC/List+of+reports#Listofreports-0540_SalesPerHourAndCashier_std). **Missing translation** ([RTC-25860)](https://jira.eg.dk/browse/RTC-25860) Added missing Swedish translations for subscription of report 0457. **Support for Liter15** ([RTC-25711)](https://jira.eg.dk/browse/RTC-25711) In report for Wet Stock and Daily Wet Stock support for new unit of measure, Liter15 was added. When dippings are registered in Liter15 this will be shown with and * on the day for the dipping. Changed reports: 0750_WetStock and 0751_DailyWetStock. **Subgroups sales** ([RTC-25486)](https://jira.eg.dk/browse/RTC-25486) Report 0611: sorting of item groups changed from alphanumeric to numeric. **New parameters in Top sales per item** ([RTC-25474)](https://jira.eg.dk/browse/RTC-25474) To do the follow up on item sales better, two new parameters are added to existing report 0459_TopSalesPerItem: - Brand - Filters result based on selected brand, - Campaign - Filters result based on selected campaign. | | **Shift balances** | **Not able to edit all settlements with status "Ready for balance"** ( [RTP-18165)](https://jira.eg.dk/browse/RTP-18165) It's possible to create balance for every shift settlement with status "Ready for balance". Correction on filtering of balances where user was not able to edit all settlements "Ready for balance" is done. | | **Users** | **Cashier** ([RTC-24978)](https://jira.eg.dk/browse/RTC-24978) Correction on error message when choosing default cashier role when creating new cashier. | --- ## Chain Web v. 2.10.185 > [!TIP] > Released 15th of November 2022 **Adjustments to the invoice layout standard V1 and V2** ([RTC-16646)](https://jira.eg.dk/browse/RTC-16646) Adding color and size to the Invoice based on transactions using POS Services/ POSLog processing. If there are both color and size given during Customer order creation, these properties will be displayed on Invoice just below item text. If color or size is given then only one value will be presented on Invoice. If none of the properties are given, then there is no extra line with information about color and size. --- ## Chain Web v. 2.10.184 > [!TIP] > Released 19th of October 2022 #### Improvements **Adjustments to the invoice standard** V3 ([RTC-26113](https://jira.eg.dk/browse/RTC-26113)) Remove Reference text and number fields from invoice header and place them into invoice grid to avoid loosing information during consolidate invoice generation. If there is no reference text/ number added to the order, this fields are invisible on the invoice. Additionally, Payment terms and Our references fields have been added in invoice header and text "Reference" before the date in grid has been removed. During testing the previous assumptions (task: [RTC-22650](https://jira.eg.dk/browse/RTC-22650)) related to logo size and margins also have been checked. **Translation correction** ([RTP-18999](https://jira.eg.dk/browse/RTP-18999)) ’Proper Swedish translations have been added for activity "Deposit refund" in Receipt journal logs. **Fix related to sign in for Azure AD user (EG Cloud user)** ([RTC-26754)](https://jira.eg.dk/browse/RTC-26754) Providing configuration in BackOffice.Web.ActiveDirectory/Web.config to avoid duplicated references regarding Microsoft.Owin version. After fixes Azure AD user can login properly into Chain Web. --- ## Chain Web v. 2.10.183 > [!TIP] > Released 07th of October 2022 #### **Improvements** **Refund and return** ([RTP-16124)](https://jira.eg.dk/browse/RTP-16124) Providing correct refund/return of discounted items from Customer order regarding Aera payments. **Subscriptions** ([RTC-26043)](https://jira.eg.dk/browse/RTC-26043) Correction on bug that occurred when user select option "Upcoming week" and after that change default value in "Apply date filter to". Now subscription is properly created. **Missing translation** ([RTC-25860)](https://jira.eg.dk/browse/RTC-25860) Added missing Swedish translations for subscription of report 0457. **Processing JSON files with POS Configration in FileService** ([RTP-18340)](https://jira.eg.dk/browse/RTP-18340) Support for importing POSConfigImport blobs from cloud to the on-premise Lindbak Retail database has been added to the BackOfficeImport package (GenericImport job). In order to process POSConfigImport blobs, a new POSConfigImportProcessor job has been added to the BackOfficeIntegrationSubscriber package. *Required:* *BackOfficeImport 1.3.4 or higher!* --- ## Chain Web v. 2.10.182 > [!TIP] > Released 16th of September 2022 ### Inventory on store without stock control ([RTC-22792)](https://jira.eg.dk/browse/RTC-22792) User will get the Item related information like UnitPrice, CostPrice, VatRate, Stock, Stock flag, even if the 'Inventory' flag is False in Chain Web or Chain Classic. Meaning the User can see all important values of the counted items during and after stocktaking. When 'Inventory' flag is set to False on the store: - Item related information will be fetched from Chain Classic via proxy or basis file. Basis file should contain only not stocked items. - 'Get stock level again for items in selected count list' should be visible if 'HideGetStockLevelCheckBox' configuration parameter is set to False. When 'Inventory' flag is set to True on the store: - No changes, works as before. > [!NOTE] > Breaking changes > > Chain Web changes needs to be delivered with Chain Classic changes in [(RTC-23050)](https://jira.eg.dk/browse/RTC-23050) Stocktaking: Create stocktaking basis for non "stock control" stores. ***Requires Chain Classic version 2.1.1.0.31!*** #### Improvement **Receipt Journal Log - New data lines** ([RTC-23833)](https://jira.eg.dk/browse/RTC-23833) New data lines are available in receipt journal log: - Cancellation of the receipt; - Manually registered deposit; - Scanned deposit refund; - Currency in payments logs; - Article discounts - contains type (percent/amount), reason of the discount and the amount that is subtracted from the price of the item. --- ## Chain Web v. 2.10.181 > [!TIP] > ## Released 9th of September 2022 #### Improvements **Dispatch order - Reassign order lines** ([RTC-23733)](https://jira.eg.dk/browse/RTC-23733) - Non-sale lines are not considered for removal when performing automatic reassign from the dummy store. - Normal automatic reassign doesn't handle picking orders owned by a fake store. - Removal of a line from dispatch order results in the line being removed from the previous picking order. - After removing the unavailable items when reassigning them, the order is successfully delivered. **New parameters in Top sales per item** ([RTC-25474)](https://jira.eg.dk/browse/RTC-25474) To do the follow up on item sales better, two new parameters are added to existing report 0459_TopSalesPerItem: - Brand - Filters result based on selected brand, - Campaign - Filters result based on selected campaign. **Processing JSON files with POS Configration in FileService** ([RTP-18340)](https://jira.eg.dk/browse/RTP-18340) Support for importing POSConfigImport blobs from cloud to the on-premise Lindbak Retail database has been added to the BackOfficeImport package (GenericImport job). In order to process POSConfigImport blobs, a new POSConfigImportProcessor job has been added to the BackOfficeIntegrationSubscriber package. *Required:* *BackOfficeImport 1.3.4 or higher!* --- ## Chain Web v. 2.10.180 > [!TIP] > Released 5th of September 2022 ### Create shipment using nShift ([RTC-18080)](https://jira.eg.dk/browse/RTC-18080) InStore App can create shipments using nShift and print shipping labels in the store. This is performed during the last steps of order picking if configured. In the settings page of InStore App, nShift settings needs to be added: ![](https://confluence.eg.dk/download/attachments/50075166/image2022-9-5_14-4-20.png?version=1&modificationDate=1662539110307&api=v2) New system parameter is created called "UseDispatchServiceForShipments ". If this parameter is set to True, "label format" dropdown is displayed (see image below). If set to false, label format will not be available. ![](https://confluence.eg.dk/download/attachments/50075166/image2022-9-5_14-5-48.png?version=1&modificationDate=1662539110330&api=v2) > [!NOTE] > *Note: The label format dropdown is only available for web orders with carrier option (e.g. home delivery). It will not be available for Pay&Collect or Click&Collect orders.* #### Improvements | | | | --- | --- | | **Credit note** | **Resend button is removed** ([RTC-24071)](https://jira.eg.dk/browse/RTC-24071) Resend option is not visible for credit notes, since it is not supported. | | **Customer management** | **Post code** ([RTC-23593)](https://jira.eg.dk/browse/RTC-23593) Correction on data values for post code sent from Chain Web to Chain Classic to avoid issues on customer and customer orders. After changes field for post code is given numeric value 0 whenever this field is blank or non numeric. | | **Customer order** | **Missing item lines** ([RTC-24465)](https://jira.eg.dk/browse/RTC-24465) Correction on invoice creation for consolidation invoice where invoices lines would appear missing on the PDF created. Issue was found between Customer order and Project where there was blank reference on both order and project. | | **Invoice** | **Correction on price calculation for invoice from internal transfers** ([RTC-24095)](https://jira.eg.dk/browse/RTC-24095) VAT is now properly added to the item price while sending internal transfer to credit. | | **POS Replication** | **Missing buttons in POS Replication dialog** ([RTP-17154)](https://jira.eg.dk/browse/RTP-17154) POS Replication dialog for acknowledging activation/deactivation of replication subscriber displays "Cancel" and "Confirm" buttons now. | | **Reports** | **Subgroup sales** ([RTC-25043)](https://jira.eg.dk/browse/RTC-25043) A copy of report 0610 is created with new parameters for selecting store and latest EOBD. Selection of latest EOBD makes it possible to set up subscription of report to get latest EOBD. **Sales statistics** ([RTC-25472)](https://jira.eg.dk/browse/RTC-25472) Changes made in the report for sales statistics (0752) to more efficiently report on stores and totals. Page 1 of the report is always total for all selected stores, next pages are per store. This is same behavior as in report 0714. New columns added to Gross profit section: % exc. campaign, campaign and campaign %. This is the same data as shown in report 0714. | | **System** | **Updating PIN for Cashier from Cloud User Management** ([RTC-25294)](https://jira.eg.dk/browse/RTC-25294) New user that is a cashier has PIN (the same value as CashierNumber). PIN doesn't change when user is updated or cashier is removed from user. If new user is not a cashier, then PIN stays NULL. | --- ## Chain Web v. 2.10.170 > [!TIP] > Released 15th of August 2022 #### **Improvement** | | | | --- | --- | | **BackOffice Integration Subscriber** | **Possibility to add and configure POS from JSON** ([RTC-18494)](https://jira.eg.dk/browse/RTC-10424) POSConfig job and POSConfigProcessor job have been implemented in the BackOffice Integration Subscriber package. These jobs allows to create new POS units and update configuration in the existing ones during POSConfig import from JSON file. | | **Customer Groups** | **Copy function in notifications** ([RTC-10424)](https://jira.eg.dk/browse/RTC-10424) Providing the possibility to copy the list of items that were not added during Import item list or Import item group list to customer group. This operation is possible by using the copy button on the notification. Copied item list can be pasted into text file. There is possibility to copy this list from popup about: - invalid unit of measure, - some items don't have a price for one more stores, - some items already have discounts for your store, - item groups already have discounts for your store. | | **Customer Order** | **Refund** ([RTC-24163)](https://jira.eg.dk/browse/RTC-24163) Prices on a customer order lines will be frozen at the time of customer order creation. Order lines will not be affected by any other discount than line, during the refund process. Only line discount will be added on the order after refund process. **Reference ID** ([RTC-23795)](https://jira.eg.dk/browse/RTC-23795) There is no need to fill field ReferenceId when the user has changed the delivery method on Customer order/ offer to one that has Custom type defined in system parameter CustomerOrderDeliveryMethod. Now field ReferenceId isn't mandatory for this setting and customer offer or order is properly created without it. | | **Invoice** | **Adjustments to the invoice standard V3** ([RTC-22650)](https://jira.eg.dk/browse/RTC-22650) Logo has 50px height and the width adapted to its' format. Section with customer details is placed below logo aligned with the invoice details on the right side. Margins are 20px. Reference text and number are moved to top section. When there is no reference text/ number added to the order, this fields are invisible on the invoice. Additionally, color and size are removed from receipt lines. **Subtotal rounding on Invoice** ([RTC-19153)](https://jira.eg.dk/browse/RTC-19153) Correction to how amount on receipt line is set to rounded value from POSLog which is adjusted to deal with rounding issues. Total amount on the invoice has been rounded correctly, regardless of the type of rounding up and down and kind of set discount (% or new amount). Additionally, rounding prices in the summary on Customer order has been fixed. | | **Inventory** | **Count lists** ([RTC-11439)](https://jira.eg.dk/browse/RTC-11439) When assigning count list fails, detailed exceptions are shown to the user and logged in BackOffice logs. | | **Order dispatch** | **Fix: All order lines is picked, but order is not completed, and picking order gets reassigned** ([RTC-22639)](https://jira.eg.dk/browse/RTC-22639) Automatic reassign of dispatch order (DispatchOrderReassign job) package does not create empty picking orders when no order lines can be reassigned. | | **Receipt journal** | **Correction on timeout when filtering by subtotal in Receipt journal** ([RTC-23506)](https://jira.eg.dk/browse/RTC-23506) Extension of existing index IX_MainIndex in table dbo.eljournaldetails in Lindbak POS Journal database by including column Amount that should improve searching receipts using filtering by subtotal. | | **Reports** | **Subscription options on Report 0457_CampaignStatistics** ([RTC-24237)](https://jira.eg.dk/browse/RTC-24237) Adding option "Upcoming week" in subscription when report 0457_CampaignStatistics is renamed. Providing support for Custom name on the report . Now renaming of the report 0457_CampaignStatistics doesn't make option "Upcoming week" unavailable. The report distribution follows defined time intervals and settings during subscriptions. | | **User management** | **Correction of bug in saving/editing User Roles** ([RTC-24343)](https://jira.eg.dk/browse/RTC-24343) Providing proper creation of a new user role and edition of the existing without error message. Occurrence of this bug is related to new version of web browser. | | **Web order** | **DispatchServiceRule parameter** ([RTP-17551)](https://jira.eg.dk/browse/RTP-17551) New DispatchServiceRule parameter has been implemented with the default value set to "WebOrdersFromPhysicalStores" under the filter CustomerOrder. | --- ## Chain Web v. 2.10.163 > [!TIP] > Released 30th of September 2022 **Customer - Discount** ([RTC-25643)](https://jira.eg.dk/browse/RTC-25643) Correction on visibility of customer discount when adding discount from Arts XML. After changes, the discount now shows on the customer card in Chain Web. --- ## Chain Web v. 2.10.162 > [!TIP] > Released 30th of August 2022 #### Improvements **Subscription options on Report 0457_CampaignStatistics** ([RTC-24237)](https://jira.eg.dk/browse/RTC-24237) Adding option "Upcoming week" in subscription when report 0457_CampaignStatistics is renamed. Providing support for Custom name on the report . Now renaming of the report 0457_CampaignStatistics doesn't make option "Upcoming week" unavailable. The report distribution follows defined time intervals and settings during subscriptions. **User maintenance of customer** ([RTC-24540)](https://jira.eg.dk/browse/RTC-24540) Correction on customer creation and edition while changing parameters: "Store Access" or "Customer Type". --- ## Chain Web v. 2.10.161 > [!TIP] > Released 8th of July 2022 **Correction of bug in saving/editing User Roles** ([RTC-24343)](https://jira.eg.dk/browse/RTC-24343) Providing proper creation of a new user role and edition of the existing without error message. Occurrence of this bug is related to new version of web browser. --- ## Chain Web v. 2.10.160 > [!TIP] > Released 5th of December 2022 ### Bonus rollout per store ([RTC-23230)](https://jira.eg.dk/browse/RTC-23230) In order to better follow up on bonus rollouts, a new report showing data from redeemed checks per store was created. ![](https://confluence.eg.dk/download/attachments/50075166/image2022-6-29_12-52-32.png?version=1&modificationDate=1657180854297&api=v2) | **Report details** **Bonus rollout per store** | | --- | | File name | 0088_BonusRolloutPerStore | | Data source | Analysis services (Cube) | | ***Selection*** | | | Year from | Default last year. | | Year to | Default current year. | | Bonus rollout name | Default all - shows available rollouts within period. | | Loyalty program | Loyalty program | | ***Columns -*** *One row per store with issued bonus checks for store.* | | Store | Store number - Store name. | | Number redeemed | Number of redeemed bonus checks for store. | | Sum redeemed | Sum of redeemed bonus checks for store. | | Redeemed of total issued % | Share of redeemed bonus checks for store compared to issued bonus checks for all stores. | | Average sale | Average sale for receipts with redeemed bonus checks for store. | ### Sales per item ([RTC-22944)](https://jira.eg.dk/browse/RTC-22944) A simple report showing sales per department/item group/item using Azure DW as a data source. ![](https://confluence.eg.dk/download/attachments/50075166/image2022-6-29_13-36-8.png?version=1&modificationDate=1657180854347&api=v2) | **Report details Sales per item** | | --- | | File name | 8024_ADW_SalesPerItem | | Data source | Azure Data Warehouse | | **Parameters:** | | Date from | Default today - 7 days | | Date to | Default today | | Store | Default all. | | Department | Default all. | | Item group | Default all. | | Expand to | Which level to default expand report to, default: Department. Default value can be changed with hidden parameter pExpandTo. | | Columns *(one row per department / item group / article with sum for each level)* | | EAN | EAN | | Item name | Item name. | | Amount | Amount sold. | | Quantity | Quantity sold. | | Net cost | Net cost. | | Gross profit | Gross profit (Sales ex. VAT - Net cost). | | Sales ex. VAT | Sales excluding VAT. | ### Import of users from Chain User Management ([RTC-18493)](https://jira.eg.dk/browse/RTC-18493) - When a user is created in User Management (Cloud, via UI or import of JSON contract), the user can sign in in Chain Web (OnPrem). - New roles are created in User Management (via UI or import of JSON contract), but without permissions - The user can see POS related functionality (e.g. Balance). It requires Balance permissions in role in BackOffice, but it does not require to set up a cashier. - Imported cashiers from User Management are flagged and have cashier store access - When a user in User Management has access to multiple teams/stores/profiles, Chain Web will set the first one from the list. - When a user in User Management has multiple store accesses (teams and /or stores and /or profiles), Chain Web will just set the first one (Profile -> Team -> Store). #### Improvements | | | | --- | --- | | **Customer Order** | **Refund** ([RTP-17652)](https://jira.eg.dk/browse/RTP-17652) During edition of order line with loyalty discount, only the difference between loyalty discount value and current value will be applied as line discount. This applies to all discount effects. **Refund/Return summary** ([RTC-23737)](https://jira.eg.dk/browse/RTC-23737) The total amount of the "Refund for customer" will have the same value as "Invoice total amount" of the credit invoice created during refund or return of items. | | **Dispatch Order** | **Re-dispatched orders are deleted from POS** ([RTP-16452)](https://jira.eg.dk/browse/RTP-16452) Orders that are re-dispatched to another store are correctly deleted in POS. **Shipping details in Dispatch order** ([RTC-18826)](https://jira.eg.dk/browse/RTC-18826) Tracking link in dispatch order can be used to see delivery progress. URL is linked to package number: ![](https://confluence.eg.dk/download/attachments/50075166/image2022-6-29_14-15-26.png?version=1&modificationDate=1657180854380&api=v2) | | **Gift card** | **Scrip Service** ([RTC-22747)](https://jira.eg.dk/browse/RTC-22747) When there is a difference between authorized and committed amount on gift-card, the committed amount will take priority when gift-card transaction is updated in the database. | | **Gift card Management** | **Turn on/off gift card module in chain web on-prem** ([RTC-11141)](https://jira.eg.dk/browse/RTC-11141) If system parameter "CloudChainURL" is set and the user enter Gift card view in Chain Web, the user will be moved to the gift card management in Chain Web Shell. This system parameter also affects gift cards in customer order details, when pressing the "eye" icon, the user will be moved to the details view of the gift card in Chain Web Shell. When the parameter is not set, functionality in Chain Web is not affected. The 'Gift Card Service Images' view has been deleted. | | **Project** | **Adding reference number and reference text to invoice related to fixed price project** ([RTC-21825)](https://jira.eg.dk/browse/RTC-21825) The invoice includes the reference number and the reference text on all layouts: a) If there is a fixed price project and flag fixed price on Customer order then Ref. nr and Ref. text are taken from the project. b) If there is fixed price project without flag fixed price and modified Ref. nr and Ref. text on Customer order then on in Invoice are modified values. c) If there is project without fixed price and modified Ref. nr and Ref. text then on Invoice there are modified values. *Summary:* *If user use Invoice plan, then Ref. text and Ref. nr are from fixed price project. In other cases, they use Ref. text and Ref. nr from Customer order.* | | **Receipt journal** | **Nordic characters in free search** ([RTC-23858)](https://jira.eg.dk/browse/RTC-23858) Providing the ability to enter characters specific to the Norwegian and Swedish alphabets from the keyboard in search field in Receipt Journal. Now there is possible both enter these special characters directly and copy paste them into the search field. User can enter any character in the search field, except for '-' which isn't allowed. Searching for words containing special characters works correctly. **Use LocalStoreNumber instead of StoreNumber to see receipts in Receipt Journal** ([RTC-23279)](https://jira.eg.dk/browse/RTC-23279) Accessing Receipt Journal in Chain Web results in showing the receipts based on LocalStoreNumber instead of StoreNumber from the store related to the user. **Visibility of columns Subtotal and Store is set by default** ([RTC-22070)](https://jira.eg.dk/browse/RTC-22070) These columns are always visible in Receipts journal after clearing cache. Visibility on these columns can be turned off temporarily, but after clearing cache they will be checked again. | | **Reports** | **Changes in Sale statistics to make it easier to follow up sale** ([RTC-23324)](https://jira.eg.dk/browse/RTC-23324) To make it easier to follow up on sales, two new parameters are added to report for Sale statistics. Changed report: 0013_SaleStatisticsWithDrill_std New parameters: - Include Nonsale (default: No) - if nonsale items should be included in report result. - Expand To (default: Area) - which hierarchy level to expand to when running report. It is still possible to manually drill down after running report. It is possible to change default value for both by changing hidden parameters pIncludeNonsale and pExpandTo. **Sale statistics** ([RTC-24082)](https://jira.eg.dk/browse/RTC-24082) Minor fix when when running report expanded to subgroup level. Fixed report: 0013_SaleStatisticsWithDrill_std. **Bonus rollout redeemed** ([RTC-23146)](https://jira.eg.dk/browse/RTC-23146) To better follow up bonus rollouts, two new columns are added to existing report 0086_BonusRolloutRedeemed: - Num of receipts - shows a number of receipts bonus check was redeemed in. - Average sale - shows an average sale of receipts bonus check was redeemed in. **Reporting v.76 is required to get data in new columns.** | | **Stocktaking** | **Reset stock value when counting** ([RTC-21754)](https://jira.eg.dk/browse/RTC-21754) User is able to reset stock level during finishing stocktaking operation, of the articles which were not counted, also for NotCountedSince and CycleCount stocktaking type. | | **Subscription** | **New subscription choice for report 0457** ([RTC-23194)](https://jira.eg.dk/browse/RTC-23194) When creating new subscription for report 0457, user can now choose to use report period "Upcoming week". Report period will follow same intervals and rules added to the subscription setup. | | **System** | **Updating cashiers in BackOffice** ([RTC-23801)](https://jira.eg.dk/browse/RTC-23801) Now cashier is correctly updated in BackOffice db; UserMerger is not aborted, there is no duplicate key row error. **BackOffice service** ([RTC-22491)](https://jira.eg.dk/browse/RTC-22491) Fixes an issue where BackOffice service could not contact cloud services due to old TLS version. | --- ## Chain Web v. 2.10.1591 > [!TIP] > Released 07th of September 2023 #### Improvements **Resend EHF** ([RTC-33534)](https://jira.eg.dk/browse/RTC-33534) Timeouts doesn't occur anymore on "Resend EHF" view. **False warning displayed in the invoice base** ([RTC-26036)](https://jira.eg.dk/browse/RTC-26036) Fixes eliminated false warnings in the invoice base about internal transfers not being sent to credit. After improvements, warning occurs only when in the selected store is at least one internal transfer which was not sent to credit. **Fix related to sign in for Azure AD user (EG Cloud user)** ([RTC-26754)](https://jira.eg.dk/browse/RTC-26754) Providing configuration in BackOffice.Web.ActiveDirectory/Web.config to avoid duplicated references regarding Microsoft.Owin version. After fixes Azure AD user can login properly into Chain Web. --- ## Chain Web v. 2.10.159 > [!TIP] > Released 1st of December 2022 #### Improvements **Adjustment in color and size display** ([RTC-23994)](https://jira.eg.dk/browse/RTC-23994) When color and/or size has value "-" or field is empty, then there is no extra line with information about color and size, for all templates after fixes. **Adjustments to the invoice standard V1 and V2** ([RTC-23994)](https://jira.eg.dk/browse/RTC-23994) Adding color and size to the Invoice based on transactions using POS Services/ POSLog processing. If there are both color and size given during Customer order creation, these properties will be displayed on Invoice just below item text. If color or size is given then only one value will be presented on Invoice. If none of the properties are given, then there is no extra line with information about color and size. **Filtering in exported Excel file from stocktaking** ([RTC-26853)](https://jira.eg.dk/browse/RTC-26853) After fixes the value of the parameter ServerSideExportBatchSize does not limit the number of rows taken into account during filtration. All rows in the Excel file can be filtered. --- ## Chain Web v. 2.10.158 > [!TIP] > Released 17th of August 2022 **Correction on price calculation for invoice from internal transfers** ([RTC-24095)](https://jira.eg.dk/browse/RTC-24095) VAT is now properly added to the item price while sending internal transfer to credit. --- ## Chain Web v. 2.10.157 > [!TIP] > Released 12th of August 2022 **Customer Order -** **Missing item lines** ([RTC-24465)](https://jira.eg.dk/browse/RTC-24465) Correction on invoice creation for consolidation invoice where invoices lines would appear missing on the PDF created. Issue was found between Customer order and Project where there was blank reference on both order and project. --- ## Chain Web v. 2.10.155 > [!TIP] > Released 22nd of June 2022 #### Improvements **Customer Order - Refund** ([RTC-24163)](https://jira.eg.dk/browse/RTC-24163) Prices on a customer order lines will be frozen at the time of customer order creation. Order lines will not be affected by any other discount than line, during the refund process. Only line discount will be added on the order after refund process. **Correction of bug in saving/editing User Roles** ([RTC-24343)](https://jira.eg.dk/browse/RTC-24343) Providing proper creation of a new user role and edition of the existing without error message. Occurrence of this bug is related to new version of web browser. --- ## Chain Web v. 2.10.153 > [!TIP] > Released 22nd of June 2022 #### Improvements **Refund** ([RTP-17652)](https://jira.eg.dk/browse/RTP-17652) During edition of order line with loyalty discount, only the difference between loyalty discount value and current value will be applied as line discount. This applies to all discount effects. **Refund/Return summary** ([RTC-23737)](https://jira.eg.dk/browse/RTC-23737) The total amount of the "Refund for customer" will have the same value as "Invoice total amount" of the credit invoice created during refund or return of items. **Nordic characters in free search** ([RTC-23858)](https://jira.eg.dk/browse/RTC-23858) Providing the ability to enter characters specific to the Norwegian and Swedish alphabets from the keyboard in search field in Receipt Journal. Now there is possible both enter these special characters directly and copy paste them into the search field. User can enter any character in the search field, except for '-' which isn't allowed. Searching for words containing special characters works correctly. --- ## Chain Web v. 2.10.152 > [!TIP] > Released 9th of June 2022 #### Improvements **Re-dispatched orders are deleted from POS** ([RTP-16452)](https://jira.eg.dk/browse/RTP-16452) Orders that are re-dispatched to another store are correctly deleted in POS. **The "to pay"(Å betale) line on partially paid invoices is not visible** ([RTC-18880)](https://jira.eg.dk/browse/RTC-18880) Label "To pay" is properly displayed on the partially paid invoices. **Adding reference number and reference text to invoice related to fixed price project** ([RTC-21825)](https://jira.eg.dk/browse/RTC-21825) The invoice includes the reference number and the reference text on all layouts: a) If there is a fixed price project and flag fixed price on Customer order then Ref. nr and Ref. text are taken from the project. b) If there is fixed price project without flag fixed price and modified Ref. nr and Ref. text on Customer order then on in Invoice are modified values. c) If there is project without fixed price and modified Ref. nr and Ref. text then on Invoice there are modified values. *Summary:* *If user use Invoice plan, then Ref. text and Ref. nr are from fixed price project. In other cases, they use Ref. text and Ref. nr from Customer order.* --- ## Chain Web v. 2.10.150 > [!TIP] > Released 11th of May 2022 #### Inventory ([RTC-21163)](https://jira.eg.dk/browse/RTC-21163) Checkboxes and dialog about unprocessed count list will not be displayed if the following System Parameters will be set to True: HideActivateCountListAutomaticallyCheckBox, HideUnprocessedCountListsModal, HideGetStockLevelCheckBox. If HideGetStockLevelCheckBox set to True, the 'Get stock level again for items in selected count lists' check box will be hidden in the following modals: - In overview tab in 'Count lists' grid when activating or putting on hold. - Count list tab when activating or putting on hold from sticky column and using 'Activate count lists' button in count list tab (with single or multiple selection). - Using 'Put on hold' or 'Activate' button in count list details view. #### Credit sales and payments ([RTC-22262)](https://jira.eg.dk/browse/RTC-22262) To get a better overview over drive-offs, a new report showing credit sales and payments on account was created. ![](https://confluence.eg.dk/download/attachments/50075166/image2022-5-6_8-7-9-.png?version=1&modificationDate=1652277367283&api=v2) | **Report details** **Credit sales with payments on account** | | --- | | File name | 0756_CreditSalesWithPaymentsOnAccount | | Data source | Database "Lindbak POS Reporting DW" | | ***Parameters*** | | | Date from | Showing transaction between and including *Date from* and *Date to* | | Date to | Showing transaction between and including *Date from* and *Date to.* | | Team | Filters stores within selected team. | | Retail store | Store selection. | | ***Columns -*** *One row per transaction group by store and customer; total for each store.* | | Date | Date of the transaction. | | Receipt | Receipt number of the transaction. | | [Ref.no](http://ref.no/) | Reference number of the credit tender transaction. | | Ref.text | Reference text of the credit tender transaction. | | Amount | Amount of the credit tender transaction. | | Tax amount | VAT amount from articles. | | On account | Payments when using payment on account function in POS. | #### Improvements | | | | --- | --- | | **Customer order** | **Return/Refund: show payment types** ([RTC-20626)](https://jira.eg.dk/browse/RTC-20626) User of return and refund views in Chain Web is displayed with the summary of payments returned on Gift Card or Klarna. **Web orders** ([RTC-19577)](https://jira.eg.dk/browse/RTC-19577) Web orders containing return lines are properly exported to the file service. | | **Dispatch orders** | **Oldest orders on top** ([RTC-22027)](https://jira.eg.dk/browse/RTC-22027) Oldest orders are on the top of Dispatch Orders list in Chain Web. | | **Dispatch service** | **History modal** ([RTC-21591)](https://jira.eg.dk/browse/RTC-21591) History modal in dispatch rule displays without any glitch. | | **POS Configuration** | **Too large printer logo size** ([RTP-16194)](https://jira.eg.dk/browse/RTP-16194) Printer logo does not get bigger now after storing logo in parameter PrinterLogo. **Hide parameter value in user interface** ([RTP-16123)](https://jira.eg.dk/browse/RTP-16123) Value for parameter "BridgeWSPassword" is now hidden in user interface in POS Configuration. It still possible to change the value, but the existing value is not shown. | | **Price rule** | **Mix 27 update** ([RTC-21636)](https://jira.eg.dk/browse/RTC-21636) Updated name and description for mix 27: *Name: Buy for X amount in ordinary price and get discount on all items.* Description: - Buy over a specified subtotal based on ordinary price, and get a % or amount discount on all items in the store. The subtotal will be calculated from the ordinary price of all the items in the receipt, including items that have a discounted price in the sale. The discount will compete with other offers for an item, and it might not trigger if another offer is better for the customer. It will therefore not give discount on items that already have other (better) discounts. | | **Receipt Journal** | **Allow a cashier in a store to see receipts for that store in Receipt Journal** ([RTC-21802)](https://jira.eg.dk/browse/RTC-21802) Log in as a POS cashier and accessing receipt journal in POS results in showing the receipts from store that cashier is logged into. | | **Reports** | **Campaign statistics** ([RTC-22634)](https://jira.eg.dk/browse/RTC-22634) In order to better follow up on existing campaigns, some improvements were made in the report for campaign statistics. Report: 0457_CampaigStatistics. Added selection for date filter with following options: - End date - only campaigns with end date within date selection is shown. - Start date - only campaigns with start date within date selectin is shown. - Ongoing - only campaigns which was active within date selection is shown. Default value for selection can be changed in parameter "pApplyDateFilterTo". Added "Not approved" in selection for status. Translations inside the report and Chain Web were also updated. **Turnover per item** ([RTC-22259)](https://jira.eg.dk/browse/RTC-22259) To better follow up sales per team, a new parameter for team is added to report 0753_SalesPerHourForArticle. **Top sales per item** ([RTC-22261)](https://jira.eg.dk/browse/RTC-22261) To better follow up on sales, it is possible to exclude certain item groups in report 0754_TopSalesPerItemWithCompareDate. Following parameter are added: - Exclude groups - if turned on (default off), the report will exclude sales from Excluded groups parameter. - Excluded groups - the parameter only shows up when Exclude groups in on. This is the list of article groups that should be excluded from report. Default selection is determined by hidden parameter "pExcludedGroupsList". Hidden parameters: - **pExcludedGroupsList** - Default value for Excluded groups; comma separated list of article group numbers. **Top sales per item** ([RTC-22260)](https://jira.eg.dk/browse/RTC-22260) To better follow up on items sales for all stores, a modified version of 0754_TopSalesPerItemWithCompareDate is created. The new version has an extra column showing store number and store name. The report sorts the result by store. Parameter for grouping is removed from this report. It is also possible to exclude certain item groups from the results. New parameters added for this: - Exclude groups - If turned on (default off), the report will exclude sales from Excluded groups parameter, - Excluded groups - The parameter only shows when Exclude groups in on. This is a list of article groups that should be excluded from report. Default selection is determined by hidden parameter "pExcludedGroupsList". Hidden parameters: - **pExcludedGroupsList** - Default value for Excluded groups; comma separated list of article group numbers. **Top sales per item** ([RTC-22255)](https://jira.eg.dk/browse/RTC-22255) To better follow up on sold packages for kilo items, existing report 0459 - Top sales per item is extended with column for number of sold item lines. New column "Sales quantity" shows number of sales lines for kilo items, and quantity for all other units of measure. Old column for quantity is renamed to "Sold [kg] [i]". This column shows quantity for all units of measure. **Report for sales and waste** ([RTC-21870)](https://jira.eg.dk/browse/RTC-21870) To make sure all breakages are included in report for sales and waste, the report uses FactItemTransaction now, which is based on RIGAL export as source. It will make sure breakages handled in Chain Classic are included in report. Changed report: 0458_SalesAndWaste. | | **Stocktaking** | **Count lists** ([RTC-21964)](https://jira.eg.dk/browse/RTC-21964) Fixed creating filter in counting group - not possible to create "empty" filters (without filter value). **Stock taking results** ([RTC-22298)](https://jira.eg.dk/browse/RTC-22298) The following fixes was introduced in Stocktaking result view: 1. The GetStocktakingResults method is not called on count group tab. 2. The GetDeviation method is called once on deviation tab. | | **System** | **LindbakRetailIntegration (SSIS packages)** ([RTC-21717)](https://jira.eg.dk/browse/RTC-21717) The CashierStaging package in LindbakRetailIntegration was extended with a new field: email. | | **User interface** | **Chain Web user interface - horizontal scroll bar** ([RTC-20803)](https://jira.eg.dk/browse/RTC-20803) Horizontal scroll bar will appear in the following grids: - "New Breakage" grid - "New Stock Adjustment" grid - "New Internal Use" grid - Parameters grid in POS Configuration - Active Configuration grid in POS Configuration | --- ## Chain Web v. 2.10.1491 > [!TIP] > Released 14th of June 2023 #### Improvements **Refund/ Return - fix for Not Paid status in dashboard** ([RTC-31261)](https://jira.eg.dk/browse/RTC-31261) The issue was only related to displaying Not Paid for completed orders on dashboard for the Orders where prices from order lines sum up to sum value with more than 2 decimals after comma. E.g. Total on order was 211,00 while lines sum up to 211,0002. **Client side error for store names with apostrophe (')** ([RTP-23002)](https://jira.eg.dk/browse/RTP-23002) Choosing stores with names that contain apostrophe (') in POS Configuration no longer causes a client side error to appear. --- ## Chain Web v. 2.10.149 > [!TIP] > Released 17th of April 2023 #### Improvements **Refund/Return process** ([RTP-19382)](https://jira.eg.dk/browse/RTP-19382) The order should not be blocked for further refunds/ returns, if the process will fail on e.g. timeout, or payment. The returned/ refunded lines will be removed from order, or set as deleted and the started transaction will be cancelled - removed. **Refund/Return process** ([RTC-29996)](https://jira.eg.dk/browse/RTC-29996) The same amount will be refunded to the customer as displayed during refund/ return process - as the total amount of the "Refund for customer" and as "Invoice total amount" of the credit invoice created during refund or return of items process. **Locking customer orders** ([RTC-28319)](https://jira.eg.dk/browse/RTC-28319) Fixes were implemented to eliminate locking order without proper reason with false message "The order cannot be changed since it is edited by another user". **Refund** ([RTC-24163)](https://jira.eg.dk/browse/RTC-24163) Prices on a customer order lines will be frozen at the time of customer order creation. Order lines will not be affected by any other discount than line, during the refund process. Only line discount will be added on the order after refund process. **Refund of order with loyalty discount** ([RTC-24100)](https://jira.eg.dk/browse/RTC-24100) During edition of order line with loyalty discount, only the difference between loyalty discount value and current value will be applied as line discount. This applies to all discount effects. **Refund/Return summary** ([RTC-23737)](https://jira.eg.dk/browse/RTC-23737) The total amount of the "Refund for customer" will have the same value as "Invoice total amount" of the credit invoice created during refund or return of items. **Return/Refund: show payment types** ([RTC-20626)](https://jira.eg.dk/browse/RTC-20626) User of return and refund views in Chain Web is displayed with the summary of payments returned on Gift Card or Klarna. --- ## Chain Web v. 2.10.148 > [!TIP] > Released 23rd of November 2022 #### Improvements **Count list activation** ([RTC-26413)](https://jira.eg.dk/browse/RTC-26413) The process of count list activation was improved, for Items Not Counted and Cycle stocktaking. Count list processing/ activation process should not be blocked anymore even if it's related to a default count group creation, or if the Items from related count list, already exist in stocktaking result with empty CountingGroupInStocktakingId. **BasisImport job** ([RTC-26498)](https://jira.eg.dk/browse/RTC-26498) The logs and processing of Basis was improved, so now more detailed error message - with the related line content will be thrown, if the processing of Basis file will fail and additionally the corrupted file will be moved to failedBasisFiles subfolder. Additional log message was added for CompletedWithNoEffect execution status. **Processing of basis files** ([RTC-27203)](https://jira.eg.dk/browse/RTC-27203) The processing of Basis files was improved, so now it is possible to setup additional scheduled trigger, which is independent of already existing directory content updated trigger. A new trigger should be started even if the standard trigger will be frozen. Additionally, the faulted basis file will be moved to subfolder with the date stamp, so there is no limit of how many files related to the same store could be moved + the retry mechanism was implemented to re-try the processing of not moved file 3 times. --- ## Chain Web v. 2.10.147 > [!TIP] > Released 21st of September 2022 #### Improvement **Correction of bug in saving/editing User Roles** ([RTC-24343)](https://jira.eg.dk/browse/RTC-24343) Providing proper creation of a new user role and edition of the existing without error message. Occurrence of this bug is related to new version of web browser. --- ## Chain Web v. 2.10.145 > [!TIP] > Released 23rd of June 2022 **Receipt journal - Nordic characters in free search** ([RTC-23858)](https://jira.eg.dk/browse/RTC-23858) Providing the ability to enter characters specific to the Norwegian and Swedish alphabets from the keyboard in search field in Receipt Journal. Now there is possible both enter these special characters directly and copy paste them into the search field. User can enter any character in the search field, except for '-' which isn't allowed. Searching for words containing special characters works correctly. --- ## Chain Web v. 2.10.144 > [!TIP] > Released 14th of June 2022 #### Improvements **Gift card - Scrip Service** ([RTC-22747)](https://jira.eg.dk/browse/RTC-22747) When there is a difference between authorized and committed amount on gift-card, the committed amount will take priority when gift-card transaction is updated in the database. **Reset stock value when counting** ([RTC-21754)](https://jira.eg.dk/browse/RTC-21754) User is able to reset stock level during finishing stocktaking operation, of the articles which were not counted, also for Not Counted Since and Cycle Count stocktaking type. --- ## Chain Web v. 2.10.142 > [!TIP] > Released 6th of May 2022 #### Improvements **Count lists** ([RTC-21964)](https://jira.eg.dk/browse/RTC-21964) Fixed creating filter in counting group - not possible to create "empty" filters (without filter value). **Chain Web user interface - horizontal scroll bar** ([RTC-20803)](https://jira.eg.dk/browse/RTC-20803) Horizontal scroll bar will appear in the following grids: - "New Breakage" grid - "New Stock Adjustment" grid - "New Internal Use" grid - Parameters grid in POS Configuration - Active Configuration grid in POS Configuration --- ## Chain Web v. 2.10.141 > [!TIP] > Released 25th of April 2022 ### Report for sales and waste ([RTC-20630)](https://jira.eg.dk/browse/RTC-20630) To more efficient keep track of sales and waste, the existing report was modified. ![](https://confluence.eg.dk/download/attachments/50075166/image2022-3-4_12-57-59.png?version=1&modificationDate=1646399572330&api=v2) | **Report details** **Sales and waste** | | --- | | File name | 0458_SalesandWaste | | Data source | Analysis services (Cube) | | ***Selections*** | ***Comment*** | | Date from | Default today. | | Date to | Default today. | | Retail store | Default all for HQ users. | | Article area | Default all. | | Article group | Default all. | | Reason code | Default all. Default can be changed in parameter pReasonCode. | | Grouping | If report should be grouped by article area or article group. Default is article area. | | Exclude items without breakage | If the report should show only items with breakage. Default no. | | **Columns -** *Showing one row per Article areas / Article group with drilldown to an item.* | | Items no | Item number | | Item name | Item name | | Sales quantity | Number of sold items within selection. | | Sales ex. VAT | Sales ex. VAT within selection. | | Waste qty | Number of breakages within selection. | | Lost amount | Amount for breakage within selection. | | Breakage % | Share of breakage quantity in relation to sales quantity, in percentage. | | Lost sales amount % | Share of lost amount in relation to sales ex. VAT, in percentage. | ### New report - Items not counted ([RTC-20845)](https://jira.eg.dk/browse/RTC-20845) A new report to follow up on stocktaking and items not counted is created. ![](https://confluence.eg.dk/download/attachments/50075166/image2022-3-25_10-42-55.png?version=1&modificationDate=1648201375943&api=v2) | **Report details Items not counted** | | --- | | File name | 0116_ItemsNotCounted | | Data source | Lindbak Retail database | | ***Selections*** | ***Comment*** | | Not counted since | Shows items that are not counted since this date. Default same date last month. | | Retail store | Only available for HQ users. Default first available store. | | Supplier | Filter result on supplier. Default all. | | Item group | Filter result on item group. Default all. | | Brand | Filter result on brand. Default all. | | Show total only | If selected it will only show total, not any items. Default not selected. | | **Columns** *(one row per item)* | | Supplier | Supplier name | | EAN | EAN number | | Item number | Item number | | Item text | Item text | | Last number in stock | Shows quantity from last stocktaking. | | Last netcost | Shows total net cost for item from last stocktaking. | ### New report: Top sales per item ([RTC-20438)](https://jira.eg.dk/browse/RTC-20438) To more effectively follow up on sales and report to both internal and external users, a new report showing sale on top x items is created. The report has lots of options for grouping and sorting of result. ![](https://confluence.eg.dk/download/attachments/50075166/image2022-3-4_13-50-4.png?version=1&modificationDate=1646399572297&api=v2) | **Report details Top sales per item** | | --- | | File name | 0459_TopSalesPerItem | | Data source | Database "Lindbak POS Reporting DW" and Analysis services (Cube) | | ***Selections -*** *result of report is narrowed down by selections:* | | Date from | Default today. | | Date to | Default today. | | Retail store | Default all (store users will only see their own store). | | Article area | Default all. | | Article group | Default all. | | Article subgroup | Default all. | | Article special group | Default all. | | Price channels | Default all. | | Vendor | Default all. | | Subvendor | Default all. | | Sort measure | Which column to sort the result on. Available options are Amount, Quantity, NetCost, Margin and Margin %. Default Amount. | | Grouping | How result is grouped. Available options are Store, Area, Group, SubGroup and No grouping. Default is Store. Default can be changed in parameter pGrouping. | | Count | How many rows (items) to show. Default is 9999. Default can be changed in parameter pCount. | | EAN list | To create EAN list to filter report on. | | Hide margin values | Turning this on will hide column Turnover, Gross profit and Gross profit %. Default off. Default value can be changed in parameter pHideMarginValues. | | Include VAT | If VAT is included in Turnover or not. Default Yes. Default value can be changed in parameter pIncludeVAT. | | **Columns -** *One row per item. Grouping by selection. After running the report, it is possible to sort on all columns.* | | Area | Article area | | Grp | Article group | | Sgr | Special group | | Item no | Item number | | EAN | Main EAN for item. | | Article info 1 | Labeltext1. When exporting to PDF, text is trimmed | | Article info 2 | Labeltext2. When exporting to PDF, text is trimmed | | Quantity | Quantity sold | | Turnover | Turnover (including or excluding VAT depending on selection) | | Gross profit | Gross profit | | Gross profit % | Gross profit in percentage | | Net cost | Net cost | ### Import of stores from Store Management ([RTC-11494)](https://jira.eg.dk/browse/RTC-11494) After creating or updating store in Store Management, inventory flag is imported to Chain Web's database and its correct value is shown in store details. #### Improvements | | | | --- | --- | | **Balance** | **Balance hangs** ([RTC-21333)](https://jira.eg.dk/browse/RTC-21333) Fixed problem when Chain Web "froze" when PDF with the balance result was auto printed. | | **Customer** | **The flag "Save Electronic Invoice Locally" description text was improved** [(RTC-21498)](https://jira.eg.dk/browse/RTC-21498) "Save Electronic Invoice Locally" label has been changed on "Save Electronic Invoice **only** Locally". | | **Customer order** | **Order line details** ([RTC-19586](https://jira.eg.dk/browse/RTC-19586)) A new field with the old name "Net cost" was added on the order line, it will show the profile net cost of the Item. The previous "Net cost" field was renamed to "Weighted average cost price" (Veid kostpris) with the existing summation, equal to the result of multiplying the Unit net cost by the Item quantity | | **Dispatch** | **Freight is not delivered when removing all lines from multiple picking order that contains freight** ([RTC-20858)](https://jira.eg.dk/browse/RTC-20858) In case of removing the item line from the not-delivered order, the freight item is reassigned to the delivered line with correct quantity delivered amount. | | **Internal transfer** | **VAT on internal invoices** ([RTC-21040)](https://jira.eg.dk/browse/RTC-21040) UseVATOnInternalTransferInvoice system parameter has been added with the default value False. It defines if VAT will be used in Internal transfer invoices. When value of parameter UseVATOnInternalTransferInvoice is equal to True and both stores in Internal Transfer have the same Organization Number, then VAT is included on invoice. | | **Invoices** | **Faulty/Incomplete IBAN number appears on invoice if the IBAN-field is empty in the Invoice setup** ([RTC-19581)](https://jira.eg.dk/browse/RTC-19581) When IBAN in store's configuration is empty, then it is not displayed on invoice. **Chain Web invoice layout: The "to pay"(Å betale) line on partially paid invoices is not visible** ([RTC-18880)](https://jira.eg.dk/browse/RTC-18880) Label "To pay" is properly displayed on the partially paid invoices. **Changes in invoice layout - round 2** ([RTC-17277)](https://jira.eg.dk/browse/RTC-17277) The invoice layout 'Standard V3' has been adjusted. Standard store information is stored in the footer, customer information is displayed only on the first page and the total amount is also displayed only once in the invoice summary on the last page. Date format has been changed to YYYY-MM-DD. Changes also affects Reminders when the store is using invoice layout 'Standard V3'. Invoice template types have been renamed: - Standard -> Standard V1; - StandardBlue -> Standard V2; - StandardNew -> Standard V3. | | **POS Configuration** | **Editing parameters on configuration group level** ([RTP-16068)](https://jira.eg.dk/browse/RTP-16068) Users without "Edit POS parameters common" role are not allowed to edit parameters on configuration group level. | | **Receipt journal** | **Receipt journal time stamp per entry** ([RTC-21136)](https://jira.eg.dk/browse/RTC-21136) The following improvements have been provided for the receipt logs view: - The total amount is displayed for each payment log. - If there is a few payments in the receipt, then each of them is named 'Part payment'. - Pant items are displayed once. - Failed payments are displayed properly as 'Failed payment' in receipt logs. - The proper quantities and amounts are displayed in line logs. **Receipts Journal** ([RTC-18408)](https://jira.eg.dk/browse/RTC-18408) No longer an option to enter special characters in free text search in Receipt Journal. Corresponding information regarding these limitations are added next to search label. | | **Reports** | **Bonus rollout redeemed vouchers** ([(RTC-21757)](https://jira.eg.dk/browse/RTC-21757) Small fix in report for bonus rollout. This will make x-axis not to show duplicate values. **Top sales per item** ([RTC-21277)](https://jira.eg.dk/browse/RTC-21277) In the report for top sales per item, some minor improvements / changes were made: - Minor changes in Swedish translation. - Name of selection for Swedish translation. - New column for supplier order number. ***NB! This column only shows if Reporting has version 74 or more.*** **Report loading** ([RTC-21345)](https://jira.eg.dk/browse/RTC-21345) To make report load properly with parameters, improvements are made in query for fetching teams. Improved reports: 0503_Nonsale_std 0754_TopSalesPerItemWithCompareDate **Account receivable** ([RTC-19461)](https://jira.eg.dk/browse/RTC-19461) In reports related to account receivable, there is a possibility to include team customers in selection and the result of reports. To include team customers, a new hidden parameter **pIncludeTeamStoreGroups** must be set to True (default False). Changed reports: 8000_InvoiceAging 8012_InvoiceAgingDetailed 8018_RunningBalance 8008_CustomerList 8014_CustomersWithoutSale **Report improvement** [(RTC-21511)](https://jira.eg.dk/browse/RTC-21511) In all reports containing selection on Team, the query for fetching teams has been improved. This will make reports faster to load when starting. Changed reports: 0041_BestSellerPerStorePerArticle 0044_SalesPerArticleGroupPerWeek 0047_SalesPerStorePerDay 0049_SalesPerStorePerMonth 0051_SalesPerStorePerWeek 0054_SalesIncVATPerStorePerDay 0055_SalesPerStorePerMonth 0071_SecurityStatistics 0100_WeekReport 0101_MonthReport 0103_TotalSales 0104_CustomerClubSales 0107_LoyaltyClubSales 0113_WeekReportNoEcommerce 0114_TotalSalesNoEcommerce 0132_TopXArticlesperHour 0151_CustomerClubSales 0205_ArticleStatistics 0206_SalesStatistics 0250_NumberOfNewMembersPerStore 0308_CustomerClubSales 0502_TotalTurnover_std 0504_KeyFigures_std 0505_DepartmentSales_std 0506_SalesReport_std 0507_OperatorSettlement_std 0508_WorkstationSettlement_std 0509_SaleStatistics_std 0517_DashboardCashregister_std 0602_ArticleGroupSales 0603_SalesPerHour 0604_SalesAndWastePerArticle 0605_SalesAndWastePerArticleFromRIGAL 0705_TurnoverPerDayWithPriceChannel 0752_SalesStatistics 0800_TopXArticlesSold 0801_CustomerFrequence 0802_SalesPerArticleGroup 0803_SalesPerAssortment 0804_DashBoard 0810_LoyaltyClubSales 0903_LoyaltyClubSales_DW | | **Stocktaking** | **Stocktaking result** ([RTC-21423)](https://jira.eg.dk/browse/RTC-21423) Correct related data will be shown in stocktaking result view, no matter if MultipleLoyaltyPrograms system parameter will be set to False or True. **Stocktaking: Item (tandem) that has status 'isDeletedInChain = 1' appears in count list** ([RTC-18759)](https://jira.eg.dk/browse/RTC-18759) For ModelItemsProcessingType Simple and Full has been added new condition isDeletedInChain = 0 while adding missing items to the count list. All model items (color-model items for ModelItemsProcessingType = Simple) with isDeletedInChain =1 are not added to the count list in the processing process. **Export of stocktaking related Count groups and Stocktaking result to Excel/ PDF** ([RTC-18653)](https://jira.eg.dk/browse/RTC-18653) The Excel file with the results exported from Count groups tab will contain the scope of this tab instead of Stocktaking results. The export to Excel/ PDF of Stocktaking results of not completed Count group has been additionally fixed. **Export to PDF in active stocktaking fails for stocktaking type "non-counted items"** ([RTC-18652)](https://jira.eg.dk/browse/RTC-18652) When there is no data to export (to Excel or PDF), the warning is displayed that 'Grid contains any items.' and the files are not generated. | | **User management** | **Receipt journal in POS** ([RTC-16647)](https://jira.eg.dk/browse/RTC-16647) Cashiers with password not synced with user password is now able to also use receipt journal in POS. |