Coming next release
Import of stores from API
Stores can be created and updated by 3rd party using JSON file import via File Service. Required format of data is documented in Swagger. File content is validated before saving it (same rules as in user interface). Stores must have store number or external store number. These two are also used when updating existing store (store number has higher priority than external store number). When store is created with only external number, its number will be set to lowest available number.
When file does not contain profile identifier, store will be assigned to default profile. If such profile does not exist, new one is created and marked as default.
When imported store has identifier of store group that does not exist in Store Service, new store group is created with name in format "<store group type> # <store group number>".
External store number is a unique value. Existing duplicates are updated with "-Duplicate" suffix. Field uniqueness is validated when editing store in user interface and in Excel import.
Improvements
Module | Description |
---|---|
System | Fix for filter of column with date (RTC-24356) When filter is applied on date column, after opening row and coming back to grid (using breadcrumbs or back button), date filter applied to grid is displayed properly. |
...
Release 22.07.2022
Module | Description |
---|---|
Stores | Hide inactive stores by default (RTC-23778) Stores grid has a default filter on 'Inactive' column, which shows only active stores. |
Teams | Filtering store selection by a profile (RTC-22913) There is a possibility to filter stores by a selected profile when adding stores to the team. New, multi-select field named 'Profile' has been added to the view. "Select all" and "Unselect all" buttons allow selection of all stores currently filtered by profiles. Store search works only for stores filtered by profiles. Also, new column with profile assigned to store has been added to the grid. |
...
Postal codes register can be accessed from menu in "Setup" section. Postal code register contains fields: "Code", "City" and "Country". Postal codes can be added, edited and set as inactive. Pair of "Code" and "City" values must be unique. "Code and "City" are alphanumeric input fields, and "Country" is selected from dropdown.
There are two permissions in User Management: "View postal codes" and "Edit postal codes", placed in Store - Postal codes section. These are required to view and edit postal codes register.
Improvements
Module | Description |
---|---|
Company | Manage stores (RTC-20675)
|
Export | Edit company (RTC-21032 After editing a company, stores assigned to it are re-exported with new values of the company. This happens only when edited company detail field is included in store export ("Company code", "Company name", "Country", "Organization number"). |
Store groups | Active' flag for stores and store groups (RTC-21068)
|
...
New company can be created by clicking on 'New company' button in "Companies" view. By clicking on company name in grid, we can open company details. In this view we can edit details of the company. Changes are saved using 'Save' button, or canceled using "Cancel". In the grid at the bottom of this page, we can see a list of stores within the company. Clicking on store name opens store details view. Using "Add new store" we can create a new store with company pre-selected.
In company details, "Organization number" is validated based on selected "Country". This value must be 9 digits long in Norway, 10 digits in Sweden and at least one digit in other countries.
Improvements
Module | Description |
---|---|
System | Use of breadcrumbs in user interface (RTC-19764) In store, team, profile, region and company details view, we show breadcrumbs in "<unique id> - <name>" format. When opening store details from the grid in team, profile, region or company details view, breadcrumbs show the correct store group, from which we navigated to this page. Change tracking (RTC-19983) Change tracking is retained for 2 days. |
...