Fix for: Performance of the item information API is bad (RTC-44602)

Item information API (/api/gateway/Item/GetItemsByItemIdentifiers) performance has been significantly improved.  

Shelf area and type register (RTC-42201)
A Shelf register has been added to the registers view in which, there are Shelf area and Shelf type tabs. Access to these registers is filtered via view and manage registers permission.  A user with the appropriate permissions can add, edit, or delete data in those the registers.  They contain a code and a name. Both registers support country specific names. The list of languages, for which data can be provided, is taken from the system parameters. When adding a new value or editing an existing one, user must fill in the name field for all supported languages, as they are mandatory. It is not possible to edit the code field.

While adding and editing, the field for name is displayed for each supported language. Meanwhile the grid shows the name for one of them, which belongs to the country set as default in the country register. If there is no value for the default language, a value for another currently available one is randomly selected and displayed in the register to prevent an empty field. Shelf area and shelf type used by any shelf location are not removable, user will be informed about it by a message.

Fix: New retail price does not trigger price suggestion for a profile (RTC-43727)

The price suggestion for the profile is not created if only the retail price or both the retail and wholesale prices are changed. Only importing different wholesale price will trigger creating price suggestion on profile level. After mass approving rows in price control, they disappear from grid and are not showing up again, unless new wholealse price will be imported.

Fix for: Store user cannot change profile price in price control (RTC-43600)

A user with store role and "Approve prices" permission can view and approve/reject price suggestions for the level (profile or store) that they have access to.

If a user has access only to a specific store, they will not be able to view/approve price suggestions for the profile. The "Store group level" dropdown is already preselected for that user.

System parameter for Pricer plaza (RTC-43637)

Authentication to the Pricer system has been changed from logging in via username and password to an API key. The field for placing the api key is called “Pricer API key”,  the field on the URL to which the key will link to retrieve the authorization token is “Authorization URL”. In the field “Url for pricer plaza the link of the Pricer system” must be placed to which labels will be sent. In order for the labels to be correctly sent to the Pricer system, all fields must be completed with correct data.

Image Added

Fix: Not empty product features cause validation errors (RTC-44579)

Importing RIGAL file, which contains text field with Product Features, results in data being assigned to current default language set in system. 

Item is not activated when importing with SupplierPrices ruleset (RTC-42939)

When inactive item is imported with SupplierPrices ruleset, it is rejected in import and has a warning 'Item is inactive'. Rejection is performed as automatically set status to 'Rejected' of the import row after validation is completed. This status is by default hidden in the import details. No changes included in rejected import are made to the item.

In situation that only inactive items are imported in one import, it is automatically marked as 'done' and all rows are 'rejected', but if some of the imported items are active, they will be by default visible and can be imported.

Dictionaries serialization (RTC-43234)

After updating the library, JSON displays values "language code" : "text in language" correctly in Swagger of Item Service.

Image Added

External changes field (RTC-44246)

A new attribute "External changes" has been added to the "Details" page in the "Change history" section. It shows how many times that item has been updated in master data system.
This attribute will be visible to the user only, if the item has any value. The value for "External changes" can be imported and exported via 3rd party (JSON).

Best before flag in Item details (RTC-42976)

There is new item attribute - flag "Best before" which is visible in the Item details, in Food section. By default it has value 'False', but if existing item had value in 'Shelf life', flag is marked as 'True'. "Best before" flag can be a store local attribute and is added in store local values tab.

Image Added

Flag can be imported (from 3rd party and Excel) and exported (to Excel and 3rd party) both as common and store local value. 

Scale labels - Myhrvold and Strongpoint are now tracking "Best before" flag. It's value is exported along with other scales data in Item.Label.Export. If on item store local value for "Best before", it is taken into account for that specific store.

Item hierarchy names in multiple languages (RTC-34204)

The item hierarchy attribute names are displayed for supported languages in the Details page, of each hierarchy attribute. User can add and edit item hierarchy names for supported languages using the edit modal. At least one name is required.

In exported Excel file, sub columns based on the supported languages are displayed. All hierarchy attributes are exported with names for all supported languages. If there is no name, the field in the Excel file will remain empty.

User can also add or update names for all supported languages via import. If the imported file Excel/JSON does not have names for all supported languages, a name for the default language is created automatically, as at least one name is required.

Fix: Inactive profiles are visible in store group dropdown (RTC-42908)

When profile does not have any stores, it is marked in Item Service as Disabled. That means that when all stores are moved to new profile, old one is deactivated and is not visible in any dropdown in Item Management. Profile can be also deactivated manually by clicking 'Deactivate' in Store Management, but only if it contains  inactive stores.

Item search API (RTC-42123)

Contract for item search API is available on Swagger. It allows to search items by certain criteria, presented in schema.

Image Added

View item sales (RTC-43313)

A user with the reporting permissions can see the "View sales statistic" button in the Overview tab of an item. When clicked, user is taken to the dashboard where sales as shown for that specific item.

Fix for: Create new price if only difference is recommended retail price (RTC-39389)

The imported value of the recommended retail price is correctly entered into the price. A new price is also created when the only difference between it and the currently existing price is the recommended retail price. If there is no value for the recommended retail price in the imported file, it will be set to the same value as the retail price.

Support mixes ( RTC-42369)

Mixes (5.21/22,23,10/13/39,28,101) are supported by item service and their mix details are saved in the db as a json column. Components that previously used promotion price (labels, store price grid) still only use the promotion price and not other mixes. 

Shelf location (RTC-42702)

Shelf location register is exported to blob in JSON format file. Contract to export shelf location has been added to swagger and is called Item.ShelfLocation.Export.  It is possible to manually trigger the export in the Export view.

Image Added

Fix: User can edit values with only view rights (RTC-43133)

User with manage item permission can edit, delete allergens and nutrition using "Edit allergens" and " Edit nutrition" buttons. For user with viewer item only permissions, the buttons are not visible. He can only see the allergens and nutrition data, but cannot edit them.

Fix for: Brand category cannot be added (RTC-43458)

Brand category added manually through the user interface is saved correctly. 
Additionally, a bug related to refreshing the register after deactivating and activating values has also been fixed. After performing the mentioned actions, the register is refreshed to show the correct values.

Fix: New wholesale price triggers franchise price suggestion (RTC-43664)

In situation that on item there is store price with the same or different retail price as on profile, changes in wholesale price of profile price will not trigger creating price suggestions for store. If on item there was no store price, change in profile's wholesale price will trigger creating price suggestions for store (if item is in active assortment of store). 

Additionally, when entering price control grid, side panel is expanded by default. 

Fix: Exporting price doesn't work when there is deleted price (RTC-43504)

When triggering export of item or all prices, exported blobs contain correct active prices. If on item was a 'newer' price which was deleted, both previous active price and deleted price with correct statuses are exported.

Export items to Excel (RTC-35918)

It is possible to export items and prices to an excel file from the store price grid. Only items that have a price are exported, because filtering is done in the store price grid, so all items visible in the grid will be ready for export. Export is limited by view prices permission to access the store price grid and Export items from item grid permission to access the export. Store price grid should be filtered by Ordinary price, if it is not, then user will be notified by a warning on the export details page. Export is still possible. 

When clicking Export in Excel, user is redirected to view when they need to select relevant attributes for export. Store groups are not predefined, user needs to select them in this view.

Fix: Weight declaration dissapears when saving (RTC-43387)

When user edits or adds the weight declaration in the details tab via user interface, Excel import or JSON import, the information is correctly displayed for the product after the entire product is saved.

Import item hierarchy (RTC-39929)

It is possible to import the full item hierarchy using a JSON file. The contract is called Item.ItemHierarchy.Import and is visible in Swagger. During the import, it is possible to create new parts of item hierarchy, update them, and change the hierarchy structure.
Name is an optional field, it can be imported in different languages, including those that do not belong to the system countries. If a name is not specified in the import, it will be set as default, i.e. the name of the item hierarchy part and the imported number. Assigning an active part of the item hierarchy to an inactive parent will result in the activation of all parents to which the child has been assigned. 

Image Added

Export label to Pricer (Plaza) ESL (RTC-43058)

Main SupplierNumber is exported to the Pricer system and is visible in the properties.supplierNumber field.

Remove loading screen (RTC-38423)

When exporting items from grids with many items, loading screen is omitted and user is taken immediately to export view, where he can select desired columns. At the top of the view, there is an indicator of counting items, which is changed to number of exported items, after the counting is finished. Views affected are: item grid, specific item list (both export of items and prices) and details of store assortment. 

Image Added

Quantity on GTIN (RTC-40490)

In the manage GTIN view, a field and a quantity column have been added to record the quantity of a given GTIN. When manually adding a GTIN in the UI, the quantity field is required, and pre-filled as a default value of 1, which can be edited.  The numerical value accepted in this field is integers, positive, greater than 0. A new "GTINs" section has been added to the Item.Item contract, where main GTIN and alternative GTIN are exported and imported, along with their status and quantity. When importing a GTIN together with a quantity, it is saved and visible in the UI; the absence of a quantity field during import means that a default value of 1 will be assumed. Existing GTINs after release will be set to the default value of 1. Using the Status field during import, a given GTIN can be deactivated or activated. It is not possible to deactivate the main GTIN, and the user will find out through a validation error, and the inability to import. 

Fix: Label processor performance (RTC-43202)

Performance of LabelProcessor job is improved.

Fix: Not possible to create price because of currency error (RTC-42907)

When creating prices on different store groups, currencies of prices (both supplier currency and currency of store group) are correctly displayed. When switching store groups or currencies from dropdowns, values are correctly set and calculation of a price can be done with no errors.

Fix: Incorrect date for rejected suggestions (RTC-42311)

There is renamed column 'valid from' in Price suggestion history grid to 'valid from of approved price'. This new column contains date and time of approving price suggestion (both for franchise stores and profiles). For rejected price suggestions, this column is empty and exact date of rejecting suggestion is placed in column 'created date'. By default this column is first on the left in history grid.  
Image Added

Fix: Price suggestions for past prices (RTC-32970)

Price Sggestion Processor job was extended with new method to delete out of date price suggestions both franchise and wholesale price suggestions. For each item, store group and date (from the future) there is only one active and visible in the grid price suggestion. 

Following rules are used to maintain clarity of the grid:

1. When there is existing profile price suggestion, but new active price with retail price is received, price suggestion is removed.
2. When there is existing profile price syggestion, but new active price with wholesale price is received, price suggestion is updated to current data.
3. Expired price suggestions, when newer price suggestion is created, are removed.
4. Price suggestions for future prices are created for every item, store group and valid from (including time) combination, but when time changes and they are expired, they are removed.

System parameters for languages used in Item Management (RTC-42833)

In system parameters view, there is section 'supported languages' which displays chosen languages for which localized texts will be supported. Parameter is editable and user can select languages from dropdown containing list of ISO standard language codes and names of languages. Names of languages are not translated. There needs to be at least one supported language selected. 

First release of feature will set languages connected to system countries in the parameter.

Image Added

Fix: Excel export performance - filtering in item grid (RTC-42715)

There is no timeout when exporting filtered items from items grid.

Fix: 'Select All' button doesn't work (RTC-41764)

When creating new or editing existing item group list, it is possible to use button 'select all' and 'unselect all'. If grid is not filtered on anything, clicking on button to select all groups will result in a message displayed, that the range is too big and asking to filter grid on some column. 

Fix: Importing item and its deposit item at the same time (RTC-36678)

The item and the deposit item linked to it can be imported in one file even if the deposit item does not yet exist. A placeholder for the corresponding GTIN is then created. The placeholder has all required fields filled in, ItemText,ReceiptText and LabelText1 are the same and contain the text “Item” and the imported GTIN, other fields such as VatCode,Supplier,SalesUnit are copied from the item to which the deposit item created as a placeholder was linked. 
During the import, the user is informed about the creation of a placeholder for the item through a corresponding validation warning.

Fix for: Add validation in import for unique item identifiers (RTC-38146)

Importing an identifier such as ProductId or ExternalItemNo assigned to another item or duplicated inside the file does not cause an error on the entire import and lip job, but it is found at the validation/import stage. The user is informed about everything via Validation Errors containing information about the inability to import for a specific reason. 

Fix: Remove fuzzy search from some fields in item search (RTC-41101)

Fixed an issue related to item search when trying to search for an item by GTIN and TandemGtin. Searching for items through these identifiers will result in finding one particular item.

New item trigger reason (RTC-41590)

Label created as first for item, store and label type combination has assigned trigger reason 'New item'. That means that activating item in store assortment triggers creating label (if item has correctly configured price and label type). 

Image Added

Fix: Change 'Add to label printing' to 'Add to label list' (RTC-41108)

