Offer deleted on status planned (RTC-42666)

Export of promotions and offer items contain data from offers deleted not only on status 'Active' but also 'Planned'. In database, there is 'IsDeletedWhileApproved' flag instead 'IsDeletedWhileActive'.

VAT rate decimals (RTC-43453)

When item price has decimal value as a VAT rate, it is saved with no rounding on offer group item row. As a result, Margin (GP) and Promotion price WO/VAT are correct in price panel.
For existing offer group items with incorrect VAT rate, it is needed to re-add item selection to the offer (to trigger update of ordinary price used in offer group item row).

Fix: order of fields in export of promotion to blob (RTC-42404)

In Promotion.Promotion.Export offers, 'mixType' is first field in 'mixDetails' entity (to ensure backwards compatibility with old package versions).

Deleted offers (RTC-39591)

Offers deleted before approving promotion are not exported. The same for offer items from such offers.

Promotion and offer item, logs (RTC-39974)

No exception is thrown when importing not existing promotion with status 'deleted'. Such promotion is skipped in import. Log about failed offer item import contains information about external offer number, offer item identifier and flat batch JSON id.

Show offers as grid (RTC-40576)

The user can display offers as a list (by clicking 'Show offers in a grid') or as cards ('Show offers as cards'). The first view is a grid with the following columns: offer id, offer name, price rule, active, incomplete, coupon offer, external offer id, coupon offer id, member offer and bundle offer. Incomplete offer means that mix details are not defined correctly or offer doesn't have items. In the second view, in which user can view offers as cards, 'Active offers' filter is renamed to 'Active and complete offers'. When trying to submit or confirm promotion with incomplete offer, validation message contains identifiers of incomplete offers. When the user enters the details of the promotion, sees the offers as cards by default. Then, offer view type (grid or cards) selection is remembered in browser - after entering any promotion, page in lastly used offer view type is displayed.

Number of times the offer can be used in coupon offer (RTC-39868)

'Number of times the offer can be used' value is editable in offer or displayed as defined in price rule regardless of whether offer has coupon added or not. Removed 'Once per unique coupon' text that was previously displayed as value when offer had added coupon.

Get requests for promotions and offers (RTC-41205)

GET requests in Promotion Service are supported:

• get promotion by external promotion identifier
  /promotion/?externalNo=[ExternalPromotionIdentifier]
• get promotion by internal promotion identifier
  /promotion/[EgPromotionIdentifier]
• get promotion offer by external offer identifier
  /promotions/[EgPromotionIdentifier]/offers/?externalNo=[ExternalOfferIdentifier]
• get promotion offer by internal offer identifier
  /promotions/[EgPromotionIdentifier]/offers/[EgOfferIdentifier].

Authorization token is required. If promotion or offer is not found, 404 (not found) status code is returned. If no identifier is specified, 400 (bad request) status code is returned. When fetched offer belongs to another promotion than specified by promotion id, 400 (bad request) status code is returned. Incomplete offers (with missing mix details fields) are returned with default values.

Promotion API documentation in Swagger (RTC-41203)

Contracts for Promotion API endpoints are documented in Swagger:

• Put upsert promotion,
• Get promotion by external promotion identifier,
• Get promotion by internal promotion identifier,
• Put upsert offer to the specified promotion,
• Get promotion offer by external offer identifier,
• Get promotion offer by internal offer identifier,
• Put upsert items to the offer.

OfferGroupProcessor job replaces ItemSelectionItemImport job (RTC-37763)

Items are added to the offer group by OfferGroupProcessor job. Compared to ItemSelectionItemImport, item and prices lookup is done in Promotion database instead of requests to Item Service API.

When item, model or variant that is part of selection is not found in Promotion database, then job completes with warning. Processing is retried 3 times (each 10 minutes by default).
Import of items to single item offer groups (mix type 4 and 5) supports GTIN and ExternalItemNo.
When creating offers on model or variant level, the selected item from the model/variant must have an ordinary price.

Performance of promotion approval (RTC-39966)

Improved performance of approving promotion, editing approved promotion, update of promotion through 3rd party import.

Fix: offer trigger code (RTC-41748)

When creating new offer with voyado coupon, offer id is saved as offer trigger.

Coupons on offers (RTC-41435)

When only one offer trigger type can be selected (for offers created by third party import) or if previously selected offer trigger type cannot be changed, radio buttons are not displayed in the offer details view.
Fix: User can change coupon offer for offer imported from third party.

Documentation (RTC-39713)

Mix types are visible in contract schema for promotion.

Discount code (RTC-41528)

The discount code field (named offerTriggerCode in import) can have up to 30 characters.

External identifiers in export to blob (RTC-24502)

