Item Management release notes

Previous Item Management release notes

Released 9th of April 2025

Show and allow to filter on Shelf Location (RTC-48504)

A new option has been added to the "Main shelf location" column in "Label printing", allowing users to filter Shelf locations by range (from-to). It is still possible  to filter the column as before, by single shelf location number.

Label Layout (RTC-49013)

Layout for labels Maxi and Mini has been fixed: Maxi label has landscape orientation, Mini has portrait orientation.

Item details - Convenience columns (RTC-47231)

New buttons for managing food items: "Manage Ingredients," "Edit Recipe," and "Edit Menu item" are added. Each button navigates to a specific view where users can manage ingredients, recipes, or menus. Changes made from item details will be reflected in the respective grids. These features are filtered by convenience permissions to ensure appropriate access.

Released 8th of April 2025

Check digit control when importing GTINs (RTC-47797)

A new system parameter "Validate GTIN check digit on import" has been added. If the parameter is enabled, a digit check will be performed when importing GTINs (both main and alternative). If the Main GTIN does not pass the digit check, the import is rejected and the error "GTIN does not pass check digit control" is displayed. If the alternative GTIN does not pass, a warning "Some alternative GTINs won't be imported" is shown.

The digit check applies only to GTINs with 8 to 14 digits inclusive. The digit check is not performed if the GTIN is a PLU, starts with 20, or has more than 14 or fewer than 8 digits. These GTINs are considered valid.

If the "Validate GTIN check digit on import" is disabled, the digit check is not performed. Any GTIN can be imported, and the user can import GTINs as before.

"Managed by HQ" flag on item (RTC-48513)

A new flag, "Managed by HQ" has been added to the item column under Local item checkbox in item details and is set to false by default. This flag can be imported both via JSON and vie Excel. It is also exported to 3rd party in "Getaway.Item.Changes" blob and can be exported by the user. Only one flag can be set: either Local item or Managed by HQ, but never both. 

The import and export contracts have been extended with new value in Swagger, and the Item.Model table in the database has also been extended.

Related items - New relation types (RTC-47984)

New related item types have been added: Spare, Accessory, Replacement and Included. These types can be added to item via UI in related items section. The new types are supported in JSON import and are returned in the item API (GetItem). 

Available in Store, Phase in & Phase out - database + user interface (RTC-44552)

New store local attributes have been added at the store level: "Available in store" flag, "Phase in date" and "Phase out date". The attributes are independent of each other, and the user can add a column for any of these attributes in the grid or remove it. "Available in store" flag, "Phase in date" and "Phase out date" can be added to store, modified or deleted. there can be only one Phase In & Phase out date pair per item & store.

Additionally, the visual appearance of the grid for store local attributes has been updated. By default, those should be shown: store number, store name, tara, country of origin, shelf life, weight declaration, best before, self service weights, stop sale. The database has been extended with new attributes: "AvailableInStore", "PhaseInDate', "PhaseOutDate".

Price Sign A4 (RTC-47663)

Label Price Sign A4 can be assigned to items and printed. Triggers to create a new label are changes in label text, sales code and price or promotion price. Label can be printed manually from item details / item lists or added to Label list.

Characteristics of the label: 

Label is a size of the entire A4 page, with label text on top and sales code beneath it. Under the sales code there is price per unit if it exists. Below, adjusted to left side is the price or promotion price. If item is in promotion in member offer, text 'Klubprice' highlighted in light red is displayed above price. Promotion and ordinary price display differs in color - red for promotion and black for ordinary.

Languages of the texts on label are based on store from which label is generated.

Add default layout for labels (RTC-47884)

Each label has its own position (landscape or portrait), and this is already set in print view.

Fix: Display data in Shelf Label 4 and Streamer (RTC-48175)

Sales unit values appear correctly on all labels, and all relevant information is displayed accurately when printing from different views. . When clicking on link generated by QR code, user is redirected to correct destination site. 

Additionally, advertisement information, as well as other language-based fields are shown in the appropriate language, based on the store group’s country.

Import of item (RTC-47801)

When importing an item, it is possible to set a VAT code by providing the active rate. The import must specify a country code and either the VAT rate code or the active rate.

If a VAT code with the given rate already exists for the specified country, that code will be assigned. If no such VAT code exists, a new one will be created using the active rate as both the Code and Name. If a VAT code with that Code (e.g. 15.00) already exists in the database, a new code will be generated based on the active rate and the current date and time.