View 'Ordered labels' was renamed to 'Label lists' and contains both lists coming from the InStore App and lists created by adding labels manually. When user prints labels from item details or item lists manually, button that is visible for him is called 'Add to label list'. User is able to decide whether new list should be created or labels should be added to one of existing lists. It is only possible to manually add labels to lists created manually (not from the InStore App). In the dropdown with lists to choose to add labels to, names of the lists are shown as 'Created by - created date' to differentiate them.

When adding labels from item lists, then if some of the items do not have prices or are not active in store assortment for specified store, labels for these items are not added to label list. 

Similarly, if label of item added via API to the label list, does not have price or is not in active assortment, when printing label list, there will be warning with exact number of labels that will be printed.

Image Added   Image Added

Fix: Removing item from store assortment creates price suggestion (RTC-42262)

When item is removed from store assortment price suggestion is not created for this item - store pair. Additionally existing active and future store price suggestions are removed, to make it impossible to mistakenly accept old price suggestion and make item available again.

Fix: Wrong value of unit type assigned to item in RIGAL import (RTC-42443)

When importing sales unit or unit type on item, value imported (code of unit) is linked to language. In result unit is correctly set on item, even when there is no texts for specific language and in import there is code from the same unit but different language.

Important note: If different units have the same codes (but set for different languages), importing such code will assign first of the units from database.

Hide Break Bulk option (RTC-37749)

Break bulk flag (visible in item details) is visible in user interface only for Customer Unit items, as it was hidden for TU items. In import (both Item.Item and Excel ) for TU items this flag is ignored and when sending flag with value TRUE, there is a warning message displayed in import grid. 

Existing items are not changed, but if break bulk flag is imported for TU item with flag set to TRUE, no matter what the imported value is, it will be changed to FALSE.

Fix for: Create new item based on existing alternative GTIN (RTC-41738)

GTin that has been removed is treated as a new one and the new item can use it during creation. 

Fix: Show that currency was updated (RTC-41052)

When making any changes to currency register (adding rates, changing markup), 'modified date' and 'modified by' columns in currency register view are correctly updated. When doing that manually in the UI or via JSON import, there is visible e-mail of a person doing the updates. If currencies were updated via DNB API, in 'modified by' there will be visible name 'system'.

Image Added

Fix for: GenericExport shouldn't export the same data (RTC-40519)

Interrupting the GenericExport job does not re-export the data from the beginning. Export will resume from the point at which the job is interrupted.

Fix: Import of stop sale and reason code on item (RTC-41558)

Stop sale flag and reason code can be imported on item level. Item.Item contract has field 'stopSaleReasonCode', by sending NULL, flag stop sale is automatically set to false, otherwise if there is value sent, flag is set to true. There is an error when field for reason code is an empty string and file cannot be imported. Excel import works similarly, with only difference that there can be stop sale flag field in the file, but it is not relevant, as reson code value always overrides it and can be imported by itself.

Set item (RTC-41786)

When item has more than 1 limit control group assigned, additional text 'SET ITEM'  is displayed in limit control group section in item details.

Fix for: Excel export performance - filtering in item grid (RTC-42641)

Items are exported to excel faster. Performance is better and the FileExport job is completed correctly, with no timeout when exporting items after filtering. 

Fix: Side panel not collapsing when accepting last price suggestion (RTC-42358)

When price suggestion is accepted or rejected in price control view, side panel is refreshed to next, lower row. In a situation that accepted suggestion is last one visible in grid, side panel will be refreshed to the new last row.
If acecpted suggestion is only one visible in the grid, side panel will collapse. 

Add 'Discount' as a value to presentation (RTC-42203)

When item has active promotion price, presentation property in Pricer has value 'DISCOUNT'. In other situations - no promotion price, planned promotion or stopped promotion presentation value is 'NORMAL'.

System parameters for Pricer Plaza (RTC-41904)

It is possible to set url, login and password to Pricer Plaza as system parameters in user interface. In system parameters view, there is new section "Pricer plaza", where users, who have permissions to manage these parameters can input values for pricer integration. When flag to use pricer is not checked, new parameters are not visible in user interface, they are shown only when flag is marked.

Password is not visible, it is always displayed as stars, both when in view and in edit mode. Once the field for password is clicked in edit mode, the password needs to be filled again before saving. Values are correctly saved in database.

Image Added

Fix: Accepting price suggestion does not update price (RTC-42326)

Acepting price suggestions for both profiles and franchise stores, results in creating price with values like in price suggestion. Works for accepting without making any changes to suggestion, as well as acception suggestion with some values changed.

Image Added

Fix: Create new vat rate with decimal values (RTC-42312)

It is possible to create new vat rates, for new and existing vat codes, with decimal values in vat registers. Whole and decimal values should be separated by dot. Vat codes with decimal vat rates can be assigned to items, used to calculate price and exported in Gateway.ItemChanges and Gateway.ItemPrice. 

Fix: Price control bugs  (RTC-40054)

When switching between store group levels and store groups within one level, side panel is refreshed and shows data for new row in focus. Side panel is also refreshed to the next row, when price suggestion is accepted or rejected. In a situation, that last in view suggestion was approved/ rejected, side panel collapses. When approving profile price suggestions without any changes made to them, they are saved in price suggestion history with status 'Approved'.

Price suggestions on store level are created only if new price on higher level store group has different retail price value. Changes in only wholesale price, net cost or vat do not trigger creating new franchise store suggestions.

Swagger documentation (RTC-41815)

Swagger documentation for Item Service has been updated with steps that customer must take during integration process, common issues section and how to solve them. Obsolete parts of documentation were removed.

Fix: Export to excel after full text search (RTC-40742)

Items searched during full text search are correctly exported to excel. Selecting single rows in the import details view is correct and subsequent actions are applied only to the selected rows.

Fix: Update package with contract (RTC-41950)

When promotions with offer groups and offer items are submitted, they are imported to Item Management with no errors and StagingBatchExecutor finishes with status Completed.

Fix for: Angular 16 - item selection during import (RTC-42037)

Items can be selected and imported separately.

Fix: Cannot import on item different label types with the same code (RTC-41107)

Scale labels with the same code and store number can be imported on item via Excel and JSON import, as well as set manually in item details. There is new format of file, where in Excel column 'Scale' is divided into 2 subcolumns if there are Myhrvold and Strongpoint scales added in the system. In a sitaution, that there is only one scale label type defined, there is only one subcolumn exported as well as needed in import. If there are no sclae labels in system, field is not exported in Excel export. JSON Item.Item contract was extended, in 'storeLocalAttributes' entity, in 'scales' , there was added field 'labelType', which must be present in file for scales to be correctly imported.

Fix for: Angular 16 - item selection during import  (RTC-42037)

Items can be selected and imported separately.

Assortment planning (RTC-41004)

Code is not editable in all registers in which it appears.

Fix: error in printing labels when item is not in assortment (RTC-41053)

Correct error message is shown in "Print labels" modal.  When item has no price - "Selected item has no price in selected store" is shown. In case when item is not in store's active assortment - "The selected item is not in active assortment for the selected store" is displayed.

Shelf label 3 (RTC-39526)

The new label type "ShelfLabel3" has been added to the registry and can be assigned to a store and to all stores. 
The label is printed so it is visible in the label printing grid. Fields visible on the label are also tracked and changing them triggers creating new label. These fields are: LabelText1, LabelText2, Price, Supplier item number, Quantity in supplier package, GTIN, Unit type and sales amount. The barcode is generated based on the supplier item number field. When the specified value has less than six characters, this will be filled with 0 inserted before the number.
The labels are printed on an A4 sheet of paper in two columns of 10 labels, so there will be 20 labels on each page.

Update to Angular 16 (RTC-14937)

Item management has been updated to framework version Angular 16.

Fix: Full export of items include store prices (RTC-40669)

When export of item is manually triggered from the item grid, item, all active prices, item-store links and store local values are exported. Even when item has more than 500 prices, all of them are exported in one GenericExport execution.

Edit wholesale price before import (RTC-38976)

When user sends a file with price (via excel, JSON or RIGAL import) it is possible to edit value of imported wholesale price and wholesale price in supplier currency (depending on type of import). In import view, when hovering over specific row, there is visible 'edit' button, when clicked edit modal is displayed and on the bottom of the modal there are added fields with current wholesale price and wholesale price from file. Wholesale price from file value is editable and after making changes and saving them, import is revalidated. New fields in modal (current wholesale price, wholesale price and prices in supplier currency) are visible only if they exist. Prices in supplier currency and displayed with correct currencies.

Item import improvement (RTC-41752)

A file with incorrect Size = null data does not cause a null reference exception in staging.

Fix: Missing store links when job timeouts (RTC-38476)

There is new job BackgrundWorkers, which is responsible for adding missing item-store links. When system parameter Store assortment management is disabled, item store links are automatically added whenever new store is added to profile / price zone on which there are existing prices on items. This happens when new store is added, existing store is activated or moved to different higher level store group. When there ar no missing store links job finishes with status CompletedWithNoEffect. If something would interrupt execution of the job (LIP restart, timeout) next execution will resume from the place it was interrupted and rest of item-store links will be added.

When store has some item-store links and is moved to a different store group, new item-store links are added and none removed.

Fix: Change tracking for labels (RTC-40012)

Labels are created when there is a change in the values of the fields on them. New labels are not generated when change tracking is changed.

Export label to Pricer (Plaza) ESL (RTC-39376)

Pricer1 type labels are exported to the Pricer electronic shelf label system.
Integration with the system is accomplished by setting three newly added parameters in the item service database. These parameters are: 'Pricer1Login', 'Pricer1Password' and 'Pricer1Url'.  All parameters must be configured correctly, otherwise the Label Export job will be terminated with a status of CompletedWithWarning and a message that the configuration for Pricer is missing. The labels are then not exported, and each subsequent execution of the job will end with the above status until the configuration is added correctly. The store number existing in the Pricer system must be added in the ExternalStoreNumber of our cloud system. Creating a label for a store that does not exist in the Pricer system will result in, no export, the job will end up with a status of CompletedWithWarning and a message that the store is not configured. Each subsequent execution of the job will be the same until the appropriate changes are made to the store. The fields visible on the label are: 'SKU','LabelText1','Sales price (without decimal)','GTIN','SupplierItemNo','LabelText2','Promotion price','UnitPriceUnit','Quantity in supplier package','Unit price factror','SalesUnit','Ecological flag','Deposit item','Country of origin'.
Changing the values of these fields will create a new label, only the deposit item retail price amount is not tracked, but changing the deposit item will trigger a new label.

Fix: Wrong sorting when printing labels (RTC-40705)

Labels in label printing grid are grouped by item group and supplier, store and within those groups they are sorted by itemid.  Same sorting is applied when labels are printed from label printing grid, then label type and store must be the same and labels on items with same group and supplier are grouped.  

Fix: When label type is added for 'all stores' it is not returned in API for store with no label types specified (RTC-41449)

Label types assigned for 'all stores' in label type registers, mean that they are available for all the stores, which do not have any other label type assigned directly on store. When requesting label types via API and spescifing a store, in situation that store does not have any label types added, there will be returned all label types assigned for 'all stores'. If store has at least one label type specified, only those will be returned.

Fix: Delete items (RTC-40944)

The DeleteItems procedure deletes the item correctly, even if there are multiple related tables.

Fix: Import aborted when getting promotion with ExternalPromotionNo = null (RTC-41441)

The ExternalPromotionNo field is nullable in the ItemService database, and promotions are processed correctly during import.

Fix: Remove creating store links when store is updated (RTC-41216)

when store is added, moved to different profile or activated, item store links for items that have prices in this profile are not added. Updating stores or higher level groups, which results in stores being imported to Item Management ends with jobs with 'completed' status.

StrongPoint scale (RTC-34782)

A new type of scales called Strongpoint has been added. It is managed in the Scales register and can be added in the item details as a scale to the store. When adding scales to an item, the label type for available scales is also visible. Strongpoint scales are exported to Label.Export whenever there is a change in one of the attributes such as: GTIN, Item group, Scale label, Price, Promotion price, Sales unit, Shelf life, Tare, Weight declaration, Origin. When Strongpoint scales is removed from an Item, a label with a deleted status is created and exported.  Store local values if they exist are used when creating labels for StrongPoint. The uniqueness of values in the Scales register has been changed so that store/code/labeltype must be unique.

Fix for: ShelfLabel2 small and small without price (RTC-40951)

Label text on ShelfLabel2 small and ShelfLabel2 small without price is correctly matched to the field size. Text is not wrapped over other fields, and does not intersect other values.

Price suggestion (RTC-40285)

Price suggestion are not created at the profile level when the price was created in the UI, in order for the suggested price to be created profile price must be created using import.  Suggested prices for franchise stores that are in the profile are created regardless of how the initial price was created.

Re-export item, price and item-store link (RTC-37104)