ExternalPromotionNo/ExternalOfferNo are exported as ExternalPromotionNo/ExternalOfferNo in export of Promotion.Promotion.Export.

Import of offers with mix 101 (RTC-39061)

Offer with mix type 'PromotionDiscount' (mix 101) can be imported from 3rd party or from Excel file. It is marked as supported in the Swagger documentation. Excel with offer items exported for mix 101 offer contains 'Promotion discount' column. When uploading Excel, promotion discount field is ignored for offers using mix other than 101. When exporting Excel for mix 100, the 'Promotion net price' column is no longer present in the file.

One item offer group validation rule (RTC-39736)

Removed SKU validation for importing items to offers with single item (no error message when import contains only GTIN or ExternalItemNo). Note that such item will still not be added to the offer (for now SKU must be defined when importing item to one item offer group in mixes 4 and 5).

Coupons on offers (RTC-38665)

ExternalCouponId is obsolete in import. If provided, works as before but OfferTriggerType and OfferTriggerCode must be null then. ExternalCouponId has value of OfferTriggerCode in export.

Possible values for OfferTriggerType:

• 'DiscountCode' ('General coupon' in UI),
• 'Coupon' ('3rd party integration coupon' in UI),
• 'Standard' (no 'Coupon offer' in UI).

'Coupon' is not supported in import. 'OfferTriggerCode' must be specified when OfferTriggerType is 'DiscountCode' and must be null if OfferTriggerType is 'Standard'. If OfferTriggerType and OfferTriggerCode are not specified, we have 'Standard' offer without coupon.

Import of offers with mix 26 (RTC-39131)

Offer with mix type 'SubtotalDiscount' (mix 26) can be imported from 3rd party. It is marked as supported in the Swagger documentation. Offer items cannot be imported for such offers (this mix type affects all items).

Import of offers with mix 4 (RTC-39034)

Offer with mix type 'DiscountOnWeightItem' (mix 5) can be imported from 3rd party. It is marked as supported in the Swagger documentation. Only a single item can be imported to such offer (with logic as in mix 4).

Import of offers with mix 4 (RTC-39035)

Offer with mix type 'BuyOneItemFromSelectionAAndGetDiscountOnItemB' (mix 4) can be imported from 3rd party. It is marked as supported in the Swagger documentation. When importing PromotionOfferItem for the offer, selection to which item should be added can be specified using OfferItemType field: 'Condition' and 'Reward'.
Only a single item can be imported to 'Reward' offer group of offer using mix 4 - for each import to 'Reward' group, only 'newest' item (based on created date) is added to offer (new imported item removes previous one, and only item from last line is added if there are multiple in one file).

Import of offers with mix 28 (RTC-39033)

Offer with mix type 'discount on selected items' (mix 28) can be imported from 3rd party. It is marked as supported in the Swagger documentation.

Fix: Edit external offer without coupon (RTC-39449)

It is possible to save changes when editing an offer that was created from 3rd party, without the need to touch 'coupon' checkbox.

Choose type of coupon (RTC-38615)

When tenant is not configured to use Voyado integration, coupon can be added as before.
When tenant is configured to use Voyado integration, user can choose type of coupon creating new or editing existing offer. When '3rd party integration coupon' chosen, offer is created in Voyado. This type of coupon cannot be changed or removed once created. '3rd party integration coupon' cannot be added for offer that was created by import from 3rd party. User can now also choose 'General coupon'. In this option, coupon can be defined by input field, same as when not configured to use Voyado. This coupon can be removed or replaced by 3rd party one.
Coupon input field now allows text, no spaces, and maximum of 10 signs. Validation is changed in import of promotions from 3rd party as well.

Mix 101: Promotion discount (RTC-38232)

There is a general discount on whole offer which can be defined in price rule or editable in offer. In items in promotions view it's possible to adjust promotion discount per item.

Export documentation (RTC-38276)

Swagger contains documentation regarding export of promotions, available mix types and examples of Promotion and PromotionOfferItem exports for various offers and offer items.

Import of prices (RTC-37762)

All item prices from Item Service are imported to Promotion database by new ItemPriceMerger job.

Import of item groups (RTC-38300)

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

Access control - copy offer, copy promotion (RTC-30144)

Both 'Copy promotion' and 'Copy offer' buttons are visible when user has access to manage any store or store group.

Performance of active promotions in user interface (RTC-39251)

Improved performance of approving promotion, editing and stopping active promotion in user interface (fix related to marking offer items to be exported).

Import of items (RTC-37761)