If the country code is not specified, importing using the code or active rate will default to the system's default country code.

Fix: Create price wrong time zone adjustment (RTC-48580)

Fixed formatting of ValidFrom in price calculation during price creation and update. It is possible to create prices for stores/store groups in different time zones in user interface.

Recipe items  (RTC-47023)

The system supports the automatic creation of ingredients from the content of recipe items.
Users can add ingredients and any other items to recipe. This process uses an ingredient made from the item with quantities set to 1. If the ingredient does not exist, it is created automatically without user intervention. A new ingredient is created if the ingredient exists but the chosen item is inactive, users do not need to perform any actions regarding the creation or usage of ingredients, but they can see the results in the ingredient grid.

Copy recipe item (RTC-47064)

Recipe item can be copied. It contains all the data of the original item, excluding prices, GTIN is created automatically. To do this in the recipe items view, simply select the item and click the Copy button. Since copying this type of item creates a new item, this option has also been added to the item grid. It is therefore possible to copy any existing item from the item grid using the copy button hidden in the additional functions for each line. Even then, prices are not copied. 

Ingredients (RTC-47818)

Gross and net weight fields are optional for ingredients. When a base item has a weight, it will be calculated automatically. If the base item does not have a weight, these fields will be grayed out, ensuring clarity and ease of use. This enhancement allows for better handling of ingredients that may be added in pieces without specific weights.

Fix for: Create new recipe item modal  (RTC-47911)

The modal header for creating a new recipe item got a new correct text which is: ‘New recipe item’.

Released 18th of March 2025

Convenience column in Item details (RTC-47227)

A new "Convenience" column has been added to the Item details. The values in this column are read-only. Items are categorized based on their usage:

• Ingredients display their names.

• Recipe items display their assigned ingredients

• Menu items show their menu groups.

If there are more than five additional details, a View all button appears. Changes in the ingredient, recipe, or menu grids update the Item details accordingly. For non-food items, a “Food item” checkbox remains unchecked and disabled.
Recipe items can also be used as ingredients, resulting in two types of food items.

Fix for: Scroll side panel in the recipe item and menu group (RTC-47952)

Scroll functionality to the side panels in both the menu group view and recipe item view is added, ensuring users can easily navigate through options when there are more items that can be displayed at once.
Item names in the Menu group are displayed in the language corresponding to the country selected as default, both in the side panel and within the group itself.

Grocery attributes on items - Export (RTC-47922)

When "Quantity in pallet" and "Genetically modified" attributes are added, updated or deleted in the item details, they are exported to 3rd parties, Getaway.ItemChanges blob. Also, user can export them by selecting in the "export to excel" view. Additionally, the export contract in Swagger has been extended with "Quantity in pallet" and "Genetically modified" attributes.

Fix: Timeout when adding missing item - store links (RTC-48288)

When adding or moving store to profile, item store links are created faster and processing many store links does not cause timeout.

Label printing timeouts (RTP-38111)

Opening Label printing view and filtering works faster and without timeouts.

Import Assortment code per price zone - contract (RTC-47803)

The contract in Swagger for import of items has been extended with 'StoreGroupLocalAttributes' with the following list of attributes: Assortment code, Warranty type, Id requirements, Sales purpose, Special group.

Manage local items permission (RTC-47359)

The "Manage Local Convenience" permission is added to the store role under items. A new "View Convenience" permission is introduced at a common level.

The existing "Convenience" permission has been renamed to "Manage Convenience", but it still controls the same actions for now.

Newly added permissions are visible in user management role user interface and can be exported and imported, but they are not yet used in the system.

Released 11th of March 2025

API for returning prices for given item (RTC-43350)

A new API request returns all undeleted prices for a given item in a store, including prices at private, price zone, and profile levels. If there are prices for the profile or price zone the store belongs to, those prices are also included in the response.

Request requirements:

• The body of the request must include one item identifier - SKU, GTIN, or External Item Number and the Store Number (required).

• If there is no match for sent item identifier and store number, then items are presented as empty square brackets.

• When sending request with identifiers connected to different items (in one pair of the brackets), item information for all those items will be returned.

ActiveOnUtc was removed from the request.

Leading zeros are removed when importing tandem GTIN (RTC-32182)