Export of items, prices, item store links and store local values can be manually triggered from the item grid by clicking "..." on the left side of the item and selecting "Export item". This option is visible to users with permission Access to system tasks and information in the System group.

Fix: Server error when sending request when item has item planning attributes for mutiple storegroups (RTC-40962)

In request's response, there are returned only item plannings attributes which are not connected to any storegroup. This means that when there is sent request for item with more item plannings, response is sent correctly.

Fix: Resolving date when updating sales price (RTC-40142)

When there is existing price created with today's date and sales price is imported with valid from date in the past, new price is created with wholesale price from existing price and imported sales price. Same happens when there are two separate files sent, one with wholesale price and second with sales price both with valid from date created in the past - new price valid from today will be created with imported values.

Fix: Error when selecting store in many modals (RTC-40953)

In label type register view, when adding label type on store level, there is displayed dropdown with only active stores and there is no console error. Same for 'edit active assortment' modal in store assortment view, 'print labels' modal from item lists. Also it is possible to select only active stores in export to excel in store local values field, with no console errors. 

Orderability details API (RTC-39809)

New fields were added to orderability details for item response from request. For scanned item TU or CU, at the end of contract are now placed supplier sales start and end date and flag 'ordering blocked' from procurment section from item details. For trading unit items connected to scanned customer unit item as well as for customer unit connected to scanned trading unit item, same fields were added in specified sections in contract.

Shelf label 2 price location and font (RTC-40157)

Price on shelf label 2 labels is always justified to right side. Fields such as 'item number', 'supplier number', 'supplier item number', 'date' and 'assortment code' as well as text 'jmfr pris' have bigger font and are well visible on label. 

Limit control groups assigned on item (RTC-39064)

There is new section in item details - Limit control group, where are visible limit control groups added on item. Only top 5 added groups are visible, rest can be accessed by entering view ' Mange control group'. There groups can be added, edited and deleted from an item. First group added on an item via UI has prefilled Content item name with 'item text'. An item can have same limit group assigned multiple times. When an item is a model item, then when adding limit groups, user can specify for which items from the model he wants to assign the group.

All changes - adding, editing, removing groups, is triggering Gateway.ItemChanges export, where correct data on assigned limit groups is located. 

Allow to override vat code (RTC-40915)

When creating price via Item.ItemPrice.Import, it is possible to specify vat code in file. Price will then be created with imported vat code and vat code set on item will not be used, but will remain on item. If in the file, there is no vat code specified, then price will be created with vat code from item. Prices are exported to Gateway.ItemPrice with correct codes (those used for calculation) and their rates. Creating price via UI allows to create price only with vat code from item.

Ordered labels user interface (RTC-33047)

Quantity of labels has been added to the contract, database and is visible in the user interface. Clicking the label type while in the ordered labels view takes user to a new view where the user can see the items for which labels are listed. The default visible columns are Quantity of labels, GTIN, Item number, Item name, Color, and Size while other columns such as Supplier name, Supplier number, Supplier model number, External model number, Model number, SKU, and Brand are hidden. Item name inside the ordered labels list is a link and takes the user to the item. The number of copies of a given label equals the quantity written next to the item. The order as well as the number of labels is as they were scanned. The user cannot select a single label to print, and clicking the Print labels button in the lower right corner of the view prints the entire list. The order of labels and their number cannot be changed manually. 

Fix: Do not show inactive stores in dropdown when creating new values (RTC-39876)

When user creates new order points on item, in dropdown with possible stores to choose, there are visible only active stores. Same changes were made to dropdown when adding label types on item, in label printing modal and when adding new set of store local values on item.  Activating inactive store results in it being visible in the dropdowns.

Pricer labels (RTC-39371)

Label type Pricer1 with API type has been added. It is visible in the Label registry and can be assigned to an item in item details. It is a type prepared for export so it is not visible in the label printing grid. The label is created automatically when an item is assigned this label type and the following fields are changed:  MainGTIN, item name, price, externalItemNo, supplierName (the case where editing supplier does not create a label, you then need a change at the item level to make the new label contain the correct data), promotionPrice, unitPriceFactor, quantityInPackage, unit, unitPriceUnit, countryOfOrigin. 

GTIN visible on labels when assortment is U (RTC-40567)

When item has assortment code equal to 'U', then on EkoMaxi and EkoMini labels, GTIN is visible, no barcode is printed, and rest of the label stays the same. When assortment code is changed to another one, then barcode is printed on label. 

Import limit control register (RTC-39097)

The documentation on importing data into the LimitControlGroup registry is improved and includes the fields required for import, along with an example. 
It is possible to import data into the LimitControlGroup registry using a json file and the newly added blob type Item.ControlGroup.Import is responsible for this. If there are no values for the imported group in the system then it will be created, if they exist then it will be updated. Values for limits that are not in the imported file will be deleted when they exist.

Extend RIGAL import with new fields (RTC-39016)

New fields are supported to be imported via RIGAL import to item Management. On 108th place, it is possible to write 'sub-supplier number'. If number does not exist in database, new supplier will be created and added on item. Similarly 'manufacturer number' on 60th place. Flag 'healthy' can be imported on 75th place in file and 'J' means the flag will be set on item to True and 'N' to False. It is also possible to import 'exclude from price control' flag, but in this case 'J' means flag is set to False and 'N' to True.

Fix: Do not allow unit price factor to be 0 (RTC-40316)

When importing files (Excel or JSON imports) with unit price factor equal to 0, there is a validation error about importing only one of unit price unit and unit price factor values.

Fix: sales price cannot be updated without wholesale price currency (RTC-39962)

When there is active price on item and user imports file with only retail price column for the same storegroup, in newly created price wholesale price is copied from active and retail price is value from file in storegroup currency.