All item changes from Item Service are imported to Promotion database by new ItemMerger job. Items are saved in table that already contained items that were part of offers. When useModelItems=true, for each imported item, variant and model level rows are updated (they are used for offers on those levels). When useModelItems=false, only item rows are created.

Description of changes, history, info about changes exported to POS (RTC-36677)

Information for planned promotions that changes will be immediately exported to POS is visible when editing promotion or offer details and when managing items. Description of changes are required. There is a note in the history section after creating promotion, adding and copying offer, updating promotion or offer details and after managing items.

Mix 104: Buy from group 1, get discount on group 2 (RTC-35721)

Fields to define in this mix type are:

• Reward - Discounted price

Offer with mix type 104 has two offer groups. Rules: buy from group 1, get discount on group 2. Discounted price for group 2 can be editable in offer or defined in price rule. When creating a new offer with this mix, always two groups are created with quantity 1. Mix details for offer using mix 104 are properly exported.

Documentation for mix 101 'Promotion discount' (RTC-37334)

Business rules, import example and schema is added for upcoming mix type 101 - Promotion discount (mixType: PromotionDiscount in Promotion import and PercentDiscount value added in PromotionOfferItem import).
Import of this is not yet supported.

Fix: Promotion Price update (RTC-38292)

Excel and 3rd party imports support update of Promotion Price value. Change of this value result in export of updated order line to blob.

Performance when adding items to the offer group (RTC-37691)

Added database index to improve performance when adding items to offer group. Size of batch that is saved to the database is set to 2000 by default and can be changed using parameter in configuration of ItemSelectionItemImport job.

Export only changed rows after recalculation (RTC-36798)

After item selection update (e.g. after segmentation recalculation at night), only rows with changed values are exported. This increases the promotion update performance from Promotion module to POS.

Promotion grid side panel (RTC-37256)

Side panel in promotions grid is closed by default and its state is saved in local storage.

Fix: Promotion exported before PromotionOfferItems (RTC-36675)

In every blob export situation, the active/planned Promotion is exported before PromotionOfferItems.

Fix: Add segmentation to offer through 'Edit offer' page (RTC-34391)

Offer processing is started properly after user opens 'Edit offer' page, clicks 'Manage items' and creates new segmentation.

Fix: ItemSelectionItemImport (RTC-36697)

ItemSelectionItemImport is not stuck when processing the offer groups. This could happen before in some special cases.

Fix: Exception handling (RTC-35478)

Apart from the exception in the database and log in the Integration Platform, the execution of job is 'Completed with warnings'.

Fix: Missing items in export after approval of promotion (RTC-36216)

All offer items from all offer groups in promotion are included in export execution after promotion approval is finished. Before this fix, some items could be missing from export due to approval request being handled at the same time as the export job was running.

Mix 40 (RTC-34083)

Offer with mix type ''Combine from groups and get collective discount" (mix 40) can be imported from 3rd party. It is marked as supported in the Swagger documentation. Import of discount on offer level is not supported.

Fix: Add segmentation to offer through 'Edit offer' page (RTC-34391)

Offer processing is started properly after user opens 'Edit offer' page, clicks 'Manage items' and creates new segmentation.

Fix: Segmentation recalculation in night (RTC-35260)

During night recalculation of active offers, existing segmentations are recalculated and unnecessary copy of segmentation is not created.

Parameter for ItemSelectionItemImport (RTC-35197)

There is a parameter 'Timeout per offer group (in minutes)' with default value equal to 60 min. After this time offer group with problematic segmentation is skipped but other groups are processed.

Performance improvement (RTC-35199)

Improved performance of export job to prevent its failure, especially in case of re-exporting all offer items to POS.

Offer items from deleted offer group (RTC-35136)

After removing offer group, items from this group are exported with status 'Deleted'.

Logs and fix of offer items export (RTC-35802)

Export job executions (Promotions and PromotionOfferItems) save logs with row versions that are exported as well as number of exported rows.
Missing rows export of offer items is fixed (bug in comparison of row versions to be exported).

Deleted offer group (RTC-35136)

There is no validation message after import of promotion as JSON file with offer group which have 'Deleted' status, when this group was already deleted before.

Mix 35/41 (RTC-34082)

Offer with mix type 'combine from groups and get discount per group' (mix 35/41) can be imported from the 3rd party. It is marked as supported in the Swagger documentation. If the mix has several groups and we provide not unique identifier, there is validation.

Offers with mix 21 (RTC-34080)

Offer with mix type 'Import of buy N selected items and get a discount' (mix 21) can be imported from 3rd party. It is marked as supported in the Swagger documentation.

Faster filtering and search (RTC-34087)

Fetching data and filtering for 'Items in promotions' page for offers (grid for item level and for item group level offers) is faster. Sorting on status, store group code, store group name, period overlaps columns in grid for offers on item level is not possible.