When importing tandem GTINs via Excel or JSON, any leading zeros are removed. This applies to both tandem and main GTINs. For existing items with leading zeros in tandem GTINs, the zeros are also removed to ensure consistency.

Ingredient base items (RTC-47132)

Users can add multiple base items to an ingredient, with only one base item being active at a time while the others remain linked but inactive. A new “Active flag “has been introduced, and all previously created ingredients, as well as those created via the user interface, are set to active by default.

When the active base item is changed, all associated recipe items are automatically updated to reflect this change, ensuring consistency. Changes to inactive base items do not affect the ingredient or its recipes.

Changes applied to the backend part, without the user interface, so for now the user cannot manage the multiple base items directly from the app.

Menu items overview (RTC-35324)

The menu items grid provides a structured overview of available menus. Clicking a menu opens a side panel showing linked menu groups, each containing a dropdown list of items and their add-on prices (if given). A "Number of items" field specifies the minimum required items per group, which can be zero but never negative.

Users can create new menus but cannot delete or deactivate menu items within this grid. Deactivated items do not appear. When opening the grid, the side panel remains collapsed for the first row. Access and actions in this grid depend on Convenience permissions.

Multicountry support for ingredients name (RTC-43349)

Ingredient names now support multiple languages. In the Add panel and Edit modal, text fields are available for all system-supported languages. A name must be provided for each supported language.

The ingredient name is displayed in the language of the default country set in the registry.

Label printing view sorted by main shelf location (RTC-46885)

The label printing view includes a "Main shelf location" column, which displays the main shelf locations. This column is hidden by default and must be added manually. Changing the main shelf location does not update the already created label.

The grid is sorted by main shelf location when available; otherwise, it sorts by item group.

Shelf label 4 Streamer (RTC-45340)

Shelf label 4 Streamer can be assigned to items and printed. A new label is created when there are changes to label text, advertisement info, sales code and price or promotion price. Label can be printed manually from Item details or Item lists or added to Label list. A QR code, generated from the system parameter , is included on the label.

Label layout:  

• Top: Label text 1, followed by advertisement info (overlapping text is cut).

• Middle: Sales code (left) and price per unit (right).

• Top right corner: Main shelf location for the store.

• Bottom right corner: Price, formatted according to store currency.

  • Highlighted yellow if the sales purpose field is filled.

  • Red font if the item is on Promotion without a sales purpose field.

• Bottom left corner: QR code with a side arrow and instructions for scanning.

The label language is based on the store where it is generated.

Country removed from ID requirement register (RTC-46080)

The “Country” column is removed from the ID requirement register. CountryCode is now nullable in the database and no longer in export.

Released 4th of March 2025

Store group level drop-down (RTC-47955)

All store group levels are displayed correctly in the dropdown when creating or updating the price (price calculation view)

Grocery attributes on item (RTC-47486)

The item details have been updated with new attributes. A new field, 'Quantity in Pallet' has been added to the 'Package' section. Additionally, a 'Genetically Modified' flag is now available in the 'Food' section. The 'Healthy' attribute has also been moved to the 'Food' section. Those fields can be updated via UI. The database has been extended with the 'Quantity in Pallet' and 'Genetically Modified' values.

Menu groups (RTC-34698)

Menu groups is newly added feature under the Food section called "Menu Groups." This allows users to view an overview of existing menu groups in a grid format. Users can create new menu groups or update existing ones. When adding new items to a menu group, users can specify an add-on price.
Users can see a list of items within each menu group, including their GTINs. Users also have the ability to edit the add-on price of items or delete items from the menu group.
Access to the view as in all food related things is managed by the convenience permission.

Fix: StagingBatchExecutor completed with warning during promotion import (RTC-46029)

The StagingBatchExecutor job execution finishes without warning when an offer is deleted.
Additionally, in other cases, if the job completed with a warning, more information is displayed to explain what happened and how to investigate it.

Released 26th of February 2025

Edit only sales price permission, when importing prices via Excel (RTC-43828)

A user with new "Edit only sales prices" permissions cannot update net price elements on item. if they attempt to do so, a warning "Some values will not be updated due to insufficient permissions." will be displayed in user interface and the net price elements will not be updated. However, such user can successfully update sales price elements without any warnings. Additionally, a user with this permission cannot create first ever price, whether it is an imported net price or sales price elements.