Item import (RTC-39930

New items can be created by importing json and excel when there is a value for the item sub-group field in the file and there is no item group value. After importing, the item will be assigned the correct item group, which is the parent of the imported sub-group.

Fix for: Timeouts when using "contains" filter in Store Price grid (RTC-38836)

There is no timeouts when user filter with contains option.

Currency rate per store group (RTC-38162)

It is possible to set currency rates per store group. In UI there are three new columns in registers - currency view, 'store group level', 'store group code' and 'store group name'. When creating currency, by clicking on 'New currency rate' button, user  can choose for which level to create currency rate for: country or store group. If store group is chosen, then more fields are shown and user can select level and group. Those fields are prefilled with default values. Currency per store group has a group name visible in breadcrumbs and  country, level and name of store group are shown in details. There is no flag 'Main' on the currency, as currency per store group cannot be main currency per country. For all currency rates, under details, there is button to 'edit currency' where default sales markup can be edited and flag 'Main' for currencies per country.

When currency rates are exported to 3rd party, hierarchy is taken into account and 'lowest' level currency rates are exported, what means that if currencies for all store groups and country are defined, currency rates for store are exported. 

Currency rates per store group can be also updated via JSON import Item.CurrencyRate.Import, where store group level and group identifier are needed.

 When creating prices on items, if for selected store group exists currency rate per store group, cost rate is used from this currency, otherwise cost rate per country. If in store group selector are store groups with different cost rates, there is shown error at the bottom of the page.

Ensure color/size is unique within a model (RTC-38843)

It is not possible to create a model that has different items with the same size/color within it. When importing new or already existing item, for which duplicate exist within model, they are merged and main GTIN is GTIN of imported item. For models, for which duplicates already exist, importing single or all duplicated items also results in merging them into one.

Fix for:  Add missing GTIN to database (RTC-40617)

GTINS that are missing are added to the db in item.Gtin table 

Scales not removed during import (RTC-39040)

Scales assigned on item can be removed by importing 'NULL' value in scales column in excel import. As they are a part of store local attributes, column with store number is required in the file and all scales for specified store are then deleted from an item. In JSON Item.Item import, similar effect can be achieved by sending empty array in 'storeLocalValues' 'scales' field.

Flag to delete only future prices (RTC-39597)

In JSON conract Item.ItemPrice.Import, there is new flag to choose in status field - DeleteAllFuture. When importing price with this status, all planned prices for specified in file store group, with valid from date equal or later from date in file, will be deleted. If a file contains valid from date in the past/ empty, it will be treated as today's date and all planned prices will be deleted.

SupplierPrice import file type (RTC-39182)

File type supplier price has been added, it can be used to import the price by matching item by supplier and supplier item no. For it to be imported ApprovalRulset must be set to "SupplierPrice".
Lookup by supplierItemNo has the highest priority of all lookups. If a lookup by item is done by SupplierIdentifier and supplierItemNo, but cannot be found, an item is looked up by GTIN. A useOnlyForLookup flag has been added to the ItemSuppliers section of the contract and the corresponding flag causes the supplier/supplierItemNo not to be or to be updatable.  In this type of import, it is not possible to create new items, so the user will be informed of this with a validation error message during import. 

Import of attributes related to duty-free and grocery (RTC-39596)

Attributes 'Duty free', 'Sealing bag', 'Restricted', 'Origin' and 'Weight control' are visible in item details, and are exported and imported by both JSON and Excel files. Origin and weight control can be defined as store local vallues.

Fix: Missing item attributes - fix for store local values (RTC-40376)

Importing Weigh control and Origin values as store local values does not edit the default value at the item level.

Removing barcode for items being phased out (RTC-39419)

The barcode is not generated for EkoMaxi and EkoMini labels when the currently active assortment code is "U".  Changing the assortment code causes the barcode to reappear on these labels.

Fix for: Timeouts when fetching labels (RTC-40104)

Preparing labels for printing from an item list is faster and does not end in a timeout. 

Limit control groups (RTC-38758)

By creating limit control group user can set limits (minimum and maximum) of substance/ goods for two different types of customers - crew and passenger. Groups can be created via add panel which is placed above the grid. They must have unique codes and required values are code, name and unit of measure. Limits can be set in add panel or added later when editing group. Unit of measure is a dropdown list with hardcoded units. Groups can be deleted and deleted code can be reused when creating new group. All changes made to registers trigger export to 3rd party (JSON).

DnB API (RTC-39502)

Currency rates fetched from DnB API are divided by unit provided by API response.

Export of items matched by tandem GTIN (RTC-38225)

When user tries to find and export item using tandem GTIN in filters, export to excel view is opened with correct count of items and after choosing fields, item is correctly exported. It works from items grid and item lists.

Re-export item, price and item-store link (RTC-36401)

Item prices, store-link, and store override are not exported for an item that is deactivated or deleted. Exported prices are active or future prices, expired prices are skipped when exporting to blob. Re-activating an item automatically trigger export prices, item-store links, and store local values (ItemStoreOverride). If a store was added to the profile while the item was deactivated, after reactivation the newly added store will be included in the export of item-store links to the blob.

Wholesale price suggestions are created for items with 'exclude from price control' flag (RTC-39077)

Even if item is marked as 'Exclude from price control', then after wholesale price changes, price suggestion should be created on profile level. In case of franchise stores, there won't be price suggestion created, when wholesale price is changed.

Import from DnB API (RTC-39877)

Currency rates are fetched only for system countries set in country register and only for those supported by DnB API. The fetched currency rates are saved only these currencies, that are set as default country currencies.

New label types (RTC-36802)

"Shelf Label 2", "Shelf Label 2 small" and "Shelf Label 2 small without price" label types are available for use in Item Management. Labels can be generated manually from item details, or when added to label type of specific item, they are triggered by changes in tracked attributes of specific label type.

On Shelf Label 2 label there are visible label text, supplier number, supplier item number, external item number (which is also used to generate barcode), date of changes on label, price, assortment code and compare price, which if is equal to zero (no UnitPriceFactor and UnitPriceUnit) is not displayed. Layout for printing on horizontal sheet is 4 columns of labels and maximum 8 rows on single sheet.

On Shelf Label 2 small label there are visible label text, price and external item number (which is used to generate  barcode).  They are printed on stickers. 

Shelf Label 2 small without prices label looks the same as Shelf Label 2 small, but is without price. 

For each label type, if there is no external item number, barcode is empty. Label text is displayed in dynamic font, which is adjusted to length of the text. If price has no decimal value, it is displayed with no ore. In case there is any decimal value in price, always two decimal places are shown.

There is also new system parameter, which if set for other number than 0, will not allow to automatically create labels (triggered by changes on tracked attributes) if item has not been in stock of a store for more than set number of days.

Fix: Timeout when printing labels (RTC-39181)

Timeout does not occur when a large number of labels are printed or exported.

Missing and changed translations (RTC-38592)

Missing and incorrect translations occurring in Item Management UI were corrected. Changes can be noticed in manage order point view, system parameters, export to excel view, menu and item deactivation modal.

Clean-up and update of documentation (RTC-39382

API documentation is updated.

Assortment codes per profile display limited by permissions (RTC-37758)

When system parameter 'assortment per profile' is set to true, profiles shown in Assortment per profile section are filtered by users view and manage store local attributes permissions. User with no view or manage permissions does not see fields related to assortment codes in item details and if he exports item to Excel, cells are not divided by profiles and are empty. User with only view permissions set on profile level, can see assortment codes per profile he has access to in item details and in exported Excel files. He does not see 'manage assortment' button. To be able to see and use the button, user has to have 'manage' permissions per profile level. This user can also update assortment codes via Excel import.

User with permissions per store level, can only view assortment codes per profile, which contains this store. 

Manage assortment button works differently for different amount of accessible profiles - for 5 or less profiles, it opens a modal to update assortment codes and for more, new view with assortment is opened.

Fetching currency rates from DnB (RTC-36012)

Currencies, which are default currencies for system countries and are in set of (NOK, SEK, DKK, EUR, GBP) quote currencies, are automatically updated everyday by integration with DnB API. If there are any changes made to base default currency (country stops being system country, currency is no longer default etc.), currency rates will not be fetched with new execution of the job for this currency.

Currency rates fetched form DNB API are saved in database as base values, that means that if currency has default markup, different than 0, then active sales currencies will be correctly calculated based on both values. 

It is possible to update fetched currency rate manually and via import, and manually created rates will be updated by new execution of job.

In logs of the new job, it is visible which base currencies were fetched and if DnB API returned null values for some of exchange currencies. 

Performance of receiving list item and item segmentation (RTC-38845)

New API methods that allow getting the identifiers of the item in list and segmentation has been added and they are visible in Swagger:  /api/gateway/ItemLists/{id}/itemIdentifiers and  /api/gateway/ItemSegmentations/{id}/itemIdentifier.  Existing requests are deprecated, however, they still work and return correct data.  New methods run faster and their performance is higher than existing ones. The performance of getting the first and last page in item list/segmentation is very similar.

Filtering in Price control grid (RTC-38233)

There is a panel for filtering in price control. The panel can be hidden and made visible. It shows two fields, Store group level, where the user can select at which level he wants to filter, and Store/Profile field where the user selects the value he is interested in. After selecting which, the grid will show prices suitable for filtering. Only profiles/stores for which there is any price suggestion can be selected. The ability to select a store/profile is dependent on the access the user has, and for a user with access to a single store, the filter panel is invisible. The profile/store selection initial value is set with the first profile/store(depending on user access) which has any suggestions. The above changes include both Price control grid and also Price control history grid.

Fuel and Freight item types (RTC-39315)

Item types - Fuel and Freight are available in the item type register. It is possible to assign them manually and via import (both Excel and API, item.item contract). Items with these values are exported to Excel or 3rd party in JSON contract.

Turkey as system country (RTC-38816)

Turkey can be selected as one of the system countries. Currency, vat code and unit can be created for Turkey. It is possible to save item text in a language for Turkey, as well as to import and export it in Excel and JSON.

New framework for user interface (RTC-14938)

Promotion management is upgraded to framework versions Angular 16 and Kendo 12.

LIP job Label Processor performance (RTC-20085)

Label Processor job performance has been significantly improved. Labels are created faster and the whole process of change tracking takes less time. Setting up new stores by adding a label type to the item for them does not cause a linear drop in performance, and here the biggest performance improvement is noticeable, which shortened the job execution by almost 10 times.

Export of assortment codes (RTC-38524)

Assortment codes registers can be exported to 3rd party in json Item.AssortmentCode.Export contract. Export of particular register is processed, when any change to it is done. Adding new register also results in blob with information on it exported. Export maintenance view was extended with the new blob type and export can be triggered also from there. 

Fix: Supplier import contact person can not be null (RTC-39221)

Supplier can be imported into the registry using an excel file when there is no Contact Person column or when it has no value. 
It is impossible to import a null there and remove the existing value, this will cause an error on the initial validation and the file will not be imported.

Fix: wrong sales rate with markup when creating new currency (RTC-38607)

When creating new currency, it is required to create active cost, sales rate and default markup for sales rate. Created rates are calculated correctly based on input or imported values. Currency rate value is limited to only four decimals (cost rate, sales rate and adjusted sales rate). Correct active rates are visible in user interface. 

Extend contract (RTC-38542)

Contract to import currency rates - Item.CurrencyRate.Import was extended by fields related to store group. These fields include store group type, in other words level, name, code and externa reference. It is possible to import rates per store group, but it is optional and contract can be sent without those fields. 

Contract and db model (RTC-38268)

New tables for controlling limits have been added to the database, their names are: LimitControl.ControlGroup, LimitControl.ControlGroupList, LimitControl.CustomerType, LimitControl.ItemControlGroup.

Contract for limit group registers is published in Swagger.

Contract for importing and exporting items (JSON) has been expanded to include limit group attributes and is published in Swagger.

Fix: Stop sale with reason code as store local value (RTC-39212)

Stop Sale Reason Code belongs to store local values. It is imported and exported via both JSON and Excel.
The stop sale reason code field appears only when the stop sale flag is checked and is required to stop the sale.
Removing the stop sale flag removes the reason code. Stop Sale Reason Code is also required during import, and if it is not there the user gets a validation error message and the changes are not imported.

Fix: GLN, Lead and Transportations time being deleted when not included in import (RTC-38134)

In import of suppliers, when importing only certain columns in excel file, values not imported (from missing columns and empty fields) stay as they were before import. Import of value NULL results in removing value from field on supplier. 

Import of item groups (RTC-38300)

All item groups are imported from Item Service to Promotion database (extended functionality of StagingMerger job).

Import of currency rates (RTC-37234)

There is a new import type Item.CurrencyRate.Import in which 3rd party can import currency rates. It is possible to update active rates, create, edit and delete future rates. In imported file it is necessary to include base currency, exchange rates and currency code for currency rates that will be created. If country is not included it means it refers to all countries for which specified currency is a base one. Valid from date for currency rates is optional, but if it is not in file or is null, it will be taken as 'today'. When the file has a start date that is in the past, the rates are only updated if there is no rate with a newer or today's start date. To update rate, which was created 'today',  there needs to be correct valid from date. It is possible to send new default markup and markups for specific currency sales rates.

 Fix: Item type, report category and classification names are exported on item (RTC-37564)

The contract to export Item.Changes has been extended to include a name field when exporting ItemType. The reportCategoryNo and itemClassificationNo fields are marked as obsolete, and new ReportCategory and ItemClassification fields containing code and name are added in their place. Data can also be imported in the newly added fields.

Store local items & local suppliers (RTC-34662)

'Manage by store' flag is renamed to 'Local item' in item details, item grid and active assortment view. It is possible to filter by Local item column in these grids to see store local items. Entrance to supplier register is extracted to menu and it is visible when user has manage local items permission. Flag 'Local supplier' is added to the supplier register, exports to Excel and JSON are extended by this field. User with manage local items permission can see and export all of the existing suppliers but can create and edit only local ones. Local supplier flag can be edited by HQ user, so it is impossible for user with only manage local items permission to edit this flag and change status of the supplier.

Fix: editing item group via user interface (RTC-37510)

It is possible to edit item hierarchy elements in UI. To change parent hierarchy of an element, user has to  select new group from dropdown. Departments dropdown contains all active departments, area dropdown contains all active areas which are a part of selected department and so on. If higher level parent group filed is cleared, then lower level dropdown contains all active groups. 

Filter on past dates (RTC-38050)

In label printing view, in ' valid from' column, it is possible to filter on past date. All existing options for filter are working (i.e 'is equal to', 'is before' etc.). When selecting filter 'is equal to' only labels created on that particular date are shown. Filtering works also combined with filters on other columns. In a situation that there on different dates, there were added labels to label printing which were not printed, filtering only on newest date will show label. 

Items excluded from price control (RTC-34265)

There is a new flag added on item, named 'Exclude from price control'. If it is set to TRUE, for this item price suggestions for franchise stores and for retail price for profiles are not created. Flag value is by default false and already existing items were assigned this value. Flag can be exported (both excel and Gateway.ItemChanges) and imported (mass update and JSON contract). 

Store prices grid (RTC-37640)

The offer name column has been added to the store prices grid. By default, it is hidden. Offer name in this column is a hyperlink to the promotion offer where the item currently has a price. Price for pair store-item is created one at a time, no matter how many suppliers an item has assigned to it. The value in the Valid from column is a hyperlink and when clicked brings the user to the store price. When filtering by status, the valid prices are displayed. If a price has been deleted, such as by sending the isDeleted flag, it also disappears from the store prices grid.

Export performance (RTC-36702)

The excel file are exported in parallel, performance is improved. 

Translations fixes (RTC-38485)

Fields 'Consumer sales start', 'Consumer sales end', 'Supplier sales start' and 'Supplier sales end' are correctly translated to Norwegian and Swedish language.

Labels (RTC-33689)

Store local values are used when creating labels if there is a value for the store. Otherwise, the default value of the item is used as before. This applies to printed labels as well as those for export.

Fix: Approval import problem (deadlocks) (RTC-38304)

Approval Import job is not executed with status faulted because of database deadlocks. 

Currency import (RTC-37653)

A contract with the blob name Item.CurrencyRate.Import, used to import currency rates into item management has been created and is visible in swagger.

Fix for: Maintain order of processing imports (RTC-38415)

The order of imported files is maintained after timeout on ApprovalImport job.

Fix: StagingBatchExecutor aborted during timeout RTC-38464)

StagingBatchExecutor job unable to execute correctly due to a timeout, ends with the status faulted, and the next execution repeats the attempt to execute correctly.

Pack out flag (RTC-27935)

Bundle type field is removed from Item details and from the item exports. "Pack out items in sale" flag is added to item details, it is visible and can be checked only when an item has a bundle content.  Flag can be exported and imported via Excel and JSON. Validation error in import user interface occurs when the flag (pack out item) is set to have value on an item that is not a bundle. 

Supplier on item (RTC-36661)

The storeGroupReference section that contains the 'externalNo' and 'type' fields is included in the supplier information and is exported to the ItemChanges blob type along with the rest of the item information.

Fix: Export all items from grid without any filters (RTC-35081)

Export to Excel is much faster. Job FileExport is triggered by service bus message, so files are exported or at least processing of export, is started almost immediately after clicking button to export. 

All items from item grid can be exported to Excel and there is no timeout. 

Naming of colums related to countries/languages is changed in exported files. Even if there is only default language exported, there is visible country/language code in header and in hidden row. Importing items with columns without country codes will not update values.

Fix: Export of prices, where store group type is not taken into account (RTC-35081)

When exporting prices for specific store group level and reference, correct prices are exported. 

Fix: Export items that are not in active assortment (RTC-37407)

When exporting items with store local values and choosing to export 'Active assortment' flag, all selected items should be exported no matter if item is or not in active assortment of a store. This is true for all stores included in the 'include store local values - stores' or f not selecting any stores, then for all store user has permission to view store local attributes for. Value of the field can be TRUE or FALSE for specific stores and empty only for common value.

Fix: Rename ExternalNo in item supplier attributes (RTC-37827)

ExternalNo field is renamed to Reference in item supplier attributes section in ItemChanges export blob type.

Fix: Error in import of price with value 0 when there is active price on item (RTC-32651)

When there is existing price on item, created with price calculation rule which includes defined values for handling costs, supplier discount etc, importing prices equal to 0 does not result in error in import. Importing only wholesale price will affect wholesale and net price (as it is calculated based on wholesale), but retail price will be taken from previously existing price. Importing price and additional price calculation elelements , will create price based on values included in file. If in previously existing price, there are other defined values, which are not imported in file, their percentage value will be taken from this price. 

In import of first price, there should included be all price calculation elelements. If they are not included, their values will be set as values from default calculation setup currently set on environment. In case that price calculation has no values set for certain elements, their value will be 0 by default.

Fix: Retry when timeout for approval import (RTC-37829)

When during import, there is a timeout in ApprovalImport job execution that finishes with status 'Faulted' and not imported items have status 'Ready For Import' . Next executions of job, till there is no more timeout, will be processing rows from imports that were not imported. 

Fix: Do not allow to manually print labels for items not active in assortment (RTC-36619)

Labels can be printed only if for stores in which items are active in. There are 3 new error messages shown in Print Labels modal, first shown when user wants to print label from item details and for selected store, item is not in active assortment. Other two are shown when printing from item lists. One show count of items that are not in active assortment. User can still print out rest of the labels. Other error message is shown when none of the items is in active assortment, in such case buttons to print labels are grayed-out and it is impossible to click them.

Fix: Update of wholesale prices does not lead to timeout ( RTC-38024)

There is no timeout on PriceSuggestionProcessor when wholesale prices on profiles are created and wholesale prices on lower level store groups belonging to these profiles are updated. 

Price suggestions based on wholesale prices (RTC-33726)

Store group table is extended with flag 'CreatePriceSuggestions'. For profiles, which have this flag set to True, when new wholeslae price is created, price suggestions for retail price are created with 'keep margin' rule. It means that when previous price was created with price calculation rule or manually with margin of certain percentage value, in price control grid, there will be a price suggestion with new wholesale price and retail price calculated with previous margin. If new wholesale price is the same as old, then suggestion is not created. 

In price control grid, user can edit, reject and approve new type of suggestions, but there is no button to 'keep margin' as it is calculated automatically. 

Profile price suggestions can be created for active and planned prices.

Flag 'Create price suggestions' on store groups (RTC-37616)

In Store Management, it is possible to set flag 'Create price suggestions' flag on profiles. If profile consists of at least one store, data, including value of the flag on this profile is imported to Chain.StoreGroup table in Item Management database. Any changes on flag made in UI are noted and saved correctly in table. 

For profiles that have flag set to true, if there is added a new wholesale price, price suggestions for price with the same margin as previous price are created.

Markup for currency sales rates (RTC-36908)

The 'Default sales rate markup' field appears in the modal when creating a new currency and is used to calculate the adjusted rate in sales rate. The default value is applied to the first sales rate created and is filled in automatically when creating new rates. Default sales rate markup can be edited from currency details and it's visible below name field.
Markup and adjusted rate columns is included in the sales rate view. By default, the markup is taken from the 'default sales rate markup' for the currency but can be changed by the user to a value from -99.99 to 10,000. The adjusted rate is calculated based on markup and rate, so 'adjusted rate' = 'sales rate' + 'sales rate' * 'markup'.
The markup on all existing currencies is set to 0 by default so it is not affecting current rates.
Two new columns are added in the currency register, 'Active sales rate markup' and 'Active adjusted sales rate', which displays the currently active data for the currency. 
The value from 'adjusted rate' is from now on exported as rate in Currency Sales Rate export blob type.

Validation error when importing incorrect file (RTC-33235)

When a user is uploading an Excel file, which is in incorrect format, or with missing or malformed system header, there is an information about it displayed in 'upload file' modal. In a situation that a file is uploaded without system header - the one row that is hidden, or with it unhidden, there is a message 'Hidden row is not present in file'.

For row present but with incorrect values of names of columns, there is displayed 'One or more columns in hidden row contain not supported values for this kind of file' message. And for files in incorrect format, that cannot be opened in Excel, following message is shown: 'Provided file could not be opened'.

If user tries to upload a file with outdated column name, missing '¦' character he will be informed in message : 'Missing '¦' character in one or more country related columns in hidden row'.

Fix: Order when importing prices (RTC-37686)

Prices are imported and created in the same order as in the imported file. The last price from the imported file is the value that will be active after import.

Break bulk field when ordering item (RTC-37333)

The GetOrderAbilityDetails API method includes the Break bulk field. It's value is returned for scanned CU/TU items and also for TU/CU items linked to them.

Manage order points (RTC-35530)

When adding order point in manage order points grid, valid from date is prefilled with today's date. In item details, in order point section there are visible only 5 stores with active order points. If there are more active order points there is shown 'View all stores' hyperlink. To see all order points user can click on 'manage order point' button. For store user with limited permissions to view store local attributes, there are only visible order points for the store he has permissions to.

Fix: Item group hierarchy panel do not require view register permission (RTC-32684)

To open and filter on group hierarchy panel in items grid, user needs to have only 'view items' permission.

Fix: Changing assortment code trigger label (RTC-37398)

Adding or changing assortment code on item manually or through import, which has assigned 'Eko' label types (Eko Maxi, Eko Mini, Eko Pallet), triggers creation of labels.

Fix: Scheduled trigger of segmentation (RTC-36641)

SegmentationExecutor is scheduled to run once every hour on 15th second of 21st minute. It is possible to trigger it on different moment in time by calculating new or exisiting segmentation. 

Fix: Order proposal attributes (RTC-37002)

Fields in procurement section on supplier - 'Generate order proposal' and 'Email for purchase order' are correctly named and translated. Naming was changed in UI, export - both to Excel and to 3rd party. Column name in database stayed the same.

Fix: Export of Order points (RTC-37152)

Adding, updating or deleting order points via user interface on store level triggers export to 3rd party in blob Item.ItemStoreOverride.Export. When performing these actions on order points on common level, blob Gateway.ItemChanges is exported. Export is triggered also when items are updated by import.

Fix: Excel import and export improvements (RTC-37263)

The store number field is not always checked by default in the export view. 
The Stores field and the Include common values option in the export view are hidden and appear when the Include values per store option in the Store local fields section is checked. Active assortment and Scale fields also appear as selectable for export after the above action. Store local values on the common level are not updated when the user does not have Update existing items permission.

Fix: ItemService package stopped after release (RTC-36451)

In a situation that ItemService package is restarted while there is a long execution of a job, it finishes with status 'CompletedWithWarnings' and is resumed after package is correctly started. 

Translation corrections (RTC-36650)

Translations for Quantity in supplier package, Min.ord quantity and Auto replenishment are correct.

Fix: Duplicated prices in the same file (RTC-36159)

When importing a file in which there are prices for the same item and store group, but with valid from date in the past, only one active price will be created. Its price value will be taken from last row imported (with valid from date set in the past). 

Fix: Currency and active status in wholesale price tab (RTC-34589)

Wholesale prices are shown with their supplier currency and amount. By default only active price is visible, but the user can change filter on 'status' column. There is only one active wholesale price for item, even when there are created multiple different prices with the same ValidFrom, then one of them will have status 'active' and the rest 'expired'.

Fix: Removed scales (RTC-35993)

In Excel export, which includes column 'scale', only those scales which are currently assigned to item are exported. Removed scales are not exported.

Fix: Moving items between models (RTC-36812)

Two situations in which it is possible to move model items are additionally supported:

First is importing file with updated items from the same model, but first is moved (by external model number) to another model and second stays in original model. Then items are correctly updated and moved accordingly to imported external model number.

Second is importing file, where item is found by alternative GTIN and is moved to model (by external model number) with the same color/size variant. Item is moved to model correctly, merged with duplicated item and alternative GTIN is assigned as main (previous main GTINs are now alternative). 

Fix: Filter item grid by item group hierachy (RTC-35674)

It is possible to open side panel for filtering on item groups in items grid. User can select item groups to filter on from dropdown checkboxes segregated according to group hierarchy. Deactivating certain element of group hierarchy is possible only if all 'children' elements contained in it are inactive. There is an error message shown on the bottom of the page when the user tries to deactivate element when there are active 'children'.

Fix: Item-store link is created when a store is added to a profile (RTC-32934)

When creating prices for profiles or price zones (with system parameter 'active assortment' disabled) item-store links are created for every active store, which is contained in 'higher level' store group. If a new store is created and added to an existing profile, for which prices are already created, item-store links on items with these prices are created for this store. The same happens if an inactive store is activated or already existing store is moved to a profile. When the system parameter 'active assortment' is enabled, for newly added store item store-links are only created when the item is added to this store's active assortment. 

Break bulk flag instead of break bulk code register (RTC-34512)

Break bulk code is obsolete and not visible in the user interface, both in the register and item details. Break bulk is a flag, by default set to false, that can be defined on item. Break bulk flag can be exported to Excel and 3rd party, as well as imported (via Excel, Item.Item and RIGAL). Segments in item segmentation, which use break bulk filter can be counted. If item was created when register was still in use, in database in BreakBulkCodeId column in Item.Item table, there will be an old value, but for new items, there will be NULL.

Order proposal attributes and email for purchase orders (RTC-36339)

Supplier registers have following fields in the procurement section: Text field 'Email for purchase order', decimal  'Free freight' and flags 'Replenishment' and 'Generate order proposal'. Values can be imported and exported via Excel in accordingly named columns from supplier registers view. 'Free Freight' value cannot be lower than 0 and validation for 'Email for purchase order' to be in mail format is added. Export of Supplier register for 3rd party also contains these fields.

Currency rate (RTC-36058)

In contract CurrencyRate the flag 'isDefaultForCountry' indicates if exported currency is set as default one for country in which the store is located in.

Sales unit in Orderability details (RTC-36430)

API GetOrderabilityDetails includes 'localizedSalesUnits', which contains information on sales unit of scanned item (item, which is sent in request) in all languages that the unit has name in the registers.

Assortment code (RTC-36083)

Assortment code column is available in Label Printing grid (hidden by default). Only values on item level are shown. User can filter upon this column.

Export items and prices for new stores (RTC-22481)

All exports from Item Management are maintained via Export.BlobType table. After export we save data in the tables [Export].[ExportHistory] and [Export].[ExportHistoryBlob]. The data stored in the database is: start and end time of export, number of exported entities, type of the entity, blob url. This data is saved after the export of changes for which GenericExport job is responsible.

Import of stock status from Inventory (RTC-35573)

Database is extened with table Item.ItemStock, where information on item, store, different type of stock quantities and audit columns are stored. Stock changes are imported by job 'ItemStockImport' whenever Inventory.StockStatus.Export blob is exported. This blob contains maximum 500 rows and the job can process all of them in one execution. If stock is exported for an item or store, that does not exist in database, the job finishes with status 'CompletedWithWarnings'. 

Fix: Store Local Attributes cannot insert duplicate keys (RTC-36408)

It is possible to import multiple import items with store local attributes for the same item and store. Also, if item already exist in database with store local attributes for certain store, then user can update them and import new attributes for another store. When in import, there are different values for the same attributes on item, the last one imported is set on an item. 

ShelfLabel1 adjustments (RTC-35611)

Long supplier names are cut, if they exceed the length of barcode. Label text, supplier name and assortment code fonts are smaller, to not cut bottom parts of characters. Margins of labels were moved to fit perforated paper. 

Fix: Profile country code (RTC-36374)

Country code in profile is updated in database after changes in StoreManagement user interface. 

Fix: Import file with the same new items multiple times (RTC-36288)

The import can handle creating new items when the file contains copies of the same item.

Missing translations in Price Control and notifications (RTC-34620)

Norwegian and Swedish translations are added to Price control columns and side panel. Default name of the exported file is translated to correct language, depending on language settings when exporting 'Item and price' to excel. In price calculation view previously Margin(GP) is renamed to Margin(Gross Profit) and translated.

Fix: Showing the same row for multiple stores (RTC-35207)

In active assortment grid rows for each item-store pair are shown only once.

Moving items between models (RTC-34500)

Items can be moved between models using import (Excel mass update and Item API), according to the following rules:

• When importing already existing items and assigning external model number, which is already in database, these items are move to model with following external model number.
• If in model there exist item with the same size and color, GTIN from moved item is assigned as Main Gtin, while existing one becomes an alternative GTIN (tandem)
• When an item is imported with a new external model number and that number is available in our system - a new model is created and the item is moved to that model

These rules apply when creating new items as well. Models can consist of combination of variants, that does not follow the same pattern of having size, color or both.

Logging exceptions per item in import (RTC-36042)

If faulted data is imported, ApprovalImport job is finished with status 'CompletedWithWarnings'. Exception is not logged per item in job logs, but is saved in database.

Filtering on supplier number (RTC-36205)

Default filter operator for columns in items grid, which have 'number' in name has been changed to 'is equal to'. This results in faster searching for item by default filter.

Segmentation on external model number (RTC-35182)

The InList operator is available for string fields when creating groups in segmentation.

Database, Import and Export (3rd party) (RTC-19907)

Auto-replenishment, Can be ordered, Stop sale, Weight declaration are in Item.Item contract store local attributes section. 
Store local values can be imported by importing Item.Item. 
Store local values are exported via Item.ItemStoreOverride.Export blob type, values for order points on the common level are exported to Item.Changes. 

It is possible to import order points, edit and delete them. 

Order points imported with a valid fom from date in the past will be imported with today's date and the user will receive warning about this during import. Order points imported with a valid from date in the past, when there is already an active value for a store/item pair, will be ignored during import and the user will be notified about it. Valid To date is ignored.

There is a validation in import that order point min must be greater than order point max and values must be greater than 0, the user is informed via an import error.
A table storing store local vales for store-item pairs is added to the database under the name [Item].[StoreLocalAttributes].

Price contract includes total supplier discount (RTC-35003)

Gateway.ItemPrice contract includes total supplier discount. This value is a sum of negative discounts based on wholesale price. Positive values are not included and in a situation, when price calulation rule has only positive discounts, in contract there is exported 'null' value. 

Performance when importing items and prices (RTC-18385)

Import performance is improved by around 50%. When importing from import grid or items in an import grid, validation and automatic import is done without the user having to perform an additional action.  If the validation ends with an error, the import is not carried out. If the validation contains warning, items are imported automatically. The button for PRICAT import and this type of import is removed. 
Files with duplicate new items are imported correctly.

Fix: Update of GTIN in import (RTC-35678)

GTIN can be updated only by users with "update existing items" permission.

Product series (RTC-34663)

Product series column is added in three grids: items grid, items in item list grid and store assortment. Column is hidden by default. It is possible to sort and filter on this column.

Fix: Item grid performance (RTC-35928)

Item grid query is faster.

Fix: Loading of store prices (RTC-35414)

Store prices are loading correctly and request is sent only once when opening StorePrices tab. Changing items between model results in showing correct prices (assign to correct item from this model). 

SKU without leading zeros (RTC-35799)

For new items, SKU is generated with no leading zeros. Next available number is assigned to an item. Updating already existing items has no influence on their SKU.

Order in export from Item Master (RTC-35867)

Whenever item with price is created and activated, the order of blobs exported from ItemManagement is Item, Price, Store link.

Item Order details (RTC-34627)

There is an API GetOrderabilityDetails to the ItemService endpoint, which returns information about whether an item is a consumer unit or a trading unit and information, item properties such as sales unit, whether item can be ordered, quantity in supplier packages, as well as link of linked consumer or trading unit items. When list of trading unit items is returned, default order unit is marked.

Import of wholesale price changes (RTC-34144)

In import details and items in import, there are columns "Wholesale price in supplier currency", which shows the price that is imported, and "Current wholesale price in supplier currency", which shows the price currently active for the given store/store group.  Wholesale prices are shown in these views with the currency code in which they are imported or exist.     
The Pre.Wholesale price column is still visible in the item details view, but will not be used so it is empty.

Fix: Performance when creating price (RTC-35567)

For systems containing big amount of labels, performance of inserting prices is improved. 

Fix: User can't add rows to price calculation setup (RTC-35103)

New rows can be added to the price calculation setup.

Fix: Allowing more filter groups than 32 (RTC-35181)

Segemntations Segmentations can be created with more filter groups, limit of filter groups in one segmentation is set to 500. Old segmentations containing exactly or more than 32 groups cannot be accessed or changed, new segmentations must be created. For ones containing less filter groups, they can be accessed and calculations are correct. 

Fix: Assigning existing GLN to supplier (RTC-33221)

SupplierNO and GLN must be unique so the user sees a corresponding notification when these values do not meet the requirements.  Error 500 is no longer displayed and the user sees the message "This field must be unique".

Fix: Supplier web address (RTC-32191)

Adding a website address when creating a new supplier is possible.

Fix: Avoid copies of the price created at the same time (RTC-31566)

Updating active and future price does not create duplicate future price for an item.

Fix: Wholesale prices tab timeout (RTC-33359)

Opening wholesale prices tab, as well as filtering on columns is fast. There are no timeouts when loading wholesale prices for item. 

Creating new VAT codes (RTC-33528)

When user creates VAT code which is a first active VAT code for a specific country, this VAT code is automatically set as a default VAT code. Then, when creating prices for that country for new item, user does not need to fill-in field in item details regarding VAT codes.

Stability and performance of item imports (RTC-23586)

Working jobs interrupted by a package restart via Integration Platform management or via Integration Platform package release or via webjob restart (in Azure), is resumed afterwards and completes its work.

Fix for: Assortment code per profile (RTC-33740)

Item is exported after change in assortment code per profile.

Fix: Letters typed in product information fields (RTC-33724)

Product information fields in item details can be filled with "w" and "r" without being taken to price calculation window. Other fields in item details can also be filled with hotkeys letters. 'W' and 'R' takes user to price calculation view with focus on accordingly wholesale and retail price fields, when user is not in any input field.

Order of labels in item lists (RTC-32816)

When printing labels from item lists, it is possible to set order. Items added to item list via user interface have order '0' and will be printed in order by created date ascending. User can add items to item list also by 'use file' option in item list view, then order of labels to print will be set the same as the order of items in the file. Every item added by import gets next available number and will be printed after all items with order '0'. In a situation that user adds the same item multiple times, the order will be set as the last action of adding the item. When excluding items, the rest of the items stays in the same order. Order is not visible in the grid, only when user prints labels from item list. When including items to item list by 'use item list' option, the order of all added items is '0'.

Fix: Searching by Store Number in Store Assortment (RTC-33603)

It is possible to filter on store number in Active Assortment per store view. When the user has permissions to access only one store there is no store number column, so search on store is not possible.

Fix: Timeout when searching in item text column (RTC-33501)

Searching for items by item text column returns results within 30 seconds. Filtering in item texts includes item texts for multicountry localized text (for all system countries).
Following operators are available during the search: is equal to, starts with and contains.

Fix: Searching by GTIN (RTC-33563)

It is possible to search by GTIN in Items in import grid. 

New shelf label types (RTC-30500)

ShelfLabel1 label type is available for use in Item Management. Labels can be generated manually from item details, or when added to label type of specific item, they are triggered by changes in price, GTIN, LabelText1, UnitPriceFactor, UnitPiceUnit, Supplier Name and Assortment Code. On label there is visible unit price, which if is equal to zero ( no UnitPriceFactor and UnitPriceUnit) is shown as retail price value. Layout for printing on vertical sheet is 3 columns of labels and maximum 11 rows on single sheet.

Fix: Creating store price for an item that has a new VAT code (RTC-33555)

Prices are created correctly when VAT rate starts today.

Export currency rates (RTC-32361)

When a new store is created, export of a blob CurrencyRate with all currencies per store is triggered. If currency's End Date is in the past, it will not be exported.

Fix: Excel cannot be exported with VAT code and rate (RTC-33498)

Item is correctly exported to Excel file, when user is exporting VAT code and VAT rate.

Fixed price columns (RTC-18946)

In import items grid (both in items in import and in details of a specific import), user can add to view columns 'Current Fixed Price' and 'New Fixed Price'. Values of those columns are checkboxes, which if checked signify that imported price is fixed. 'Current Fixed Price' shows existing value of flag on an item or on store price and 'New Fixed Price' value of a flag after import of selected file. In import grid 'New Fixed Price' value is either taken from current store price or if there is no previous price for imported store number - from item. The value shown is the same which will be on an item/price after import.

Fix: Multi-language item text: truncate item and model name (RTC-33366)

Item text and model name are truncated to 255 characters when a longer value is imported. 
Items are correctly visible in the item grid and it is also possible to enter item details when there is no default language, or when the default language is different from the language for which the item text is saved.

Fix for gap in vat code rate validity (RTC-30494)

Start date and end date is created with an offset corresponding to the time zone of the country for which the vat rate was created. It is also possible to edit the vat rate if its start date is today or is in the future. Vat rate must be a whole number not a decimal value. The registry only shows vat codes for countries that may be system countries, this also applies to the creation of new ones.

Fix: Performance and filtering in Store Assortment grid (RTC-32926)

It is possible to filter on store number in active assortment view. Default value of filter is set to 'is equal to'. If user has access to only one store, store columns are not visible so it is not possible to filter upon it. Item area values are visible in the grid. 

Changes on item via import (RTC-31620)

Fix for multicountry item text (RTC-33231)

CountryLanguage does not duplicate in the cache, so importing items is possible. 
ItemText containing special characters is correctly processed and exported by GenericExport job.

Wholesale price (RTC-31867)

Wholesale price table contains columns as: Valid from, Status,Valid to, Wholesale price and Net price. 
The table displays the wholesale price that is created during the creation of store price. Unique wholesale prices are shown, which means that even if several stores have the same price, it will be shown only once.
Clicking on the valid from corresponding to the wholesale price will take user to the store price, the open store price is the oldest one (that matches Validfrom date).

Supplier register: Export to Excel (RTC-23340)

It is possible to export supplier registers from supplier register's view by 'Export to excel' button. They can be filtered on and file contains only visible in user interface suppliers and columns (except for audit columns). 'View registers' permission needed. Nulls instead of empty cells are allowed only for 'Lead time (days)' and 'Transport time (days)' columns.

Fix: Brand register: Export to Excel (RTC-23340)

Null brand category values ​​are exported as empty strings. 'View registers' permission is needed to export Excel file with brand.

'Manage assortment codes' button (http://RTC-32121)

Button name is translated to Norwegian and Swedish accordingly to user's choice of used language. 

Export to Excel (RTC-28823)

User can export items from store assortment from 'edit' view. Clicking on the Export items to excel button open a view where user can select store group level, and desired columns. Prices existing on the item for only chosen store group level will be exported, for the rest fields will be empty. Checkbox 'Include value per store' in store local fields is checked as default. For exporting items user has to have permissions 'export to excel from items grid'. If user has access to limited amount of  stores and does not choose which store to export prices or store local values from, they will be exported for all stores item has prices on and user has access to. 

FIX: Removing ID requirement in import (RTC-32757)

Entering 'null' as a value of idRequirement in Item. Item import results is removing it from an item.  When user uses 'mass update' import  'code' columns of Id Requirement have to be NULL in order to remove the values from an item.

FIX: Currency rate at the same day (RTC-32143)

It is possible to edit sales and cost rates in the currency register, when the start date is on today's date.

External model number and ID requirement (RTC-31591)

'External model number'  and 'ID requirement' can be used to create groups in segmentation

API for label printing (RTC-24130)

Sending a request GET api/gateway/Labels/labelType - without store specified - results in receiving a message with all registered label types. The same results will be returned when there is an incorrect store number in the request. In a situation that a store is chosen in request parameters, only label types registered for that store are returned. Sending a non-existing number will show no label types in results. API can choose a language to translate the names of label types by setting parameter 'culture' to nb-NO, en-US, sv-SE, but default language is set to English.

It is possible to add labels to label printing by sending request POST /api/gateway/Labels/print. Label of specified type can be created or be ready to be printed  by request, only when the item has an active price and label type assigned to the item. If the same label has already been printed, it would be set as not printed, but if it was not existing yet, new label will be created.

StagingBatchExecutor job (RTC-32242)

When there is a timeout in StagingBatchExecutor job, it finishes with status 'Faulted' and resumes on the next trigger. In essence, when processing big imports and reaching a timeout - job will be only faulted and resume with processing unprocessed rows in import. 

Import prices with 0 (RTC-32571)

User can import prices, where retail price, net price or both are equal to zero. There is a warning shown when retail price is equal to zero. 

Fix: Filtering on GTIN column with different values of checkboxes (RTC-32616)

User can filter on GTIN column - using GTIN or alternative item (tandem) as value - with all of the options of the checkbox in item lists. Correct results are returned based on filtering in the column and value of the checkbox.

Fix: Sticker 2/3 barcode problem (RTC-32342)

The barcode on Sticker1 and Sticker 2 labels is larger and therefore more visible and scannable.

Filtering on GTIN  (RTC-31155)

Default filtering on GTIN column in: Label printing, Import details, Items in import, Item lists view is "is equal to". User can look for an item using GTIN value in this column, as well as Tandem GTIN value.

Mass update import: Deleting prices (RTC-31884)

Importing item with price in mass update containing column "Price is deleted" will have following impact on prices: If value is set to TRUE, all of the prices for given store group (profile/price zone/store) are deleted for this item. When prices are deleted for profile or price zone and item has also price on store level - and store is part of that profile/price zone - store prices are deleted as well. Importing value FALSE is not deleting any of prices, as well as leaving values in column empty.

Fix: Item area column (RTC-32069)

Item area column shows correct values on items,  both in items grid and items lists view. It can be filtered and sorted upon. 

Use file (RTC-31872)

Including or excluding items in the item lists can be done using alternative GTIN (Tandem) as values in column GTIN. Tandem GTIN values are used only as a lookup for an item.

Multicountry: Store prices with time / Always create new price (not edit) (RTC-30820)

• Valid from date and time is displayed in store price details and in store price grid. It is possible to create a price with the selected time. 
• In the user interface it is not possible to edit active price. Only the future price can be edited via user interface. If the user wants to edit active price for given store, user creates a new price.
• When importing price that has valid from in the past (past = can be the same date, but 2 hours earlier) new price is created.
• Future prices can also be edited via import.

Price control grid (RTC-31424)

Column informing of price suggestion status is named 'Update type' and can have values such as 'New' or 'Price change'. There are links in price control and price control history grids, on the 'item text fields', that open item view for selected item. User can also click on a link on 'active' and 'new' retail price in price control grids, it will take it accordingly to a current store and source profile price view. In both price control and price control history grid, there are 3 frozen columns always visible to a user - 'Valid from', 'Gtin' and 'Item text'.

Brand register: Export to Excel (RTC-31001)

It is possible to export brand registers from brand registers view. They can be filtered on and file contains only visible in user interface brands and columns (except for columns containing dates/users). 

Fix: Item search modal (RTC-32232)

When selecting an item in item search modal (deposit and substitution item), the form is updated with it.

InternalSupplierNo in export of item changes (RTC-28310)

InternalSupplierNo value is added to supplier in export of item changes.

Barcode on sticker labels (RTC-31465)

• The barcode on sticker labels is taken from Sales code
• The barcode is encoded in code 128
• The labels are scannable

Price calculation (RTC-29715)

Margin (GP) % is calculated as (Retail Price excluding VAT-Net Price)/Retail Price excluding VAT. Boundary conditions for values are +100% and -10000%, when they are reached system parameter set in system is used for calculating its value. Very high or low values of margin percentage are rounded in UI to +100% or -10000%, but in calculations they're below this value (user can click on margin percentage and it's visible).

Import performance (RTC-27780)

Database queries are optimized to improve performance when importing items.

Weight declaration (RTC-31224)

Weight declaration field is 50 characters of width (more or less it depends on the characters). When editing this field user sees a horizontal scroll bar that informs about reaching the limit, the words that are behind the scroll bar are moved to the next line.

Database maintenance fix (RTC-27620)

ItemServiceJanitor: Deleting indexes in nightly trigger of jobs is refrased, so the job is not faulted.

Price import (RTC-31167)

When sending an Item.ItemPrice blob with 'deleted' status on price: if any prices for this storegroup exist on the item, they are removed. If there isn't any price for presented storegroup, contract is ignored and price is not created.

FIX: Fixed price on store price (RTC-31167)

If sent store price has ValidFromDate in the past and price is the same as it was before, but the flag on Fixed Price is different from current store price, price is updated.

Active Assortment (RTC-30823)

Columns in Active Assortment view can be filtered and sorted upon.

Fix: Print labels as store user (RTC-30196)

There is no 'Store' dropdown in print label modals if the user has access to only one store.

Changes have been made to the manual printing labels from item details and item list.

Better performance when exporting to Excel (RTC-30016)

When exporting all items/all store prices the performance is much faster.

FIX: New price created all the time when ValidFrom is in the past (RTC-30993)

• A new price is not created when it is the same as the currently existing price.  If the price in the system has a validFrom of 2021 and we update it with a price with a validFrom of 2022 but the prices are identical, new price is not created.
• A new price is created when it is different from the existing one. If the price in the system has a validFrom of 2021 and we update it with a price with a validFrom of 2022 but the prices are other than existing one, a new price is created. 
• A future price is always created.
• In case there are multiple prices within a single file for the same item/store/store group, where all of the prices have validFrom in the past, the last one (by order of appearance within the file) will be used.

Store prices in local time (RTC-25902)

Valid from in local time is exported with price in FromDate field. Obsolete version of valid from date is still exported in FromDateUtc field.

FIX: Keeping values when Excel import does not contain values (RTC-30617)

When updating item via mass update (Excel file doesn't contain following columns) values from these fields are not removed:

• substitutionItem
• riskItem
• categoryManager
• productSeries
• scaleLabel
• treatmentType

Price control (RTC-12193)

Price control entry can be found in main menu, under "Item" section. In right top corner there's Price control and price control history switch grid button. It is possible to navigate to price control history from price control grid. To access this grid user needs permission "Approve prices" on store level. 

Improved performance of Swagger user interface (RTC-30314)

Performance of Swagger user interface is improved. Loading of docs takes visibly less time. There is a new button that copies file-type name to clipboard. 

Import of unit price factor (RTC-29077)

If any of the fields unit price factor or unit price unit are specified, both are required. When importing, there is a validation error if there is only one field specified in the import file.

Generation of model number (RTC-27887)

The smallest value of generated ModelNo is 100 000, and the biggest value is 99.999.999.

Label types for stickers (RTC-29281)

• Three label types: Sticker 1, Sticker 2, Sticker 3.
• It is possible to print the labels on a stickers in a roll.
• Label size is 75x33mm.
• Sticker size is 45x23mm.
• Information on the label (Sticker1):
  • Price
  • Item text
  • Barcode (Code128) containing Sales Code
  • Sales code
  • Comparing price (price/liter, price/Kilo etc.) when that exist
• Information on stickers (Sticker2 and Sticker3):
  • Sales code
  • Barcode (Code128) containing Sales Code
  • Printing date (Sticker2 only)
• The currency symbol on the labels is Euro.
• Number of sheets required in printing modal doesn't appear for Sticker1, Sticker2 and Sticker3. 

Revert to "ready for import" (RTC-29703)

Reverting import to "ready for import" changes status of an import and triggers revalidation. 

Label types section (RTC-29834)

When there is more than five stores in the label types section, only top five of them are shown. There is a button underneath them, which takes the user to another view with list of label types per store. Label types that are on 'All stores' level are shown first.

Printing labels from item list (RTC-24213)

• User can print/create labels for all items in the item list.
• When not all items within the item list have prices for the selected store, user will see a warning that X out of Y items don't have prices for selected store. 
• User can print/create max 1000 labels from one item list
• Stores in the model are filtered by the user permission 'Manage store local values'
• Label types are filtered by the label type register. 
• Items that do not have a price for the store, their number is shown to the user in the notification. It is still possible to create/print label for the remaining items.

Import of franchise store flag (RTC-29209)

Price control is used for franchise stores. The FranchiseStore flag is updated based on changes in Store Management. 

Import of supplier item number (RTC-28902)

Import of RIGAL format supports RIGAL field 7.1.125 as an alphanumeric supplier item number.

FIX: Update of Item name (RTC-29313)

In non-model items, the model name is changed to the value imported in the item text field.

Model name for non-model items is updatable after changing item text manually in item details view.

FIX: VAT code when switching items within model (RTC-29313)

VAT code does not disappear when moving between model items.

Warranty type (RTC-29463)

The maximum value for warranty months is 999.

FIX: Large number of rows in label printing grid (RTC-29787, RTC-29907))

There is no timeout when opening label printing grid, and filtering is fast.

FIX: Alternative GTINs (RTC-29827)

• To manage GTINs/alternative tandems user needs 'Update existing items' permission or 'Manage local items' permission and item needs to be manage in store (where user has permission).
• Managed by store checkbox is visible on non-model items.

Permissions for alternative GTINs (RTC-28462)

User that does not have 'Update items' permission cannot add or remove GTINs/alternative GTINs. User that has this permission or Manage local item (and the item is managed by store), can add or remove GTINs for items.

Grid in model/variant/item level (RTC-24923)

State of grid is kept when changing 'browsing by' levels and after a page refresh.

Weight declaration (RTC-28385)

• Weight declaration is shown in its own section (one column).
• The whole text is visible in the preview.
• Text is editable in modal, in a text area roughly 40 characters wide and 20 lines in height. If the text is longer scrolling appears.
• Modal has the ability to decide whether to save the change on all elements/sizes/colors of the model.

Processing of labels (RTC-29689)

LabelProcessor perfomence is slightly better.

Export of alternative GTINs (RTC-29328)

• Deleted alternative GTINs are exported as 'Deactivated'.
• When an alternative GTIN is 'moved' from item A to item B, then alternative GTIN is exported with item B and item A has null value.
  
  

Stability in approval import (RTC-23108)

When a long running job is running, and a package is restarted via Integration Platform Manager or via release of Integration Platform package there is no exception and validation/import is resumed in next job execution.

FIX: Export of labels to 3rd party (RTC-29473)

Only the latest labels are exported (if there are more labels not exported). Next job execution doesn't export older labels.

FIX: Converting PLU field (RTC-29401)

When converting scale labels to Myhrvold in ItemServiceOnPremIntegration package, field PLU contains digits 3-8 from the GTIN. When these digits have leading zeros, they are removed. 

FIX: Manually printing label (RTC-29349)

When manually printing a label, the generated label is compared to the latest one, not the first one created.

FIX: CountryCode in profile/team (RTC-29383)

StagingBatchExecutor job is not aborted when a store is imported from Store Service with CountryCode = '' (empty string) in profile or team.

Printing future labels (RTC-25130)

Import of country linked to stores (RTC-23087

• CountryCode is updated only when storeGroup has 'Profile' type 
• New column in Chain.Store table - AddressId
• Store address is saved in the dbo.address table. The correct address id is assigned to the store
• All stores have AddressId (possibility to assign address to it)

Export of external model number (RTC-29023)

ExternalModelNo is exported from Item Management to JSON file.

FIX: Print of amount on labels (RTC-28948)

When store price amount is in whole kroner, the .00 øre is printed.

Fix for Myhrvold scales (RTC-28851)

ConvertItemLabelToMyhrvold job doesn't fail when exporting labels on items that don't have unit price unit and unit price unit different than stk.

FIX: New item without supplierNo (RTC-28459)

• SupplierNo is a mandatory element of the imported new item. If it is not in the import, there is a validation error informing the user about it.
• ItemGroupNo is a mandatory element of the imported new item. If it is not in the import, there is a validation error informing the user about it.

Export to Myhrvold scales (RTC-27932)

• Unit and calculateUnitPriceInScale flag are exported in lowercase.
• Unit piece is exported as stk.
• The delete action is sent for items that have deleted item store links and for items that have been deactivated.

Multi country VAT code (RTC-22544)

• List for VAT codes for countries appears when there are multiple system countries in the country register
• Only system countries are exported (both Excel and blob)
• If there is no attached VAT for the country in the import of the item, the default is set. If VAT exists in the import, it is assigned to the item, (non-system countries are skipped, with an appropriate warning)
• The default VAT code for a country is assigned when creating a new item. If the default VAT code is not set in the registry, the field remains without VAT value
• VAT code is required only for the default country when editing item.

Print label from item details (RTC-28033)

• User can print labels for a specific item from the item details view.
• The button is visible only when the user has the label printing permission
• The store picker in the modal shows only the stores that the user has permission
• User can manually create label or add it to label printing
• Label can only be created for a store that has a price
• Store that has 'None' label type or no label type assigned in the register is unable to create a label (the choice of label type is blocked)
• The label type picker in the modal shows only the label types that are in label type register
• Labels created manually have a Manual label trigger reason

Fix: Import from Promotion module (RTC-28648)

There is no timeout in StagingBatchExecutor  when importing  and staging a lot of OfferItems from Promotion Module. The promotion package is updated to 1.6 and new type of offer mix type (100) is supported.

Export of item status to 3rd party (RTC-26850)

• Scale labels are exported with Item Status.
• Exported scales have their status exported as well (Active or Deleted).
• When scale link is deleted from item, their scale status is exported only once.

View and manage labels for store users (RTC-26783)

• For label printing there are permissions: 'Manage store local attributes' and 'View store local attributes'.
• In order to view label types on the item, user needs 'View store local attributes'. No matter the level of role with this permission, user will always see the label types on the 'all level'. For other levels, the visibility should be filtered by the access of that permissions.
• If the user does not have the manage store local attributes, the 'manage label types' button is hidden.
• In order to modify label types on item, user needs 'Manage store local attributes'.
• User needs the permission on 'all stores' to be able to add the attribute on 'all stores level'. Otherwise, he can only manage it on stores that he has access to. 
• When a user has 'Manage store  local attributes' on store 100 (and no 'View store local attributes') he should still be able to view the store local attributes on store 100. I.e. 'Manage' permission should implicitly give 'view' on all stores (that have the manage permission + labels on all store level).
• Without those permissions, user does not see label types on item at all. 

Fix: Change ValidFrom to today (RTC-28194)

Fixed import when importing file without price.

RIGAL import of supplier discount and fixed price (RTC-27561)

EkoPallet label type (RTC-27824)

Fix: Item store links (RTC-28098)

When creating a profile price (for a new item), item store links are created for all stores that profile has.

Import of 20-codes (RTC-27461)

Alternative GTINs are converted to 20xxxxxx00000 format when the parameter "EAN20 conversion" is enabled. The original and converted alternative GTINs are added to the item.

Permissions to view prices (RTC-27422)

User that has store access and view prices permission on store level, can see price calculation on profile/price zone level, if store is in profile/price zone.

Performance for dynamic segments (RTC-27540)

• The method GET ItemSegmentations/GetItemsWithPrices [id] returns results faster, there's no timeouts when requesting prices (if they are, they're related to bug in Promotion that will be fixed in: RTC-27395 [Promotion] Add indexes to the views)
• Method return top price for an item (in list)
• The hierarchy for returning prices when making promotion is (the same):
  • When filtering by store - store price, with fallback to profile and then price zone.
  • When filtering by team - Price zone price with fallback to store.
  • When filtering by profile - Price zone price with fallback then store.
  • When no filtering (promotion on all stores)- Price zone price -> profile -> store. 

Label printing grid (RTC-27764)

Columns "Item group number" and "Item Group Name" are available in the printing label grid. 

The label printing grid is sorted in the following order:  LabelType, StoreId, ItemGroupNumber, SupplierId, ValidFrom.

Import of alternative GTINs from Excel (RTC-26789)

Excel can be used to import and export (mass update) alternative GTINs.

Alternative GTINs (RTC-27349)

There are buttons that allows to collapse and expand list of alternative GTINs and scale groups, if there's more than 5 of them linked to an item.

Avoid generating labels for specific items and specific stores (RTC-25063)

• Label type 'None' can be added to specific stores (both in item details and in label type register).
• If an item has label type none, no labels are created for it.
• By adding none label type to the store, it can be the only label type for that store. If there are other label types in the store, there should be validation error when trying to add 'none'. 
• The label type 'none' can be added on the item level, even if it doesn't exist in the register.
• When adding 'none' to register for a given store, it is always added as default (and must be the only 'default' label type for the given store).
• 'None' label type can be exported only per store. 
• When importing items and Excel/file has 'None' in store, it wins over any other label types (i.e. ignore the rest). 'None' imported as common will be ignored.

Handling of item status (RTC-26848)

When item status is changed (to inactive, active, stopped form sale) and label has already been exported, a new change (label type Myhrvold) is created and exported.

Import status (RTC-23195)

• When validation/import is in progress, there is a percentage next to 'Validating... 10%' or 'Importing...'. The percentage shown is updated after validation/import of each batch is processed (500 items).
• Validation/import percentage is visible for all users.
• The percentage updates automatically, same as "No of rows not imported". 

Fix: Managing scale links (RTC-27428)

User that has 'Edit items' permission can add/remove scale links to/from item.

3rd label type (RTC-26757)

Label type EkoPallet is added to label type register

Scale register (RTC-26376)

Scale can be added to scale group from scale group register view.

Export to Myhrvold scales (RTC-27273)

FixedWeight in exported labels has a value from UnitPriceFactor in item details or 0 if there is no value there.

FIX: Creating register values during import (RTC-26933)

• When importing file with many items that has brand that is not in the register and there's space in one of the brand codes (for e.g. 'CODE1' and 'CODE1 '), space is removed and new brand in register is created.
• When importing model item with new subgroup or new item group and subgroup that are not in registers, they are created during import.

Search for item/price imported for given item (RTC-26793)

When searing for an item in imports, available columns also includes:

• Created by
• Created date
• Modified by
• Modified date
• Store group code
• Store group level
• Store group name

Keeping good performance on filtering and sorting on these columns will be developed later.

Print label from item details (RTC-24121)

• User can print labels for a specific item from the item details view.
• The button is visible only when the user has the label printing permission.
• The store picker in the modal shows only the stores that the item has labels for (+ filtered by user permissions).
• When the label is printed, it's marked as printed/current.

Import of 20-codes (RTC-27109)

Parameter  EnableEan20Conversion must be set for retailers using 20-codes with price or weight.

When the parameter is enabled:

• When imported item has GTIN with 13 digits and starts with 20-25, then second digit is set to 0 and last 5 digits is set to 00000
• When importing item with GTIN 2x and item with GTIN 2x exists, the 2x GTIN is moved to tandem and set main GTIN to 20x. The last five digits are also set to 00000
• When importing item with GTIN starts from 20-25x and item with GTIN 20x exists, the existing item will be updated.  
• In the import items view, the GTIN visible in the grid is the original GTIN. 

Fix: View price permission (RTC-26795)

User that has view prices permissions on store level, can see store prices on profile/price zone level that contains this store.

Import of alternative items (RTC-27188)

Fix: In case of alternative GTINs for an item and scale links per store for an item.

• When applying changes to item with many alternative GTINS, search indexing job works properly
• When exporting item with many scale links to Excel, file is exported with all scale links

Create item with 20-code (RTC-25881)

The check digit is not validated when manually creating item has GTIN starting with 20.

Fix: Filtering in label printing grid (RTC-26984)

• When filtering a column user can input the value and filter by clicking 'Enter'.
• Store number is not decimal.
• EAN/PLU in heading is changed to GTIN.

Supplier's internal identifier (RTC-24871)

Supplier export to blob contains supplier id as 'internalSupplierNo' field.

Fix: Items in import (RTC-26383)

Item in import can be searched easily without a timeout.

Default label type (RTC-26103)

It is possible to set the default label type in the label type register (both common and per store).

The default label type is used when creating a new item manually.  If an item that is created during import has a label type specified in the imported file, the label type is taken from the file, otherwise, label type is set from the default value in the register. 

In import: If a label type specified on the item does not exist in label type register the value is ignored and system show a validation warning.

Fix: View items (RTC-26788)

User needs only 'view items' permission to see items (there is no server side error).

Export performance and stability (RTC-26405)

For Generic Export there is a log of exported rows of Items, ItemPrices, ItemStoreLinks.

MemoryGrant is reduced and query plan is more stable.

Export to Myhrvold scales (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 Myhrvold XML file is named after StoreID, by which labels inside XML are grouped.

Label type register and manage label type view (RTC-26389)

When adding label type on item:

• The default selection is 'All stores'
• Label types are not be preselected
• When label type in register is on 'All stores' level, user can add any store for that label type on item
• If user selects a label type that already exists, there is an error that this is already added.
• Available label types are shown based on chosen store
• When in register there are two types of label types A,B  with 'All stores', but there is also label type A on specific store, then on item level when adding the label type A with this specific store, it's not possible to add label type B for this specific store

Use Excel to link item to scales (RTC-25743)

Import performance and stability (RTC-26412)

Merging of ImportItem is split into Inserting and Updating, ApprovalImport is more stable (no timeout during validation when comparing to old version).

Fix: Item/scale links (RTC-26531)

When removing all scale links (within the scale group) from the item it can be done by unselecting scale group checkbox.

Export item and price changes to scales and 3rd party label system (RTC-25745)

• When a scale is added to an item, an export row (label) of the corresponding label type is created.
  • When another scale within the same store/labeltype is added, a new export row (label) is created (in order to export the label with a new scale code). 
  • When the scale is deactivated, export rows are no longer created (or include it in the export).
• Export rows (Labels) are created per item/store.
• Item.Label.Export blob is extended with a list of scale codes.
• LTG label type is added.
• Myhrvold label type is visible in Scale register instead of Label Type register.
• When filtering by label type in the label printing grid, only EkoMini and EkoMaxi label type are visible.

Fix: Export Excel from import view (RTC-25168)

Default item file type (JSON) that has been imported, can be exported to Excel from import view.

Fix: Scale links (RTC-26513)

Scale links are saved on item when user clicks save button in scale links view.

Link items to scales (RTC-25742)

There is a view in item details, under the Scale section, where scales can be linked to an item (scales group are displayed). Only active scales can be added/removed to an item, when scales group is inactive, user cannot link scales from this group to an item.

Applied only for non-model items so far.

Better performance when exporting from ItemService (RTC-25985)

• Export of items and item prices are using row version instead of using ChangeTracking. There are indexes on RowVersion for these tables
• SearchIndexing (Elastic search) is completed after export of Item changes
• Changes are exported in batches of value established in GenericExport AppSettings
• Fix for paging on ItemPrice, now it does a scan on StorePrice table if there are many rows in changetable.

Fix: Units import when default country is Sweden (RTC-25511)

During item import via JSON contract with new unit register, new Swedish unit is displayed in unit register and has correct LanguageCode for Sweden (SV).

Labe type register (RTC-24129)

Label types register is used for defining what label types is used by all stores or by specific stores.

• When adding label type on item, only pairs of Label Type and Store that are in the register can be added.
• • When label type in register is on all stores level, in item details it can be added on all stores as well as for specific store.
  • When label type is registered is for a specific store, in item details the label type can be added only for this store.

Myrhvold label is removed from register (it's has scale Category), LTG label is added to register.

Scale group register (RTC-25740)

Scales can be grouped to make it easier to maintain the link between items and scales. Scale groups can for example be 'Bakery' and 'Fruit and vegetables'.

Export labels (RTC-24210)

Labels with Myhrvold label type are exported to blob.

Creating labels (RTC-25057)

• When a label type is added to an item (common or store), new labels (including current and future) are automatically created.
• When a label type is removed from an item (common or store), all future labels (of that type) are removed.
• When a label type Z is added on store A and an item has a common label type Y, all future labels on of type Y on store A are removed (and of course new labels of type Z are created). 
• Labels that are of type ESL (Breece), are not removed when label types for printing are removed (common or store, current or future).

Imports set as Done (RTC-24238)

All existing imports that have all imported or rejected rows are marked as done.

Label type (RTC-25061)

EkoMini label type can be selected when managing label types.

Export of VAT to Excel (RTC-24214)

When exporting items with a different system country and default country than Norway (e.g. Sweden) VAT code and rate are correctly exported to Excel.

Fix: Mass update export and import of sorting code (RTC-24862)

It is possible to export and import via mass update sorting code without any other values from the assortment category.

Supplier number filter (RTC-24672)

There is a possibility to search for an item assigned to supplier, using Item Service API. Requests with new parameter (supplierNo) returns only items assigned to correct supplier.

Fix: Uploading an image to non-model item (RTC-24538)

Uploading an image to a non-model item works fine again.

Use Excel file to manage lists (RTC-13667)

Excel file can be used to manage selection in item list and item group list. Item/item group list exported to Excel file can be used as a template. CSV files are also supported. At least one column with identifiers is required in the file:

• Item list: Sku, MainGtin, ExternalItemNo,
• Item group list: ItemGroupNo.

Fix: Deactivated item becomes active when pressing save (RTC-24815)

When saving a deactivated item user gets a modal window asking whether to activate the item. The 'submit' (aka default) button is 'No'. There are also Yes and 'Cancel' buttons.

When user click 'no', the window with saving changes should appear and after saving changes selected items should still be inactive.

When user click 'yes', the window with saving changes should appear and after saving changes selected items should become active.

When user click 'cancel' the window should close and nothing happens.

Label types (RTC-24128)

Label types valid for item and items for given store can be specified. Label type specified for store level has priority over the label type on the item level.

There is always created a label in Breece label type, when store is configurated as Breece store, even if there is no ItemLabelType with this type. 

Fix: Update button when editing price (RTC-24824)

It is possible to edit price that are active and have a valid from date in the past.

Fix: Configuration cleared when switching between tenants (RTC-22045)

Configuration browser cache is cleared each time the user logs in. Fixes issue when switching tenants that have different configuration (user needs to log out and log in, in order to switch tenants). 

Fix: Excel template are duplicated in Excel view (RTC-24495)

"Excel template" text is not duplicated in export wholesale prices to Excel view.

Fix: Scheduled update of promotion offer (RTC-24602)

During scheduled update of segmentation in Promotion Management, there is no issue in communication between Item Service and Segmentation Service.

Cleanup of imported items (RTC-20464)

• Janitor job continiously runs every minute (on 18th second).
• The 100 oldest rows of import, that are older than 180 days, are deleted from database, including empty imports.

Notifications during import (RTC-22004)

When validation/import of an item in import is done, the status header disappears and notification shows up automatically.

Item attributes: Product ID, sales code and bonus flag (RTC-23854)

• Product Id (Item section)
• Sales Code (Item section)
• Bonus (Sales section)

From 3rd party we can get items with Product ID as item identifier. Sales code is used when different items represents the same item from a customer perspective (for example two oil filters with the same price can used in the same car). Bonus flag is used to mark items that should not give any bonus.

All the fields above can be segmented upon.

Label printing view (RTC-24118)

Label printing grid shows all items with changes available for export or print. The grid contains columns such as:

• Valid from, Store, Item text, Brand, Promotion price, Label text1, EAN/PLU - which are shown in default view.
• Brand, Member Price, Label text 2, Supplier name, Supplier item no., Volume, Weight, Eco label, Created/Modified date, Created/Modified by.

All the columns can be filtered and sorted upon. 

Permission can be defined on store role level - 'Labels', when role with Label permission is assigned to a store, the user can only see labels created for this store.

'Print Labels' button is shown, but do not perfom any action. This functionality will be released later.

Fix for import 'default' file type staging (RTC-24157)

• When sending file with blobtype 'item' and with 'default' ApprovalRuleset (or without ApprovalRuleset) import is created in db and scheduled for ValidationAndImport.
• When sending file with blobtype 'item' and with filename containing text 'swisslog' directly import contents of the file without creating import in db.

Integration documentation (RTC-24074)

Fixed swagger documentation for import, so that it can be used for code generation. 

Default import of items and prices (RTC-22414)

The two file types in the "File type" in imports view that are default when importing from 3rd party:

1. Item ("Default" approval ruleset is named "Item")
2. Store price (BlobType ItemPrice)

In the file type "Store price" you can import items with store prices, you can create a new price that will be created with the default price calculation, and update the existing price. You cannot create a new item of this type.

When changing image the new image is displayed for user (RTC-23127)

Clicking 'Save' after changing image, does not reset the image back to the previous one. 

Special characters in RIGAL file (RTC-22777)

When uploading RIGAL file with special characters, the system can handle both the UTF-8 and iso8859-1 encodings. Applies to import via import grid and Postman/API.