Fix: Adding hundred thousands of items to offer (RTC-35572)

Reduced page size when fetching items and prices from Item Service to avoid errors when item list or segmentation contains hundred thousands of items.

Export after update from 3rd party import (RTC-34351)

Promotion is exported properly after offer is added to existing promotion or updated through 3rd party import. Offer items are always exported after such import as well.

Performance of export of offer items (RTC-30142)

There is no timeout when there are many offer item changes exported (e.g. after approving promotion with 100+ thousands of items or manually re-exporting all promotions to POS with SQL script).

Import file with thousands of rows (RTC-34237)

StagingImport job does not fail when one imported file contains over 4000 of JSON rows.

Documentation for mix 10/13/39 (RTC-34227)

Business rules and import example in Swagger are added for 'Buy N or more items and get a discount per piece' mix type.

Access control - filter promotions in grid (RTC-14422)

In Promotions grid user sees only those promotions for which he has access to view (e.g. promotions in this store, but also profile and team promotions of store for which he has permission and profile promotion of store from team for which he has access etc). When copying offer, list of promotions show only those to which he has manage permission.

Model name (RTC-33204)

Model names with up to 255 characters are correctly stored in the Promotion database.

Database compatibility level (RTC-32039)

Compatibility level on databases is set to 150.

Fix: Remove unnecessary "Save changes" dialog (RTC-32922)

Dirty modal does not appear if the user wants to go to the previous view and has not edited offer details / price rule. It's also not visible when leaving offer details / price rules which are in read-only mode.

Fix: ItemSelectionItemImport job logs (RTC-33069)

ItemSelectionItemImport logs contain number of items added to offer group and items with no prices. Example: 'Offer groups with succeeded state (offer group id (items with prices / items with no prices)): 1234 (5/1)'. At the end of each section containing information on a single segmentation/list is such message: 'Offer group processed: 0 items and 1 item without price.' Above messages are visible only for groups that were processed 10 seconds or longer and their processing was successful. If the job has status 'CompletedWithWarnings', the user sees the text 'Offer groups with failed state: 1234'.

Number of times the offer can be used if 'Coupon offer' checked (RTC-28451)

When 'Coupon offer' checkbox is selected then 'Number of times the offer can be used' input is replaced with text 'Once per unique coupon'. Reuse condition is saved in database based on previous values and price rule settings. If ' Number of times the offer can be used' is editable in offer and the user does not enter a value and select 'Coupon offer' checkbox, the value 1 is saved in the Promotion database. Regardless of value in Promotion database, in POS the coupon offer is treated as 'Once per unique coupon'.

Offer items

Process manually updated offer groups before externally imported ones (RTC-32502)

ItemSelectionItemImport job (responsible for adding items into offer groups) first process changes triggered in user interface and then changes triggered by external import of JSON file. When there is ongoing import of items, and user adds items to some other offer group using user interface, this offer group is first in processing queue so user does not need to wait till import of data is finished.

Upgrade to LibBackEnd 5.4.0 (RTC-33205)

LibBackEnd updated in order to support notifications and Azure SignalR.

External model number (RTC-32735)

'External Model Number' is added as column in the 'Items in promotions' grid in item view and in the offer group items grid. New column appears when an item list or segmentation at item, variant or model level is added to an offer group. This is visible by default only on model and variant level. Column cannot be shown when tenant is using non-model items (system parameter). 

Fix: no duplicates of items (RTC-33160)

Fixed issue in ItemSelectionItemImport job, which caused duplicated item rows in Promotion database after adding non-model item to offer on variant level (then such duplicates were added to offers anytime when adding such SKU to offer on any level).
During release, existing duplicates are removed. Unique indexes added to prevent duplicated items in future.

Performance of adding items to offer group (RTC-32248)

Improved performance of adding items to offer group. Improved performance of fetching data for 'Items in promotions' page.

Database maintenance job (RTC-32287)

There is a 'PromotionServiceJanitor' job in PromotionIntegrationPackage package. By default, in runs once every night. If there were any changes in database, it rebuilds index on tables in Promotion database. This results in a reduction of the database size and improves performance of external data processing.

Integration job cancellation (RTC-32247)

Integration package has a handling for cancellation of job (e.g. during package restart).

Fix: Segmentation in offer on model/variant level (RTC-28577)

Offer group items are added on item, variant or model level according to what was selected in modal when adding new segmentation to offer/ editing segmentation used in offer.
When creating new offer, there is possibility to choose selection level in new modal after selecting existing segmentation from the list.

Item lists' 'browse by' variant is remembered and used when adding item lists to promotion.