Note: Now, the "Price calculation" column is not required for updating/creating the sales price elements.

A user with "Create/Update prices" permissions can create/update prices as before.

Additionally: A user without any price permissions cannot update or create prices if the Excel file contains a Wholesale price column.

If a user without "Manage store local attributes" permissions uploads an excel file containing store local attributes and non store local attributes, non store local attributes will be updated, while store local attributes will be ignored.

Add 'Additional item' to Related Item/Convert to enum (RTC-46571)

"Upselling" is renamed to "Additional item" in the "Related items" section. Now, this section includes "Alternative" and "Additional item". It is also renamed in db in the ItemRelationType.

Additionally, the contract for relation type in Swagger is changed to enum for both file- import and file-export documentation.

Export to elastic based on promotion changes (RTC-46761)

When item gets an active promotion price, the data is exported with promotion sales price field to elastic. It happens when promotion is started, item is added to active promotion, planned promotion starts. Items removed from promotion or when promotion ends, are exported to elastic as documents without data on promotion price. If there is more than one promotion on item, one with current lowest promotion price is exported. 

In item search API effective price is promotion price or ordinary price, depending on which is lower. Fields 'effectivePriceFrom' and 'effectivePriceTo' help filter result items. To search only promotion or only ordinary prices, there is boolean 'isInPromotion' to use in request body.

Add shelf locations texts to Store local values contract (RTP-36368)

Contract for importing and exporting store local values was extended with 'shelfArea' and 'shelfType' properties in 'shelfLocation' section. Each property contain 'code' and 'texts' with localized names. Existing 'shelfAreaCode' and 'shelfAreaType' are marked as obsolete and importing those fields does not make any changes to shelf locations on item. New properties work in import.

Remove export 'wholesale prices' (RTC-43632)

The 'Export prices to excel' button has been removed from the item list and Item segmentation, only 'export items to excel' is available. After clicking the button, the user is redirected directly to the export to excel view. Additionally, the 'export to excel' button in the item grid no longer has any options, and the ability to export wholesale prices has been completely removed.

Searching item by sales code (RTC-46637)

Sales code is an exported to elastic search properly.  Adding, updating or removing sales code triggers export of item and changes are noted. It is searchable via API in 'fullTextQuery" field.

Edit only sales prices permission (RTC-43430)

New scoped permissions "Edit only sales prices" has been added. User with this permission can edit only sales price elements in the price calculation. Such user cannot create first ever price for a draft item. If there is no active price in the store (profile), an error "Could not find cost price for item" will be displayed. In a situation that user tries to change the price of the item for two stores at once, where one store has an active price and the other does not, an error message will be displayed. User with new permission can create a future price only if an active price already exists in the store.

Users with 'Create/edit prices' permissions can create and edit prices as before.

Food supplier (RTC-34916)

"Food production supplier" flag is added to the Supplier register. Column with this information is hidden by default but can be added to the grid from "+". Food Production Supplier flag can be Enabled/Disabled. The flag can be updated via Excel/JSON import and exported via Excel/JSON format.

Ingredients (RTC-46819)

Ingredients can be copied by using the button "Copy" hidden in the "..." option. Copied ingredient is automatically created with the same data as existed one and new ingredient no.

Fix: Creating an item with product features via RIGAL (RTC-46355)

It is now possible to create an item using the RIGAL file with a product feature. In the JSON file containing the product feature, the language code can be set as empty quotation "" marks. The file will be imported with the default country language.
At least one localization is required on item.

When importing a JSON file, item name must be present for the Language code. The model name should also be specified for at least one localization. When creating a new item, If the model name is missing in the JSON , it will be taken from the item name. A localization cannot exist without item text, label text1 or item receipt text. If these values are not present in the JSON, they will be taken from the item name.

All properties in the localized text can be edited. If they are not present in the JSON, those fields will not be changed. If the properties have values, they will be added or updated accordingly. If the properties have a null or empty string, those fields will be deleted. However, when such values ("null",empty string) are sent for the item name, the item name will be deleted only if the item has no additional properties, such as label text2, product features, advertise info or technical info. If these properties are present on the item, a validation error will occur.

The default country's language overrides the itemText (if it presents in the file) and will be applied to the item during import.

Fix: Filter deleted store prices in WholesalePricesChangesHandler in price suggestion job (RTC-47354)

PriceSuggestionProcessor is not failing and has the correct status with every execution (completed or completed with no effect). When there are deleted planned prices for profile level and new planned price is created, job processes only the not deleted price and updates 'children' prices accordingly with no duplicates. Additionally, created By for the 'child' store group's price is copied from the profile price, not from the active store price.

Fix: Shelf location is not editable (RTC-47392)

Shelf location number cannot be changed. It has been moved to the top and is now grayed out and non - editable.

Fix: Item hierarchy export contains all values ((RTC-46923)

When Item hierarchy is exported, all values are retrieved, including numbers and names for all hierarchy types and filled languages.

Fix: Supplier is exported to 3rd party when the address is corrected RTC-46635

When changes are made to the supplier's address, the supplier is exported to the 3rd party with the correct address data.

Fix: Console error while opening modal to edit value in the register ((RTC-43548)

Error does not appear when opening the edit modal in the item registers.

Item/GetItemsByItemIdentifiers API RTC-47295

FIX: Endpoint now works correctly instead of returning 404 NOT FOUND.

Fix: Search indexing timeout (RTC-47426

Export of item changes to elastic search is much faster an does not cause timeout of SearchIndexing job.

Fix: Add support for cancelling SearchIndexing job ((RTC-47470)

More informative logs were added to SearchIndexing job, with information on amount of changes processed and documents sent to elastic. Additionally when execution of a job is cancelled, by for instant restart of integration package, job is resumed in correct place when package is up and running.

Return prices for given item (Contract) (RTC-46913)

A new contract for an API request has been added in Swagger, which will return prices for a given item. It is a POST api/gateway/Items/GetOrdinaryPrices request. The request body must contain the required parameters:  ItemIdentifier, StoreNumber and 'activeOnUtc' (datetimeoffset).

Released 5th of February 2025

Import from 3rd party store local GTINs on items (RTC-43898)

A GTIN can be imported from 3rd party on item by specifying the store identifier and setting attemptToSaveAsCommon flag to True or False in alternative GTINs section. If the flag is set to False, the GTIN will be imported on store level as a store local GTIN. The same GTIN can exist for different items and different stores, as well as being a common GTIN for one item and a store local GTIN for other items. If the imported GTIN exists on different item within the same store, it will be 'stolen' by the imported item.

When the flag is set to True, and the GTIN does not exist on another item or exists on store level, the GTIN will be added on common level. If it exists on common level, the GTIN will be added as store local GTIN for the imported item.

It is not possible to set store local GTIN as the main GTIN. If isMain flag set to True and a store identifier is provided, an error message will be displayed. When creating a new item, only common GTINs are considered. If the GTIN sent in the file exists on the store level, it will not be found, and a new item will be created instead.

Display and export to 3rd party (RTC-43897)

GTINs added per store are supported and GTIN table in database is extended with store identifier. In Item details, manage GTINs view there are visible GTINs that are added per store on item. Store related columns are added to the grid and it is possible to filter on them. Contract to export local GTINs to 3rd party in Gateway.ItemChanges blobs is extended and store identifier is added to GTINs section. 

It is possible to have the same GTIN set per different items and different stores, as well as the same GTIN set as no local GTIN on one item and local GTIN on other item.

Shelf label 4 (RTC-45327)

Shelf label 4 can be assigned to items and printed. Triggers to create a new label are changes in label text, advertisement info, sales code and price or Promotion price. Label can  be printed manually from Item detail/ Item lists or added to Label list. On the label there is QR code generated from system parameter.

Look of the label: 

On top of the label there is label  text 1, beneath it advertisement info and overlapping texts are cut. Below there is sales code, price per unit and information if price is a Promotion price. In top right corner there is main shelf location. Price is located at the bottom left and is displayed differently for different countries of stores (currency and pennies).  Price is highlighted to yellow when there is sales purpose field filled out, as when item is in Promotion without that field it is written in red font. In left bottom corner there is QR code.

Languages of the texts on label are based on store from which label is generated.

Fix: Adding shelf location does not trigger export to 3rd party (RTC-47063)

When adding or updating shelf location on item, blob Item.ItemStoreOverride.Export is triggered to export and contains correct data. It is exported both when there were no previous stor local values on item and if there were already.

Fix: Look of the grid and warnings (RTC-46253)

When an existing shelf location is assigned to an imported item, and shelf area and/or shelf type are not provided in the file, there is no warning displayed to the user. However, when creating a new shelf location, if the shelf area and/or shelf type are not provided in the Excel file, a warning will be displayed.

In the shelf locations grid, the first column with plus is fitted to icons width.

Extend exchange rate precision (RTC-46905)

It is possible to create or update currency rates with values with up to 6 decimals. Exchange rates can be created both via UI and import. When adding rated via UI there is validation allowing only 6 decimals, while via import values longer than 6 decimal will be cut and rounded to 6 decimals, correctly saved in database and exported to 3rd party.

Released 23th of January 2025

Text in confirmation dialog in Export view (RTC-46127)

When exporting entities other than item, the header and text inside the confirmation dialog are changed according to the exported values. The text on the button and Export page title is "export" instead of "Export item". Also the names of the entities in the left menu change according to the selected language.

Export image to elastic (RTC-45693)

Image Uri is exported to elastic search in the "thumbnailUri" field.  Exported value is the image with the thumbnail role or if there is no role then the first image saved on the item will be exported.

Export image Url’s (RTC-45177)

Image Url’s are exported with the role to the gateway.itemchanges blob type. Images are exported with the same order as in the import file.

Fix: Exception when merging duplicated items between models (RTP-35403)

When moving items between models in import, if duplicated items are moved - on result model there already exists item with same same color/size, items are merged into one and last imported GTIN becomes main GTIN, rest is alternative. The same happens when similar items are moved from multiple models or are created via import.

New index in elastic (RTC-43832)

Items, which are connected to store via item-store link are exported as documents to Elastic Search. One document is an item per store. Items in elastic are updated whenever item changes or ordinary price is updated. Changes of price affect only document regarding relevant store group, while changes on item affect all stores item is active in. Creating price on higher store group level, such as profile or price zone will result in exporting as many documents as there are stores (on condition that item-store links are added).  Removing item-store link results in removing document from elastic. When future price becomes active, price in elastic is updated accordingly.

New search API (RTC-43022)

A new search API  /api/gateway/Search/items used to filter items is added along with a contract that allows the user to search by the fields placed in them. All the necessary information about the available fields and their operation is presented in the swagger contract schema.

Shelf locations assigned to item (RTC-42790)

In user interface, in Item details there is a new section called 'Shelf location' where assigned shelf locations are displayed. User can enter Manage shelf locations view by clicking on accordingly named button. In this view, it is possible to add shelf locations to item, by selecting correct shelf location in the 'Add panel'. Required fields are store and shelf location, but for the shelf location dropdown to be visible, store must be selected first. User can set shelf location as main and delete them from item. When deleting main shelf location, if there is any other shelf location for the same store, it will be set as main. Actions and visibility of data is limited by 'Manage' and 'View store local attributes' permissions.

Manage item in shelf locations (RTC-45394)

The user can enter the shelf location where the items assigned to it are displayed. Using the Add panel located at the top of the view, it is possible to add an item to the shelf location in which the user is currently located. To do this, just search for the item and after selecting it, it is automatically added. It is possible to remove an item from a shelf location using the option located in the line with the item, or to remove all items from a given shelf location using the option located in the lower right corner of the view. Before deleting all items a warning message is displayed, which the user can confirm or cancel the action.  The other shelf numbers column contains the numbers of shelf locations to which the item is assigned within one store. Many additional numbers can be displayed as a comma-separated list. It is not possible to filter this column.

Fix for: Inactive stores are not available in active store assortment (RTC-45505)

If the store is inactive, it is not available in the dropdown when adding items to the active assortment.

Store local values API (RTC-31805)

There is a new API request which returns store local values. The request body must include a store identifier (storeNumber) and an item identifier (itemIdentifier - GTIN). It is possible to send multiple items in the request by placing identifiers in separate brackets and separating them with comma, but there can be only one store in request. In the response, there will be present data on all items matching identifiers. If there is no match for sent item identifier, then values are presented as empty square brackets.

'Values per profile' system parameter (RTC-46076)

A new system parameter has been added to the "Other settings" section regarding values per profile. There is a question displayed "Would you like to define warranty type and ID requirement per profile?". It is possible to set the value to true/false using the checkbox. By default, it set to False.