Page Contents

25 January 2022 (8.11.1)

Admin Orchestration Service

The following new features or enhancements have been implemented in the Admin Orchestration service for this release:

  • The issue of not displaying PLP/PDP promotion messages in the React or SFO layer for the promotion with batch purchase quantity has been resolved. [SECOM-53892]
  • The display of 500 error page when saving a promotion has been resolved. [SECOM-53893]
  • The issue of not displaying the Customer subscription details in the Subscriptions tab of the Customer Admin console has been resolved. [SECOM-53883]

Loyalty Service

The following new features or enhancements have been implemented in the Loyalty service for this release:

  • Ability to block/unblock earning loyalty programs. [ECS-388]
  • Ability to block/unblock loyalty redemption points. [ECS-391]
  • Ability to enable/disable the Reward Approval process. [ECS-390]
  • Ability to enable/disable the manually add earning points.
  • Ability to add transaction details. [SECOM-44458]

Security and Performance

  • Apache Log4j2 versions 2.0-beta7 through 2.17.1 have been updated in the respective JAR files and deployed on the Cloud environment. For more details, see https://logging.apache.org/log4j/2.x/. [ECS-513]

Storefront Orchestration Service

The following new feature or enhancement has been implemented in the Storefront Orchestration service for this release:

  • The issue of up-sell and cross-sell products not loading in the orchestration’s PDP API call, even after configuring in the admin has been resolved. [SECOM-53881]

Technical Improvements

The following technical improvement has been implemented:

  • ​The issue of invalid cache data while accessing more than one DNS in the Cloud environment has been resolved. Currently, all the top categories are loaded and displayed. [SECOM-53888]

30 December 2021 (8.11.0)

Release Changes for Infosys Equinox Commerce Microservices

Accounts Service

The following new features or enhancements have been implemented in the Accounts service for this release:

  • Ability to update account properties using the “Create or Update Contract Properties” API (PUT call). For more information, see Accounts API End Points. [SECOM-49612]
  • Ability to bulk update the contract properties. [SECOM-50110]
  • Ability to publish the accounts data from the authoring environment to the production environment. [SECOM-51080]
  • Ability to configure pricelist or price rule for a contract. [SECOM-48850]
  • A new Account Delta feed has been implemented. [SECOM-51898]

Catalog Service

The following new features or enhancements have been implemented in the Catalog service for this release:

  • Ability to manage sales catalog rules based on “SKUs”. [SECOM-49595]
  • Ability to provide duplicate sequence values for attribute groups. [SECOM-50549]
  • Ability to configure an attribute as “comparable” or “displayable”. [SECOM-50094]
  • Ability to support special characters (such as !@$&()-_:{}/.*=space) have been provided in the Product or SKU ID. [SECOM-50003]
  • Ability to download a sample sheet for importing model values for “model by template” attributes. [SECOM-49902]
  • Ability to configure sales catalog rules based on the “OR” condition along with the “AND” condition. [SECOM-49901]
  • Ability to publish an entire store or the collections associated with a store for B2B or B2C. [SECOM-49743]
  • Ability to choose Default or Filter type of catalog while creating a sales catalog. [SECOM-50942]
  • Ability to filter and view based on the type of the sales catalog such as Default or Filter using the “Find All Products API” in Product Controller and “Find All SKUs API” in SKU Controller. For more information, see Catalog API Endpoints. [SECOM-50942]
  • Ability to display a summary of catalog publish based on history ID. [SECOM-51500]
  • Cache support for version tables has been provided. [SECOM-51499]
  • Ability to update record count on running the Catalog feed. [SECOM-51496]
  • Added support to the Model and Model_value entities, in the full, incremental, backup, and rollback functionalities. [SECOM-51076]
  • Ability to import and/or export model values for “model by template” attributes. [SECOM-50478]
  • Ability to skip project approval workflow in the Catalog. [SECOM-50104]
  • The Filter type Sales Catalog functionality has been enhanced as follows: [SECOM-51734]
    • Ability to navigate to the Products and SKUs details page from the Product/SKU listing page.
    • Ability to view only the associated SKUs that belong to the specific catalog filter for a Product.
    • Ability to update or delete only the catalog rules.
  • The Delta publish feature has been introduced in the Search service for incremental support. [SECOM-51730]
  • Ability to use the “backup and restore” option to publish SOLR data. [SECOM-51729]
  • Ability to generate an error file if SKU or product is invalid or empty. [SECOM-52440]

Feed Service

The following new features or enhancements have been implemented in the Feed service for this release:

  • Ability to support price rules-based indexing in storefront’s product indexer feed for B2C. [SECOM-48858]
  • Ability to accept “0” as a price value for Transaction Price, Subscription Price, Price Type, Bundle Price, and Floor Price. [SECOM-50450]
  • Fallback support for price rules has been provided in the Feed service. [SECOM-51187]
  • The publish master feed calls all the applicable publish feeds (such as Foundation, Catalog, Price, Merchandising, Search, and/or Accounts), and displays the feed run result.
  • The price feed “PriceruleEventListener” has been implemented for B2B & B2C. [SECOM-50153]
  • Support for special characters (such as !@$&()-_:{}/.*=space) have been provided in the Product or SKU ID. [SECOM-50003]
  • Ability to view the prices of products based on a price rule. [SECOM-50872]
  • Price rules support for Special Products (SKU-Kits) has been provided. [SECOM-50871]
  • The price_rule_config entity has been added to full or delta publish the pricing data. [SECOM-52213]
  • Ability to update record count on running the Merchandising feed. [SECOM-51497]

Merchandising Service

The following new features or enhancements have been implemented in the Merchandising service for this release:

  • Ability to update record count on running the Merchandising feed. [SECOM-51497]
  • Ability to publish the merchandising data from the authoring environment to the production environment. [SECOM-51077]
  • Support for enabling or disabling the project approval workflow has been provided in the collection property. [SECOM-50103]

Pricing Service

The following new features or enhancements have been implemented in the Pricing service for this release:

  • Added a new POST API to create a multi-price for creating or updating a list of prices. [TMOBCAT-46]
  • Ability to create and manage price rules which involve the application of different price adjustments like mark up, markdown, and rounding-off options for different conditions. [SECOM-48854]
  • Ability to configure a list of price rule conditions in a collection property “pricerules_config”. [SECOM-49898]
  • Ability to accept “0” as a price value when the collection property “allow_zero_pricing” is enabled. [SECOM-50613]
  • Ability to publish the pricing data from the authoring environment to the production environment. [SECOM-49743 and SECOM-51078]
  • When a price is not returned for a product, SKU, or special products (SKU-Kits) based on a price rule, the price is retrieved from the default pricelist that is associated with the store. [SECOM-50873]

Search Service

  • Ability to retrieve the prices of a SKU based on the price rule. [SECOM-48859]
  • When a price is not returned for a product, SKU, or special products (SKU-Kits) based on a price rule, the price is retrieved from the default pricelist that is associated with the store. [SECOM-50873]
  • Ability to view the prices of products based on a price rule. [SECOM-50872]
  • Price rules support for Special Products (SKU-Kits) has been provided. [SECOM-50871]
  • Ability to create indexes for product attributes such as searchable, sortable, and filterable in the CatalogB2BEventlistener feed. [SECOM-51481]
  • Fallback support for price rules has been provided. [SECOM-51185]
  • Ability to publish the search data from the authoring environment to the production environment. [SECOM-51079]
  • Support for special characters (such as !@$&()-_:{}/.*=space) have been provided in the Product or SKU ID. [SECOM-50231]
  • Support has been added for persistent messages in the queue whenever RabbitMQ is restarted. [SECOM-52434]

Promotion Service

The following new feature or enhancement has been implemented in the Promotion service for this release:

  • Ability to fetch offers when matching promotion condition is configured with the minLines and/or maxLines in the Actions section. [TMOBCAT-202]

Storefront Orchestration (SFO) Service

The following new features or enhancements have been implemented in the Storefront Orchestration service for this release:

  • As part of the ticket [SECOM-48860], a storefront’s guest or registered user can:
    • View the prices in PLP, PDP, Cart & Checkout for SKUs based on the price rule.
    • Obtain prices based on the conditions configured in the price rule based on user property or reg/guest user flows.
    • Filter the products based on the default price, which is based on the pricelist associated with the store.
  • When a price is not returned for a product, SKU, or special products (SKU-Kits) based on a price rule, the price is retrieved from the default pricelist that is associated with the store. [SECOM-50873]
  • Ability to view the prices of products based on a price rule. [SECOM-50872]
  • Price rules support for Special Products (SKU-Kits) has been provided. [SECOM-50871]
  • Support for special characters (such as !@$&()-_:{}/.*=space) have been provided in the Product or SKU ID. [SECOM-50232]
  • A common session in the storefront for all the browse APIs without needing to create a guest user for a request from each browser. [SECOM-52779]

Customer Service

The following new features or enhancements have been implemented in the Customer (User) service for this release:

  • A new collection property “password_expiry_days” has been introduced to set password validity (in days). [SECOM-52780]

Release Changes for Infosys Equinox Commerce Admin Console

Accounts Admin

The following new features or enhancements have been implemented in the Accounts Admin console for this release:

  • Ability to set default values and sequence for the attributes as an account admin. Allows the attribute to be listed based on sequence within an account/contract. [SECOM-49486]
  • Ability to configure pricelist or price rule for a contract. [SECOM-48850]
  • Ability to define the start time and end time in addition to the start date and end date for creating or editing a contract. [SECOM-50629]
  • Ability to enter custom properties (Attributes) for contracts. [SECOM-48773]
  • Ability to enter a contract name. [SECOM-48773]
  • Ability to associate a price rule to an account via a contract. [SECOM-48850]
  • Ability to enter the name of the contract, associate a pricing method and select the required pricelist or price rule. Previously, only the pricelist was part of the contract. [SECOM-48773]
  • Ability to list entity names along with an ID for pricelist or price rule, catalog, site navigation of Merchandising. [SECOM-50828]
  • The message property files have been updated appropriately for multi-language support. [SECOM-50728]

Catalog Admin

The following new features or enhancements have been implemented in the Catalog Admin console for this release:

  • Ability to clone a sales catalog. [SECOM-51742]
  • The following issues have been resolved as part of this ticket [TMOBCAT-171]:
    • Rectified the mismatch of model value ID in the error sheet.
    • The error message during “Product/sku not found” scenario has been changed to “Product/sku not found to create model value – productId/skuId“.
  • The session time out during an import logs out the user properly now instead of throwing an error in the import summary. [TMOBCAT-109]
  • Previously, the admin was able to edit only from the second rule. Now, the admin user can delete the first rule as well without impacting the other rules. [TMOBCAT-204]
  • The following enhancements have been implemented in the Catalog Filter Rules UI [TMOBCAT-285]:
    • The Data table instead of Values chips.
    • The Data table is applicable ONLY when the user adds products/SKUs only which is supposed to have multiple/single part numbers
    • The Data table is searchable now to narrow down the search result.
    • When data is added to the table by clicking the plus icons, the most recent row is shown in the first row in the table.
    • The Data table is sortable by clicking the column header.
    • The Data table contains the Part number, Product name, Top Category, and Delete columns.
    • A scroll bar or pagination appears in each table.
  • Ability to create and manage products & SKUs association attributes within models. [SECOM-49391]
  • Ability to provide duplicate sequence values for attribute groups. [SECOM-50549]
  • Ability to import or export model values for “model by template” attributes along with products and/or SKUs. [SECOM-49860]
  • Support for “OR” condition and “SKU” based conditions have been provided while setting rules for the Sales Catalog. [SECOM-49742]
  • Support for enabling or disabling the project approval workflow in the Catalog’s collection property has been provided. [SECOM-49506]
  • Ability to skip the project approval workflow when the collection property “disable_project_workflow” is set to “true“. [SECOM-52646, SECOM-52644]
  • Support for special characters (such as !@$&()-_:{}/.*=space) have been provided in the Product or SKU ID. [SECOM-50003]
  • Ability to configure an attribute as “comparable” and/or “displayable”. [SECOM-50095] [SECOM-50483]
  • Ability to choose the sub-type of catalog (Default or Filter) while creating a sales catalog. [SECOM-50943]
  • Ability to search and view based on the sales catalog sub-type such as All, Default, or Filter in the Catalog’s listing page. [SECOM-50943]
  • The message property files have been updated appropriately for multi-language support. [SECOM-50728]
  • Ability to display a username instead of ID in the import history. [SECOM-50644]
  • The product and SKU Search modal has been enhanced as follows: [SECOM-51746]
    • The scrollbar appears automatically on entering more Product and/or SKU IDs in the search input area.
    • Ability to select or deselect all or required items has been added in the search result section.
  • The Filter type Sales Catalog functionality has been enhanced as follows: [SECOM-51734]
    • Ability to navigate to the Products and SKUs details page from the Product/SKU listing page.
    • Ability to view only the associated SKUs that belong to the specific catalog filter for a Product.
    • Ability to update or delete only the catalog rules.
  • Ability to exclude status-based conditions for catalog filters. [SECOM-51579]

Foundation Admin

The following new features or enhancements have been implemented in the Foundation Admin console for this release:

  • Ability to skip the triggered publish feed from the master publish when the other specific publish feed is triggered via the master publish. [SECOM-53422]
  • Ability to associate a price rule or price list to a B2C or B2B store based on the shipping region. [SECOM-48852]
  • Ability to navigate to the specific price rule detail page on clicking the Pricing card from the StoreOps page. [SECOM-48852]
  • Ability to associate collections automatically for all the microservices while creating a store. [SECOM-52645]
  • The message property files have been updated appropriately for multi-language support. [SECOM-50728]

Merchandising Admin

The following new features or enhancements have been implemented in the Merchandising Admin console for this release:

  • Ability to display a username instead of an ID in the import history. [SECOM-50644]
  • Support for enabling or disabling the project approval workflow in the Merchandising collection property has been provided. [SECOM-49506, SECOM-49994, SECOM-50105]
  • Ability to skip the project approval workflow when the collection property “disable_project_workflow” is set to “true“. [SECOM-52646, SECOM-52644]
  • Ability to update record count on running the Merchandising feed. [SECOM-51497]

Pricing Admin

The following new features or enhancements have been implemented in the Pricing Admin console for this release:

  • The following feature has been implemented as part of this ticket [SECOM-52071]:
    • Ability to copy a pricelist and edit the pricelist name. [TMOBCAT-52]
    • It is recommended that the user stays on the copy screen while the copying is in progress, although there is no such enforced restriction.
    • Only one copying job can be run at one time.
    • Copying will take a few minutes for up to 10,000 SKUs and up to 10 minutes for 50,000
  • The Recursive price field in the Pricelist page is now optional. Previously, this field was a mandatory field. [TMOBCAT-160]
  • Ability to delete (soft delete) the Evergreen Price from a SKU via the project approval workflow. [TMOBCAT-233]
  • Support for enabling or disabling the project approval workflow has been provided in the collection property. [SECOM-49506]
  • Ability to skip the project approval workflow when the collection property “disable_project_workflow” is set to “true”. [SECOM-52646, SECOM-52644]
  • Ability to import prices that have a valid number of digits after the decimal to have accurate prices for the store. An error message is shown for an invalid price value. [TMOBCAT-3 / TMOBCAT-4]
  • Ability to provide float values for markup and markdown. The round-off option is optional. [SECOM-48857]
  • Ability to create and manage conditions and actions within a price rule. [SECOM-48856]
  • Ability to create and manage a price rule. [SECOM-48855]
  • Ability to accept “0” as a price value for Transaction Price, Subscription Price, Price Type, Bundle Price, and Floor Price. [SECOM-50548]
    • Ability to fetch a price with the given pricelist ID and/or name in the Fetch Pricelist dropdown of the Price Rules page. [SECOM-51166]
    • Ability to view the pricelist IDs and names in the Search Pricelist drop-down list. [SECOM-51166]
  • Ability to display a username instead of an ID in the import history. [SECOM-50644]
  • Ability to accept “0” as a price value when the collection property “allow_zero_pricing” is enabled. [SECOM-50613]
  • Ability to clone an existing price rule. [SECOM-50367]
  • Ability to update record count on running the pricing feed. [SECOM-51498]

Promotion Admin

The following new features or enhancements have been implemented in the Promotion Admin console for this release:

  • Ability to display Project icon in the header and the select project pop-up at the time of creating, editing, or cloning promotion actions when the collection property ‘defaultprojectaccess‘ is turned off. [SECOM-53257]
  • Ability to skip the project approval workflow when the collection property “disable_project_workflow” is set to “true”. [SECOM-52646]
  • After an upload, the promotion list summary details were not displayed. Now, this has been rectified to display the necessary summary details. [TMOBCAT-189]
  • The Account ID value is appended with 000 at the end after generating the condition. This has been rectified to generate only the Account Id value. Previously, only the numeric character was allowed in the Account Id field. Now, it accepts the alpha-numeric characters. [TMOBCAT-123]
  • Ability to configure Min Quantity and Max Quantity attributes with options to select Greater Than or Less Than under the SKU object in Actions’ Condition section. [TMOBCAT-202]
  • Ability to display a username instead of an ID in the import history. [SECOM-50644]
  • Ability to publish the promotion data from the authoring environment to the production environment. [TMOBCAT-98]

Release Changes for Infosys Equinox Framework

  • Third-party credentials, client secrets, and access keys were maintained as plain text in the ZooKeeper properties. This is now encrypted by the secret which is maintained in the AWS Secret Manager. [SECOM-52778]

Security and Performance

  • The Apache Log4j security vulnerability issue has been resolved by upgrading to the Log4j 2.16.0 version. Now, all the log messages running from Infosys Equinox Commerce are executed appropriately without any arbitrary code.

Technical Improvements

The following technical improvements have been implemented:

  • The evictor policy of Pentaho HTTP Components has been updated from -1 to 1000 milliseconds. [SECOM-49899]
  • Updated the Lodash package to the current version “17.21”. [SECOM-53803]
  • Additional provisions for loading external plugins JPA repositories have been implemented in all the microservices, and also included swagger YML docs from the plugins. [SECOM-53108]
  • Apache Camel version has been upgraded to 2.25.1 to fix a potential vulnerability while accessing RabbitMQ. [SECOM-50939]
  • Upgraded the following software to address the potential vulnerability issues. [SECOM-53076, SECOM-52481]
Software Previous Version Current Version
Apache SOLR 7.7.2 7.7.3
RabbitMQ 3.7.7 3.7.28
Apache ZooKeeper 3.4.10 3.4.14
MySQL 5.7.27 5.7.34
MongoDB 4.0.1 4.0.27
Redis 4.0.10 6.0.5
Kettle Not Available 8.2.0.0-342
  • The connection leak and date format have been fixed in all the feed jobs. [SECOM-52248]
  • The following technical improvements have been implemented in all the admin services [SECOM-49415]:
    • Removed residual codes
    • Bug fixes for admin localization

Known Issues

The following are the known issues in this release:

JIRA Ticket # Service Name Description
SECOM-53611 Search, Storefront Orchestration Response for a few Search terms is the same with or without filters when provided.
SECOM-53129 Catalog Admin Only Partial products are displayed in the filter catalog when the rule is given as ‘ALL’.
SECOM-52956 Promotion Admin Past Dates are not disabled in the Date Range field of the Create Promotion Group page.
SECOM-52620 Foundation Admin On running the full publish via admin, even if the feeds are successful, the summary details are reported wrong.
SECOM-52506 Promotion Admin The Stop Condition “Always” is not working at the promotion level on selecting Item Price offer type and BOGO action type.
SECOM-52488 Feed, Foundation Admin The summary details show incorrectly after triggering the Account Publish with the type INCREMENTAL.
SECOM-52067 Catalog Admin The count is not reflected immediately in the Master Catalog, Overview page, and the pagination count after adding products and/or SKUs.
SECOM-53236 Admin Orchestration When priceFacet ID is mandatory for a particular pricelist; however, it allows to assign or update prices for a SKU even without assigning a price facet to it.
SECOM-53151 Admin Orchestration When the transaction price, scheduled prices, and facet prices are provided along with the variable min and max price, an error should be displayed as these values are not acceptable.
SECOM-53152 Admin Orchestration The bundle price is not getting updated in the call multiPriceUpdate.
SECOM-52479 Catalog Admin The List operator in the Sales Catalog Rule filter is not showing a valid response.
SECOM-52777 Storefront Orchestration The price obtained in the response is not considering the schedule price when all the prices are taken from the default price list.
SECOM-53867 Cart/Foundation Admin The data is not reflected in SOLR after running the Reindexer feed.
The Add to Cart issue to be resolved for the error “Cart with the requested ID does not exist”.

 

17 December 2021 (8.9.5)

Security and Performance

The Apache Log4j security vulnerability issue has been resolved by upgrading to the Log4j 2.16.0 version. Now, all the log messages running from Infosys Equinox Commerce are executed appropriately without any arbitrary code.

18 March 2021 (8.9.4)

Authorization Service

The following bug has been fixed in the Authorization service:

  • Facebook user authentication issue has been resolved. [SECOM-52395]

Search Service

The following bugs have been fixed in the Search service [SECOM-52475]:

  • autoSoftCommit has been enabled with revised maxDocs and maxTime in the <updateHandler> element in the solrconfig.xml file.
  • openSearcher has been set to false in the <autoCommit> element in the solrconfig.xml file.

09 September 2020 (8.9.3)

Storefront Orchestration Service

The following hotfix has been implemented in the Storefront Orchestration service:

  • The shared Cart functionality which was not working in the Cloud environment in the previous release has been resolved. [SECOM-50891]

25 August 2020 (8.9.0)

Accounts Admin

The following new feature has been implemented in the Accounts Admin for this release:

  • Ability to enter custom properties for an account as an admin or account representative. [SECOM-48771]

Accounts Service

The following new features or enhancements have been implemented in the Account service for this release:

  • Ability to associate a price rule to the contract. [SECOM-48849]
  • Allows a buyer organization user to view the contract properties. [SECOM-48772]
  • Ability to enter custom properties for accounts has been included for the accounts admin, accounts representative, and buyer admin user. [SECOM-48770]
  • Ability to create and manage custom attributes for accounts and contracts have been included for the accounts admin user. [SECOM-48769]

Catalog Admin

The following features or enhancements have been newly implemented for this release [SECOM-48780]:

  • Ability to associate a set of products or SKUs to a SKU 
  • Ability to create an attribute with field type as “Products” or “SKUs” and attribute level as “SKU”.
  • Ability to search an attribute and add relations to an SKU has been included i.e adding any number of products/SKUs using an associated attribute.
  • Ability to mark an attribute section for deletion and submit it for approval.
  • Ability to delete a particular item from an attribute.

The following features or enhancements have been newly implemented for this release [SECOM-48779]:

  • Ability to associate a set of products or SKUs to a product 
  • Ability to create an attribute with field type as “Products” or “SKUs” and attribute level as “Product”.
  • Ability to search an attribute and add relations to a product has been updated i.e adding any number of products/SKUs using an associated attribute.
  • Ability to mark an attribute section for deletion and submit it for approval.
  • Ability to delete a particular item from an attribute.

Catalog Service

The following new feature has been implemented in the Catalog service for this release [SECOM-48777]:

  • Ability to create and manage an attribute with field type as “Products” or “SKUs”.
  • Ability to associate those attributes to a product or SKU or both in the relations section. 

The following new feature has been implemented in the Catalog service for this release [SECOM-48778]:

  • Ability to create and manage an attribute with model type as “Products” or “SKUs”.
  • Ability to define if an attribute can be associated with “Products” or “SKUs” or both using the “level” field. 

Feed Service

The following new feature has been implemented in the Feeds service for this release:

  • Ability to import and export the attributes with level and field type as “Products” and “SKUs”. [SECOM-48784]

Pricing Service

The following new feature has been implemented in the Pricing service for this release:

  • Ability to create and manage price rules within a pricing collection. [SECOM-48853]

Performance

The following issues have been resolved in the Performance for this release:

  • My SQL connections have been closed which resolved the Feed Pentaho server issue. [SECOM-49736]
  • Latency issue has been resolved in the Merchandising Admin’s Category rule builder page which makes a search call to get attributes and values for constructing rules. [SECOM-49737]

Storefront Orchestration Service

The following new features or enhancements  have been implemented in the Storefront Orchestration service for this release:

  • Allows a buyer organization user to view the contract properties. [SECOM-48774]
  • Ability to enter properties for accounts while creating and editing an account. [SECOM-47327]

Technical Improvements

  • The evictor policy of Pentaho HTTP Components has been updated from -1 to 1000 millisecond. [SECOM-49899]

17 June 2020 (8.8.1)

Foundation Admin

The following feature has been implemented in the Foundation Admin:

  • A basic Google Analytics Report dashboard has been implemented in the Store Ops page. [SPS-527]

Merchandising Admin

The following bug has been fixed in the Merchandising Admin console:

  • Latency issue in a Milestone’s Preview section in the Merchandising Admin console which was encountered in the Mac machine has been resolved. [SECOM-49594]

Bug Fixes in Storefront Orchestration

The following bug has been fixed in the Storefront Orchestration service:

  • The issue of merging carts into a single cart for up to 3 stores has been fixed. [SPS-534]

Security and Performance

  • Latency issue in the “Inv – collections_prop_put” API has been resolved. [SECOM-48804]
  • Latency issue in the “DELETE_Hard_Delete By Subscription Id” API has been resolved. [SECOM-48829]
  • Support has been added to handle the Pentaho cluster in the Feed service. [SECOM-49581]
  • The following collection attributes have been added to the Loyalty service [INFRA-22306]:
    • customActionTypesConfig
    • expirationPeriod
    • roundOffValue
  • ReGex has been removed from the Multi-model DB query for better performance. [SECOM-49580]

Technical Improvements

  • The maximum column limit of the Catalog import feed has been increased from 100 to 200. [SECOM-49411]
  • The evictor policy of Pentaho HTTP Components has been updated from -1 to 1000 millisecond. [SECOM-49899]

05 June 2020 (8.8.0)

Release Changes for Skava Commerce Microservices

Accounts Service

The following new feature or enhancement has been implemented in the Accounts service for this release:

  • Allows a buyer org user to place orders within the budget limits of the cost center. [SECOM-47611]

Cart Service

The following new feature or enhancement has been implemented in the Cart service for this release:

  • Displays a warning message stating that there no shipping methods available when dangerous goods are added to the cart with the military address. [SECOM-47276]

Feeds Service

The following new feature has been implemented in the Feeds service for this release:

  • Ability to enter a maximum number of quantities that can be preordered for a particular SKU. This is entered in the Preordered Quantity column of the Bin-Item sheet. [SECOM-47613]

Inventory Service

The following new feature or enhancement has been implemented in the Inventory service for this release:

  • Ability to add or remove any number of backorder items to a cart in the checkout page or while placing an order. [SECOM-47449]

Loyalty Service

The following new features or enhancements  have been implemented in the Loyalty service for this release:

  • Ability to view the loyalty history details on the customer’s My Account page. [SECOM-47271]
  • Ability to configure the gift item in a promotion rule with the priority. [SECOM-47272]
  • Ability to redeem the loyalty points with business conditions, such as redeeming a maximum configured points for a given month, redeeming any particular item or category more than the maximum configured points, etc. [SECOM-47273]
  • Ability to configure the number of consecutive months and the loyalty point conversion percentage based on customer longevity in the program, which will enable the customers to earn the points based on their tier. [SECOM-47274]
  • Allows a CSR admin to change the eligibility criteria and reward rules. [SECOM-47277]
  • Allows a CSR admin to remove credits from a member’s account. [SECOM-47279]
  • Ability to calculate and apply reward points on a monthly basis. [SECOM-47283]
  • Ability to expire the unused loyalty points after 12 months. [SECOM-47286]

Order Service

The following new features or enhancements  have been implemented in the Order service for this release:

  • Ability to place an order even when there is no inventory available. [SECOM-47333]
  • Allows a buyer org user to place orders within the budget limits of the cost center. [SECOM-47612]

Storefront Orchestration Service

The following new features or enhancements  have been implemented in the Storefront Orchestration service for this release:

  • Ability to place orders only within the available budget of the cost center. [SECOM-42214]
  • Ability to view and apply promotions based on the account to which the user belongs to. [SECOM-47047]
  • Support has been provided for mapping a user to more than one cost center by a buyer admin. [SECOM-47324]
  • Ability to add or remove any number of backorder items to a cart in the checkout page or while placing an order by a customer. [SECOM-47448]

Subscription Service

The following new features or enhancements  have been implemented in the Subscription service for this release:

  • The following features have been implemented as part of the ticket [SECOM-47266]:
    • Ability to view subscription’s product image, name, quantity subscribed, frequency, and price.
    • Ability to update the quantity and frequency.
    • Ability to skip the next delivery from the subscription recurring order.
    • Ability to cancel the subscription by selecting the delete icon.
  • Ability to update the shipping address and payment method in the Subscription dashboard from the Customer Service page. [SECOM-47267]
  • Ability to update the immediate processing date of the subscription for a particular user. [SECOM-47269]
  • Ability to distinguish between order placed as subscriptions and one-time order(s).  [SECOM-47278]
  • The following features have been implemented as part of the ticket [SECOM-47285]:
    • Ability to merge all the recurrence subscriptions in the same month as a single order.
    • Ability to display the next month’s subscription if the subscription order is already processed for the current month.

Release Changes for Skava Commerce Admin Consoles

Catalog Admin

  • Ability to define if a SKU is pre-orderable. For the pre-orderable SKU, the option to set a date of availability post which the SKU cannot be preordered has been provided. [SECOM-47447]

Foundation

  • The Feed History tab has been enhanced to display service name and summary for each feed. [SECOM-47321]
  • Ability to provide account-based promotion offers while returning, replacing, or exchanging item(s). [SECOM-47782]

Order Admin

  • Allows a buyer org user to place orders within the budget limits of the cost center. [SECOM-47610]
  • Allows a CSR to filter for orders and customers based on the account ID. [SECOM-47780]
  • The following changes have been implemented as part of the ticket [SECOM-47905]:
    • Allows a CSR to return, replace, exchange, correct the orders placed by buyer org users.
    • Considers initial address and payment methods in the checkout screen.

Other Release Changes

Framework

  • In addition to AWS Secrets Manager, support for Azure Key Vault has been introduced at the framework level for storing secrets required for the application to work. [SECOM-48597]
  • The webbox folder, etl folder, and build.yml file have been packaged into a config binary for breaking the code dependency of deliverables. [SECOM-48599]
  • Support for comma-separated multiple packages has been provided for entity scan so that plugins or entities present in various package names can be loaded into the Spring Boot context. [SECOM-48600]

Security and Performance

  • Latency issues in the Overview page of a customer when logged in as a CSR Admin has been resolved. [SECOM-48476]
  • Latency issues in the Overview page of an order when logged in as a CSR Admin has been resolved. [SECOM-48509]
  • The server information which was revealed inadvertently in an error code has been fixed by updating the content type. [SECOM-48588]

Technical Improvements

  • The tag was getting rendered instead of plain text for Team and Cost Center in the Users tab of the Accounts Admin console. Now, this issue has been resolved. [SECOM-48581]

05 May 2020 (8.7.3 & 8.7.4)

Bug Fixes for Release 8.7.4

The following changes have been implemented in the Tagging section of Catalog Admin console for both single product update and bulk updates:

  • The Bulk Update button has been renamed as Update Tags button in the Tagging page.
  • The Update Tags button and Go button alignment have been resolved.
  • The breadcrumb for a Product Tag has been fixed to display Catalogs/Master/Tagging/<Product Tag>, where Product Tag is the product’s tag name.
  • The Tagging label has been renamed as Product Tags after navigating to a particular product.
  • The Product Tags screen’s box alignment has been fixed for non-edit and edit modes.
  • Under the product tag, displays the tag caption for the selected tags. Otherwise, the text “No Tags Available” is shown when no tags are selected.

Bug Fixes for Release 8.7.3

The following changes have been implemented in the Tagging section of Catalog Admin console:

  • Allows the user to select 50 products on the Tagging page.
  • When switching the locale, the existing tags are shown based on the selected locale.
  • The Tags Overview title alignment and font issues have been resolved to maintain consistency.
  • The Project icon has been removed from the Tags Overview page.
  • The Tagging title alignment and font issues have been resolved to maintain consistency.
  • The sort option has been removed from the Select column.
  • The sort option has been provided to the Product ID column.
  • The UI alignment issue has been fixed between the initial load and after applying the filters.
  • The width of the Product Name column has been increased and the width of the Product ID column has been reduced to reflect appropriately.

15 April 2020 (8.7.1 & 8.7.2)

Catalog Admin

The following changes have been implemented in the Catalog Admin console:

  • While exporting the model data, there is a separate sheet that appears for an attribute. This sheet containing the attribute has been removed. Now, it contains only the model data. [SECOM-47180]
  • The Catalog Import feed is completed with an error while importing model values for multiple locales. This has been resolved. [SECOM-47421]
  • When there is no data for a particular locale, it was not picking up the default locale. This issue has been rectified. [SECOM-47488]
  • On clicking the Add button in the Model Values Import section it was not prompting to an appropriate page after selecting a project. This has been resolved now. [SECOM-47561]
  • After importing the model values, the imported details were not getting reflected immediately. This issue has been resolved. [SECOM-47562]
  • The reference values of the model attribute were getting rendered on the admin for only one reference value and not for the other reference value. This has been rectified. [SECOM-47563]
  • In the nested model scenario, the model values of the nested model were not getting displayed in View mode. This has been rectified. [SECOM-47564]
  • The deleted model was displayed in the export model data. The deleted model will not be reflected now. [SECOM-47565]
  • The template model values are non-editable now in the Product/SKU association when its nested under the Reference model. [SECOM-47572]
  • The following issues in the Tagging screen have been resolved [SECOM-47573]:
    • Resolved Alignment issue in the Tags Overview page
    • Removed Product related search fields from the Tag grid
  • The issue related to default expansion of the nested model in the model value creation page has been rectified. [SECOM-47578]
  • The data duplication issue of an approved project in the Attributes section has been resolved. [SECOM-47581]
  • Issues related to the lazy load option within the model values have been resolved. [SECOM-47582]

Feed Service

The following changes have been implemented in the Feed service:

  • In the B2B Reindexer feed, the second-level children model attributes are not getting reflected in SOLR. This issue has been rectified. [SECOM-47123]
  • Previously, the description was not displayed when the models are created via the Import sheet. This issue has been resolved. [SECOM-47182]
  • The bundled products are not reflected in SOLR after running the B2C Reindexer feed. This is resolved now. [SECOM-47727]

08 April 2020 (8.7.0)

Release Changes for Skava Commerce Microservices

Catalog Service

The following new features or changes have been implemented in the Catalog Service for this release:

  • Ability to manage the Model value attribute. [SECOM-46066]
  • Added privileges to manage the Model entity. [SECOM-46028]
  • Added multi-locale support for type Reference Model. [SECOM-45987]
  • Ability to map the Reference Model type to product and/or SKU. [SECOM-45962]
  • Ability to map the Template Model type to product and/or SKU. [SECOM-45958]
  • Ability to create attributes for Model and nested Model. [SECOM-45957]
  • Added an optional param that is used to pull out the models and the attributes within that model, which is associated with the given Product and/or SKU. [SECOM-45956]
  • Added entity value to store attribute value for the Reference Model type. [SECOM-45955]
  • Added entity value to store attribute value for the Template Model type. [SECOM-45953]
  • Ability to Delete a Model. [SECOM-45950]
  • Ability to update all or specific attributes of a Model. [SECOM-45949]
  • Ability to update a specific Model. [SECOM-45948]
  • Ability to find a specific Model. [SECOM-45947]
  • Ability to find all the Models. [SECOM-45946]
  • Ability to create a Model. [SECOM-45945]
  • Added new field type Model for attributes. [SECOM-45944, SECOM-45936]
  • Added new fields Parent Model ID and Model ID in attribute master. [SECOM-45935]

Ratings and Reviews Service

The following changes have been implemented as part of this ticket [SECOM-47072]:

  • The Ratings and Reviews service has been newly introduced where a super admin/business admin user can view all the ratings and reviews detail and approve/reject a review of a registered customer.
  • Ability to display the submitted review of a customer with the “Pending” status.
  • Ability to publish only the approved reviews on the storefront.
  • Ability to display the reviews in the chronological order based on the review submitted timestamp.
  • Ability to display the ratings and reviews according to the selected locale.
  • Ability to view the recently reviewed items by showing the latest at the top.
  • Ability to view the item-wise overall ratings (average rating, rating count, and review count) of a product/SKU.
  • Ability to download the recently reviewed items or overall ratings of all the products/SKUs in an excel sheet file format to your local computer.
  • Ability to search by item ID, rating, and status of the item.
  • The following capabilities have been implemented as a plugin (SDK) for Ratings & Reviews as part of this ticket [SECOM-47072]:
    • Ability to submit one or more ratings and reviews as a registered user or Anonymous user for the same product/SKU.
    • Ability to like or unlike a rating or review provided for a product in the PDP page by a registered or anonymous user.
    • Ability to sort the ratings by “High to Low” or “Low to High” order.
    • Ability to view reviews by rating-wise.
    • Ability to upload images by a customer.

Feed Service

The following new features or changes have been implemented in the Feed Service for this release:

  • Added feed support for product and/or SKU association with model attributes. [SECOM-46365]
  • Added export feed support to export products and/or SKUs with reference model attribute values. [SECOM-46351]
  • Ability to honor the attribute entity changes and addition of model entity in the B2B Reindexer feed. [SECOM-46349]
  • Ability to honor the attribute entity changes and addition of model entity in the B2C Reindexer feed. [SECOM-46348]
  • Added export feed support to export models. [SECOM-46341]
  • Project approval feed to support the Reference Model attributes. [SECOM-45998]
  • Ability to honor the data type model and the model entity in the Reindexer feed. [SECOM-45997]
  • Ability to handle reference model values in product and/or SKU Import feed. [SECOM-45989]
  • Export capabilities to get the model values of type Reference via feed. [SECOM-45986]
  • Added import support to create multiple attribute values for reference model type. [SECOM-45983]
  • Added import support to create models. [SECOM-45982]
  • Ability to honor the model field type and additional columns in Attribute Import feed. [SECOM-45979]

Release Changes for Skava Commerce Admin Consoles

Catalog Admin Console

The following change has been implemented in the Catalog Admin Console for this release:

  • Ability to use model attributes for sales catalog mapping and product and/or SKU attribute listing filter. [SECOM-46042]
  • The following changes have been implemented for the reference model as part of this ticket [SECOM-46041]:
    • Added project workflow to define attribute values.
    • Added a new Models tab in the project details page.
  • Limited privilege to delete a Model by a Catalog Editor. [SECOM-46039]
  • Added Model value in the Field Type of the attribute. [SECOM-46035]
  • Modified sample template to support the Model creation, addition of attribute value for reference Model. [SECOM-46034]
  • Ability to export the attribute values of the reference model. [SECOM-46033]
  • Ability to import the attribute values of the reference model. [SECOM-46032]
  • Added support to import the attribute values. [SECOM-46031]
  • Ability to view attributes, template model as attributes, and reference model as attributes while mapping the attributes with products. [SECOM-45974]
  • The following changes have been implemented as part of this ticket [SECOM-45934]:
    • Ability to view the Reference Models in the product attributes list and map the Model(s) as attributes to the product.
    • Ability to choose multiple attribute values of the Reference Model.
  • The following changes have been implemented as part of this ticket [SECOM-45933]:
    • Ability to view the Reference Models in the master catalog details page and define values for the attributes via project workflow.
    • Ability to define multiple attribute values for the Reference Model based on the locale.
  • Ability to view the Template Models in the product attributes list and map the Model(s) as attributes to the product. [SECOM-45932]
  • Ability to nest a Model within another Model via the attribute type “Model”. [SECOM-45931]
  • Ability to edit an existing attribute within a model. [SECOM-45930]
  • Ability to add attributes within a model. [SECOM-45928]
  • Ability to create a new Model. [SECOM-45927]
  • Ability to view Model listing page. [SECOM-45925]
  • Added the Data Model tab in the left navigation panel. [SECOM-45924]

Foundation Admin Console

The following new features or changes have been implemented in the Foundation Admin Console for this release:

  • The following changes have been implemented as part of this ticket [SECOM-47111]:
    • Added the Feed History tab in the Left Navigation panel to view the Feed history that has run in the SkavaCommerce application.
    • Ability to search for feed, view the status of the feed, auto-refresh the Feed History page, and export feed in the Feed History page.

Merchandising Admin Console

The following new features or changes have been implemented in the Merchandising Admin Console for this release:

  • The following changes have been implemented as part of this ticket [SECOM-46821]:
    • Ability to add images for a category.
    • Enhanced the authoring section of the category description with HTML for a category.
  • Ability to map the products with a category by using the product filter. [SECOM-45622]
  • Ability to maintain the order of the products and sequence of the template within the category. [SECOM-45888]
  • Ability to view the category property as part of the search criteria. [SECOM-46826]

Ratings and Reviews Console

The following changes have been implemented as part of this ticket [SECOM-47072]:

  • The Ratings and Reviews Admin console has been newly introduced where a super admin/business admin user can view all the ratings and reviews detail and approve/reject a review of a registered customer.
  • Ability to display the submitted review of a customer with the “Pending” status.
  • Ability to publish only the approved reviews on the storefront.
  • Ability to display the reviews in the chronological order based on the review submitted timestamp.
  • Ability to display the ratings and reviews according to the selected locale.
  • Ability to view the recently reviewed items by showing the latest at the top.
  • Ability to view the item-wise overall ratings (average rating, rating count, and review count) of a product/SKU.
  • Ability to download the recently reviewed items or overall ratings of all the products/SKUs in an excel sheet file format to your local computer.
  • Ability to search by item ID, rating, and status of the item.

Known Issues

Users may experience latency under high load (less than 3 seconds) when opening the following pages in the CSR Admin console:

  • Customer Overview page [SECOM-48476]
  • Order Overview page [SECOM-48509]
  • Order Checkout page [SECOM-48510]

03 February 2020 (8.6.0)

Release Changes for Storefront Orchestration Service

The following new features or changes have been implemented in the Storefront Orchestration Service for this release:

  • Added support to track the status of an item, which is yet to be delivered to a customer. [SECOM-44705]
  • Added support for a CSR to create backdated orders on behalf of a customer. [SECOM-44829]
  • Added support to send an email notification to a customer upon receiving appeasements. [SECOM-44689]
  • Added support to choose required payment methods to pay for an order, such as Card, Store Credits, and/or Reward Points. [SECOM-44629]

Release Changes for Skava Commerce Microservices

Authorization Service

The following new features or changes have been implemented in the Authorization Service for this release [SECOM-44569]:

  • The existing role ROLE_CSR_ADMIN has been enhanced with the additional privilege.
  • A new role ROLE_CSR_ASSOCIATE has been added with relevant privileges that are a subset of the role ROLE_CSR_ADMIN.

Address Service

The following new features or changes have been implemented in the Address Service for this release:

  • Ability to view the list of address suggestions. [SECOM-45386]
  • Support for predefined data has been provided to integrate the third-party plugins. [SECOM-45387]

Cart and Checkout Service

The following new features or changes have been implemented in the Cart and Checkout Service for this release:

  • The following changes have been implemented as part of this ticket [SECOM-44707]:
    • Ability to create a cart for a customer by an admin or CSR.
    • Ability to view a customer’s cart by an admin or CSR.
  • Ability to view and manage the variable charges involved in the calculation for the returned order or order item by a CSR Admin. [SECOM-44699]
  • Ability to add and manage custom charges when CSR Admin returns the order items. [SECOM-4506]

Customers Service

The following new features or changes have been implemented in the Customers Service for this release:

  • Ability to create a new set of users who want to sign up to receive newsletters, marketing campaigns, and/or subscriptions. [SECOM-45388]
  • Ability to add notes to a customer to track all the actions that are taken or requested by a customer. [SECOM-44690]

Merchandising Service

The following new features or changes have been implemented in the Merchandising Service for this release:

  • Ability to define a product group. [SECOM-45682]
  • Ability to create more than a milestone for a product group. [SECOM-45683]
  • Ability to group the products and assign a template to the product group milestone. [SECOM-45684]
  • Ability to define a search term. [SECOM-45677]
  • Ability to create more than a milestone for a search term. [SECOM-45678]
  • Ability to override the search results for a search term and assign a template within a milestone. [SECOM-45679]
  • Ability to preview the search template in the search results preview section. [SECOM-45681]
  • Ability to redirect the user to a specific URL for a search term within a milestone. [SECOM-45680]

Notification Service

The following change has been implemented in the Notification Service for this release:

  • Ability to send a notification email to a customer upon receiving appeasements. [SECOM-44567]
  • The following changes have been implemented as part of this ticket [SECOM-44702]:
    • When a return, replacement, or exchange is initiated, an email is triggered to the customer.
    • When a refund is initiated against return, replace, or exchange, an email with refund details is triggered to the customer.
    • When a correction is performed against a default order, the order confirmation email is triggered to the customer.

Order Service

The following new features or changes have been implemented in the Order Service for this release:

  • Ability to generate a shipping label when a product is returned in return and exchange flows. [SECOM-44706]
  • Ability to receive notifications upon the initiation of return or refund of the order and the confirmation of exchange or replacement of the order. [SECOM-44703]
  • Order model has been updated to support the following functionalities [SECOM-44692]:
    • Ability to trace back to the parent order for which the return order has been triggered.
    • Ability to support different order types, such as default, return, replace, exchange and correction.
    • Ability to support the backdating of orders.
  • The following changes have been implemented as part of this ticket [SECOM-44691]:
    • Ability to configure the supported order types such as default, return, replace, exchange, and correction for an order collection.
    • Ability to define an admin workflow for each order type based on the collection property.
    • Ability to manage warehouse addresses.
  • Ability to configure the time period and the number of retry attempts in the Order processing flow. [SECOM-45384]

Payment Service

The following new features or changes have been implemented in the Payment Service for this release:

  • Ability to choose any one of the payment methods to pay for an order, such as cards, store credits, or reward points. [SECOM-44630]
  • Ability to view an order with “Pending” status after placing the order to indicate an issue with the customer’s payment method or if there is any background verification in progress. [SECOM-45385]

Shipping Service

The following change has been implemented in the Shipping Service for this release:

  • Support for predefined data has been provided to integrate the third-party plugins. [SECOM-45387]

Tax Service

The following change has been implemented in the Tax Service for this release:

  • Support for predefined data has been provided to integrate the third-party plugins. [SECOM-45387]

Release Changes for Skava Commerce Admin Consoles

Customers (User) Admin Console

The following new features or changes have been implemented in the Customers (User) Admin Console for this release:

  • Ability to add notes related to a customer to track all the actions that are taken or requested by a customer. [SECOM-44612]
  • Allows a CSR Admin to provide appeasement to a customer in the form of Store Credits, Reward Points, etc. [SECOM-44606]
  • Allows a CSR user to view Orders, Payments, Addresses, Loyalty, Subscriptions, Cart, Notes, and other details of customers. [SECOM-44602]

Foundation Admin Console

The following change has been implemented in the Foundation Admin Console for this release:

  • Ability to land to the CSR landing page where a CSR can search for a customer or order. The CSR user will be taken to the respective details page based on the search results. [SECOM-42640]

Merchandising Admin Console

The following new features or changes have been implemented in the Merchandising Admin Console for this release:

  • Added Product Group and Search Override menu in the left navigation panel. [SECOM-45676]
  • Ability to define a product group. [SECOM-45682]
  • Ability to create more than a milestone for a product group. [SECOM-45683]
  • Ability to group the products and assign a template to the product group milestone. [SECOM-45684]
  • Ability to preview the PDP template in the Product Group preview section. [SECOM-45685]
  • Ability to define a search term. [SECOM-45677]
  • Ability to create more than a milestone for a search term. [SECOM-45678]
  • Ability to override the search results for a search term and assign a template within a milestone. [SECOM-45679]
  • Ability to preview the search template in the search results preview section. [SECOM-45681]
  • Ability to redirect the user to a specific URL for a search term within a milestone. [SECOM-45680]

Order Admin Console

The following new features or changes have been implemented in the Order Admin Console for this release:

  • Allows a CSR to replace or exchange items in the order with one or more items on behalf of a customer. [SECOM-44621]
  • Ability to track the package of ordered items. [SECOM-44632]
  • The following changes have been implemented as part of this ticket [SECOM-44631]:
    • Support for multiple payment options such as Store Credits and Loyalty Reward points have been provided.
    • Ability to view refund details for the returned order in the Payment tab.
    • Ability to view the payment details for the exchanged or replaced order in the Payment tab.
  • A CSR user with necessary privileges can choose a refund or a charging method that is appropriate for the replacement or exchange initiated. [SECOM-44627]
  • Ability to view and manage shipping addresses and shipping methods while replacing or exchanging the items in the order on behalf of a customer. [SECOM-44626]
  • Allows a CSR to manage the variable charges involved while exchanging or replacing items. [SECOM-44625]
  • Allows a CSR to view the order summary of the returned items on the checkout page. [SECOM-44616]
  • The following changes have been implemented as part of this ticket [SECOM-44614]:
    • Allows a CSR to choose action against an order for both registered or guest user – Return, Replace, Exchange, Cancel, or Correction based on the status of the items ordered.
    • Ability to generate a shipping label when a product is returned in return and exchange flows.
  • Ability to add a note related to an order describing actions taken on the specific order on behalf of a customer. [SECOM-44608]

01 November 2019 (8.5.0)

Release Changes for Storefront Orchestration Service

The following new features or changes have been implemented in the Storefront Orchestration Service for this release:

  • Added support to send the refund status of the ordered item along with the amount when an order or order item is canceled. [SECOM-42715]
  • Added support to provide reason code to cancel an order. [SECOM-42690]
  • Added support to see the list of reason messages when an order or order item is canceled or returned. [SECOM-42703]
  • Added support to view the refund status of the payment along with the payment method in the order history. [SECOM-42716]
  • Added support to alias category name based on the selected locale. [SECOM-42608]
  • Added support to cancel one or more items of an order with reason. [SECOM-42694]
  • Added support to return one or more items of an order with reason. [SECOM-42700]
  • Added support to notify a customer through email regarding the order return and/or order cancel process to know the status of the return and/or cancelation. [SECOM-42706]

Release Changes for Skava Commerce Microservices

Authorization Service

The following new features or changes have been implemented in the Authorization Service for this release:

  • Ability to create a CSR Admin role. [SECOM-42734]

Feed Service

The following new features or changes have been implemented in the Feed Service for this release:

  • Ability to setup categories and its milestones as multi-locale in the Merchandising Admin reindexer feed, which enables the Merchandising Admin user to see the product categorization in their desired language. [SECOM-39501]
  • Ability to identify the loyalty points summary for a specific duration. [SECOM-42670]
  • Ability to identify the loyalty points expiration period. [SECOM-42671]
  • Ability to support the multi-locale data in the Merchandising Export feed. [SECOM-42681]
  • Ability to support the multi-locale data in the Merchandising Approval feed. [SECOM-42682]
  • Ability to set up categories and its milestones as multi-locale in the storefront user reindexer feed, which enables the Merchandising Admin user to see the product categorization in their desired language. [SECOM-42680]
  • Ability to support the multi-locale data in the Merchandising Import feed. [SECOM-42526]

Loyalty Service

The following change has been implemented in the Loyalty Service for this release:

  • Capability for collection property entities and collection attribute entities have been provided. [SECOM-42644]
  • The API calls for loading all loyalty groups, load a particular loyalty group, create a new loyalty group, update an existing loyalty group, and delete a loyalty group have been introduced. [SECOM-42654]
  • Ability to get the transaction details of a user for a given period. [SECOM-42672]
  • The loyalty user entities such as Collection ID, User ID, Status, Key-Value Pair, and Block Redemption Flag have been newly created. [SECOM-42649]
  • The API calls for creating a collection, updating an existing collection, and loading one or more collections have been newly introduced. [SECOM-42643]
  • The API calls for loading all rewards, load a particular reward, create a new reward, update an existing reward, and delete a reward have been introduced. [SECOM-42648]
  • The API calls for loading all events, load a particular event, create a new event, update an existing event, and delete an event have been introduced. [SECOM-42646]
  • The API calls for loading all loyalties, load a particular loyalty, create a new loyalty, update an existing loyalty, and delete a loyalty have been introduced. [SECOM-42677]
  • Ability to get the loyalty points using the API call “Get Points”. [SECOM-42667]
  • Ability to create a new transaction, load all transactions, load a particular transaction have been introduced. [SECOM-42669]

Catalog Service

The following change has been implemented in the Catalog Service for this release:

  • Ability to skip the project approval workflow when a user has the privilege catalog/defaultproject/catalog. [PSI-84]

Pricing Service

The following change has been implemented in the Pricing Service for this release:

  • Ability to skip the project approval workflow when a user has the privilege price/defaultproject/price. [PSI-90]

Merchandising Service

The following change has been implemented in the Merchandising Service for this release:

  • Ability to set up the the category attributes, categories, and milestones to support multi-locale. [SECOM-40965]
  • Ability to skip the project approval workflow when a user has the privilege merchandise/defaultproject/merchandise. [PSI-91]

Order Service

The following new features or changes have been implemented in the Order Service for this release:

  • Ability to notify a customer through an email regarding the order return or order cancel process to know the status of the return or cancelation. [SECOM-42705]
  • Ability to initiate the returns of an order item by a CSR or admin to help the customer returning the purchased item that is delivered to the customer. [SECOM-42699]
  • Ability to navigate to a particular order of a customer and cancel one or more item quantities in the order by a CSR or admin to partially cancel the quantities of an item in the order. [SECOM-42696]
  • Ability to navigate to a particular order of a customer and cancel one or more items in the order by a CSR or admin to stop the order items from fulfillment. [SECOM-42693]
  • Ability to initiate the partial returns of an order item by a CSR or admin to help the customer returning one or more quantity of the purchased item that is delivered to the customer. [SECOM-42702]
  • Ability to navigate to a particular order of a customer and cancel the entire order by a CSR or admin to stop the order from fulfillment. [SECOM-42689]

Search Service

The following new features or changes have been implemented in the Search Service for this release:

  • Ability to support the multi-locale data in the Merchandising service. [SECOM-39502]

Release Changes for Skava Commerce Admin Consoles

Authorization Admin Console

The following new features or changes have been implemented in the Authorization Admin Console for this release:

  • Ability to invite users with Loyalty Admin role. [SECOM-42641]

Catalog Admin Console

The following new features or changes have been implemented in the Catalog Admin Console for this release:

  • Ability to set the subscription frequency for a subscribe-able SKU by an admin user. [SECOM-39569]
  • Handling standard roles and privileges for Catalog Admin have been provided. [SECOM-20892]
  • Ability to set the subscription order processing information for a SKU. [SECOM-39570]
  • The Accounts Admin console has been improved for better consistency and look and feel. [SECOM-39485]
  • The following changes have been implemented as part of this ticket [SECOM-41099]
    • The tab ‘NOTES’ has been added in the project’s Details page with an ability to add project notes when the project status is Open, Submitted, or Approval Failed.
    • Ability to add or update a default category ID in the Basic Information page for a product.
    • Ability to add a UPC ID (Universal Product Code) in the Basic Information page for a SKU.
  • Ability to add products that are approved (Default projects) or not yet approved (Current projects) in the Relations, Bundle, Fixed Bundle, SKU Kit, or Collection tab. [SECOM-41478]
  • Ability to display progress bar while exporting all the catalog data. [SECOM-41477]
  • Ability to view the import history details for a collection in the Import tab. [SECOM-41326]

Customers (User) Admin Console

The following change has been implemented in the Customers (User) Admin Console for this release:

  • Ability to trigger a reset password email for a customer. [SECOM-42597]
  • Ability to place an order on behalf of a customer. [SECOM-42596]
  • The following changes have been implemented as part of this ticket [SECOM-42723]:
    • Ability to add the identifier of the admin user while generating an auth token.
    • Ability to get the identifier of the admin user while parsing an auth token. 
    • Ability to provide macros for user ID and admin user ID in getTestToken API call.
  • Ability to assign the CSR Admin role to a customer for a particular store, which enables the customer to log in to the store as a CSR admin. [SECOM-42531]

Foundation Admin Console

The following new features or changes have been implemented in the Foundation Admin Console for this release:

  • Ability to enable the Loyalty microservice for a business. [SECOM-42640]

Loyalty Admin Console

The following new features or changes have been implemented in the Loyalty Admin Console for this release:

  • The following changes have been implemented as part of this ticket [SECOM-42652]:
    • Ability to set up conditions and configure one or more actions after creating a new loyalty.
    • Ability to update the existing conditions and actions if required.
  • Ability to navigate to the Loyalty tab and view the Loyalty cycle details of a user from Customer Admin. [SECOM-42733]
  • Ability to search and view the loyalty groups. [SECOM-42725]
  • Ability to update a Loyalty within a Loyalty Group. [SECOM-42728]
  • Ability to navigate to Loyalty Admin console from the StoreOps page. [SECOM-42650]
  • Ability to view the loyalty summary of a user from the Loyalty tab in the Customer Admin console. [SECOM-42655]
  • Ability to update the existing Loyalty Group details. [SECOM-42724]
  • The following changes have been implemented as part of this ticket [SECOM-42653]:
    • Ability to create a new event in the Event page.
    • Ability to add multiple key-value properties to an event.
  • Ability to search and view the existing loyalty within a loyalty group. [SECOM-42726]
  • Ability to update a reward with details such as Currency and Reward Symbol. [SECOM-42721]
  • Ability to create a new reward with details such as Currency and Reward Symbol. [SECOM-42660]
  • Ability to update the existing event. [SECOM-42719]
  • Ability to search for a reward and view the reward details. [SECOM-42722]
  • Ability to search for an event and view the event details. [SECOM-42720]
  • Ability to create a new loyalty within a loyalty group. [SECOM-42727]
  • Ability to create a new loyalty group. [SECOM-42651]

Merchandising Admin Console

The following new features or changes have been implemented in the Merchandising Admin Console for this release:

  • The following changes have been implemented as part of the multi-locale selection by an admin [SECOM-42624]:
    • Ability to import and export the merchandising data based on a selected locale.
    • Ability to view categories, creative, and milestones based on a selected locale in the project details page.
  • Ability to define or view the alias category name based on the selected locale in the navigation milestones by an admin. [SECOM-42623]
  • Ability to define and view the category rules, search keyword, UX data based on the selected locale in the category milestones by an admin. [SECOM-42622]
  • Ability to define and view the categories based on the selected locale by an admin. [SECOM-42621]
  • Ability to define and view the category attributes based on the selected locale by an admin. [SECOM-35613]

Order Admin Console

The following change has been implemented in the Order Admin Console for this release:

  • Ability to view the refund status of the ordered item along with the amount by a CSR or admin when an order or order item is canceled. [SECOM-42661]
  • Ability to navigate to a particular order of a customer and cancel one or more items in the order by a CSR or admin to stop the order items from fulfillment. [SECOM-42551]
  • Ability to initiate the partial returns of an order item by a CSR or admin to help the customer returning one or more quantity of the purchased item that is delivered to the customer. [SECOM-42555]
  • Ability to notify a customer through email regarding the order return and/or order cancel process to know the status of the return and/or cancelation. [SECOM-42154]
  • Ability to initiate the returns of an order item by a CSR or admin to help the customer returning the purchased item that is delivered to the customer. [SECOM-42569]
  • Ability to navigate to a particular order of a customer and cancel one or more item quantities in the order by a CSR or admin. [SECOM-42552]
  • Ability to navigate to a particular order of a customer and cancel the entire order by a CSR or admin to stop the order from fulfillment. [SECOM-42550]

27 September 2019 (8.4.0)

Release Changes for Storefront Orchestration Service

The following new features or changes have been implemented in the Storefront Orchestration Service for this release:

  • Ability to log in to the system but products cannot be added into the cart when the status of the account is suspended. [SECOM-6066]
  • Ability to get the account-specific search results, such as product, SKU, pricing, and categories from a particular account’s contract. [SECOM-39464]
  • Ability to add Bundle product to the cart. [SECOM-39546]
  • Ability to restrict the Buyer Org user to log in to the deactivated or closed accounts. [SECOM-6065]
  • Ability to support customer data export as part of GDPR compliance. [SECOM-39650]
  • Ability to place subscription request for a SKU and perform actions for automatic order processing. [SECOM-31723]
  • Ability to place an order with a Bundle product. [SECOM-39547]
  • Ability to generate PDP with a Bundle product. [SECOM-39545]
  • Ability to support the Bundle and SKU KIT products in the PDP response. [SECOM-41457]
  • Ability to delete the customer’s account as part of GDPR compliance in the SFO perspective. [SECOM-41246]
  • Ability to view all the account orders as a buyer admin. [SECOM-41443]
  • Ability to access the account-specific category and products as a buyer user. [SECOM-41431]
  • The following changes have been implemented as part of this ticket [SECOM-41441]:
    • Ability to manage account address by a buyer admin.
    • Ability to view the account address by a buyer user for placing an order.
  • Ability to place an order using PO only up to the available credit limit by a buyer user. [SECOM-41440]
  • Ability to place an order within a cost center. [SECOM-41434]

Release Changes for Framework

The following new features or changes have been implemented in the Framework for this release:

  • Ability to publish the embedded JARs to artifactory as part of the build process. [SECOM-39554]
  • Ability to generate SDK automatically and integrate with the pipeline. [SECOM-39556]
  • Upgraded the Spring Boot version from Release 2.0.1 to Release 2.1.6. [SECOM-39558]
  • MySQL connector JAR and other third party plugins have been externalized to support different versions. [SECOM-39555]
  • Developed a new API to show the release number and release date of the microservice. [SECOM-39561]

Release Changes for Skava Commerce Microservices

Common Changes – Microservices

The naming conventions for privileges have been standardized across all microservices. [SECOM-41509]

Accounts Service

The following new features or changes have been implemented in the Accounts Service for this release:

  • Ability to create or update the account with the fields such as Account Name, Tax ID, DUNS, Account Size, Account Type, and Phone Number. [SECOM-31378]
  • The following new features have been implemented as part of this story [SECOM-39449]:
    • Ability to trigger an invitation email when the account admin or account representative creates an account.
    • Ability to trigger an email to activate the buyer admin when the contract is created.
    • Ability to trigger an email, when the account admin or account representative creates or updates the contract.
    • Ability to trigger an email, when the account admin or account representative made any change in the account information or account status.
  • The account parameter has been newly added, and validations and updates have been made in all the Search APIs. [SECOM-39497]
  • Ability to support the default roles for Seller Org (Account Admin and Account Representative) and Buyer Org (Buyer Admin and Buyer User). [SECOM-2665]
  • The following new features have been implemented as part of this story [SECOM-39499]:
    • Ability to search for any products.
    • Ability to obtain suggestions specific to the buyer-user account.
    • Ability to search, view, and/or access the suggestions for the product or category.
  • Ability to create the standard Buyer Org roles (such as Buyer Admin and Buyer User) and associate privileges to it. [SECOM-4055]
  • Ability to manage standard seller org roles and privileges for seller users. [SECOM-39460]
  • Ability to manage standard buyer org roles and privileges for buyer users. [SECOM-39463]
  • Ability to associate the merchandising site navigation for an account. [SECOM-3984]
  • Ability to upload the contract document in the .doc, .docx, or .pdf format file. The maximum limit is 16MB per document. [SECOM-3610]
  • Ability to add or update the expiry date for a contract. [SECOM-35776]
  • Ability to run SFO Merchandise Publish feed for B2B to push the category related messages to RabbitMQ. [SECOM-39495]
  • As an account admin, ability to update the existing contract (such as Catalog, Pricing, Merchandising, payment method, payment term, and/or credit limit) of an account. [SECOM-19269]
  • The following new features have been implemented as part of this story [SECOM-31375]:
    • Ability to configure ‘company bill-to’ as one of the payment methods while creating or updating an account.
    • Ability to predefine the account size via the collection properties.
  • Ability to run SFO Merchandise Listener feed for B2B to document the category messages in SOLR. [SECOM-39496]
  • Ability to update appropriate comments while updating the account status. [SECOM-35775]
  • Ability to update the start date and end date of the contract. [SECOM-40972]

Authorization Service

The following change has been implemented in the Authorization Service for this release:

  • The previous refresh token gets deactivated on generating a new refresh token. [SECOM-39500]

Catalog Service

The following new features or changes have been implemented in the Catalog Service for this release:

  • Ability to set the subscription frequency for a subscribe-able SKU by an admin user. [SECOM-39397]
  • The additional properties to support subscription at SKU level have been addressed, which impacts in the Catalog feed, Approval process, and import and mapping of SKU. [SECOM-39572]
  • Ability to set the subscription order processing information for a SKU. [SECOM-39398]

Cart and Checkout Service

The following change has been implemented in the Cart and Checkout Service for this release:

  • Ability to add Bundle product to the cart. [SECOM-39544]
  • Ability to assign an order to a cost center by a buyer org user. [SECOM-41623]
  • Ability to support  SKU KIT product in Cart service. [SECOM-41719]
  • Ability to support Bundle product in Cart service. [SECOM-41174]

Shipping Service

The following new features or changes have been implemented in the Shipping Service for this release:

  • Ability to support Bundle product in Shipping service. [SECOM-41712]
  • Ability to support  SKU KIT product in Shipping service. [SECOM-41731]

Tax Service

The following new features or changes have been implemented in the Tax Service for this release:

  • Ability to support Bundle product in Tax service. [SECOM-41718]
  • Ability to support  SKU KIT product in Tax service. [SECOM-41733]

Feed Service

The following new features or changes have been implemented in the Feed Service for this release:

  • Ability to reindex products, such as FixedBundles and Collections to generate PLP and PDP responses. [SECOM-39541]
  • Ability to retain the created time of a project even when it is edited. [SECOM-39349]
  • The following new features have been implemented as part of this story [SECOM-39346]:
    • Ability to delete the value of an attribute or field using the keyword #DELETE# in the import feed. 
    • Ability to import site navigations.
  • Ability to download the profile and other personal data of a customer such as orders, payment, etc. [SECOM-39381]
  • Ability to export merchandising details based on rules. [SECOM-39348]
  • Ability to retain the existing price values when a user imports the sheet with the empty value. [SECOM-39355]
  • Ability to run SFO Merchandise Publish feed for B2B to push the category related messages to RabbitMQ. [SECOM-39495]
  • Ability to run SFO Merchandise Listener feed for B2B to document the category messages in SOLR. [SECOM-39496]
  • Storefront Reindexer feed for the price, category, and catalog changes has been implemented. [SECOM-41445]
  • The Reindexer feed for Merchandising Admin has been implemented. [SECOM-41449]
  • Ability to clear the customer’s data, such as profile, payments, orders, and subscriptions through the feed process. [SECOM-36509]

Foundation Service

The following new features or changes have been implemented in the Foundation Service for this release:

  • Ability to enable or disable subscription microservice while creating a business. [SECOM-31632]
  • Ability to associate subscription service for a store. [SECOM-31641]

Merchandising Service

The following change has been implemented in the Merchandising Service for this release:

  • Ability to post separate events when a project is approved, denied, reopened, and submitted. [SECOM-39350]
  • Ability to choose site navigation as default or not. [SECOM-40080]

Notification Service

The following new features or changes have been implemented in the Notification Service for this release:

  • Ability to configure required templates for General Data Protection Regulation (GDPR) related emails. [SECOM-39578]
  • The following new features have been implemented pertaining to B2B as part of this story [SECOM-39449]:
    • Ability to trigger an invitation email when the account admin or account representative creates an account.
    • Ability to trigger an email to activate the buyer admin when the contract is created. 
    • Ability to trigger an email, when the account admin or account representative creates or updates the contract. 
    • Ability to trigger an email, when the account admin or account representative made any change in the account information or account status.
  • As part of GDPR compliance, ability to export customer data (like profile data, payment, orders, etc.) and send as an attachment via email. [SECOM-41325]
  • Capability to send emails with attachment has been provided in the Notification service. [SECOM-41387]

Order Service

The following new features or changes have been implemented in the Order Service for this release:

  • Ability to associate a cost center to an order by a buyer org user. [SECOM-41589]
  • The following privileges have been added pertaining as part of this story [SECOM-41590]:
    • Ability for a buyer admin to view all the orders placed by the different buyer users within the account. 
    • Ability for a buyer user to view only the orders placed by the respective buyer user within the account. 
    • Ability for an account rep to view all the orders of a specific account.

Promotions Service

The following new features or changes have been implemented in the Promotions Service for this release:

  • Ability to configure promotions depending upon the Account Type, Account ID, and/or Account Representative fields that are associated with B2B. [SECOM-1308]
  • Ability to support UTF-8 characters in all the fields of the Promotions service. [SECOM-32680]
  • The minimum value in the project name has been revised to two characters. [SECOM-39455]
  • Ability to search for promocode list by its partial name. [SECOM-35397]
  • Ability to search for promotion list by its partial name. [SECOM-35398]

Search Service

The following new features or changes have been implemented in the Search Service for this release:

  • The following new features have been implemented pertaining to B2B as part of this story [SECOM-39498]:
    • Ability to associate roles, such as Buyer Admin and Buyer User for search APIs of B2B Workflow.
    • Ability to search for account-specific products.
  • Ability to honor a SKU with subscribe-able property and frequency information as it is passed to StoreFront and StoreFront Orchestration. [SECOM-39571]
  • The following new features have been implemented pertaining to B2B as part of this story [SECOM-39499]:
    • Ability to search for any products.
    • Ability to obtain suggestions specific to the buyer-user account.
    • Ability to search, view, and/or access the suggestions for the product or category.
  • The following new features have been implemented pertaining to B2B as part of this story [SECOM-41452]
    • Ability to load suggestions of Categories and Products based on Catalog ID and/or Navigation ID.
    • Ability to load group suggestions of Products based on Catalog ID.
  • Ability to segregate the associated Pricelist for each SKU. [SECOM-41453]
  • Ability to calculate the price of the Bundle and SKU KIT products when it is reindexed in SOLR. [SECOM-41173]

Subscription Service

The following new features have been implemented in the Subscription Service for this release:

  • Ability to retrieve the list of collections that is available for the Subscription service. [SECOM-3392]
  • Ability to modify the collection information for the Subscription service to manage the subscription details. [SECOM-3391]
  • Ability to cancel an active subscription request. [SECOM-3445]
  • Ability to submit or create a subscription request for a subscribe-able product. [SECOM-3349]
  • Ability to edit the subscription request information. [SECOM-3455]
  • Ability to create a collection for the Subscription service. [SECOM-3388]
  • Ability to process the subscription orders on a periodic basis, based on the frequency opted while subscribing. [SECOM-10073]
  • Ability to search and refine the subscription request within its collection, which is associated with the Store. [SECOM-39481]
  • Ability to send an email notification to inform a user about the subscription order that would be processed based on the subscription request placed. [SECOM-39483]
  • Ability to post events for the following instances [SECOM-3608]:
    • Success or failure of a subscription request placement
    • Order processing intimation email
    • Cancel subscription
    • Update to subscription request, for example, quantity, shipping address, and payment information
  • Ability to retrieve the subscription request information. [SECOM-3375]
  • Ability to search and view the refined set of collections. [SECOM-39429]

Release Changes for Skava Commerce Admin Consoles

Common Changes – Admin Console

  • The following Admin consoles have been refactored for better consistency and improved look and feel:
    • Accounts [SECOM-39492]
    • Catalog [SECOM-39485]
    • Customers [SECOM-39490]
    • Merchandising [SECOM-39487]
    • Notification [SECOM-39491]
    • Order [SECOM-39489]
    • Pricing [SECOM-39486]
    • Promotions [SECOM-36760]
  • Common date format has been implemented across all Admin consoles. [SECOM-41360]

Accounts Admin Console

The following new features or changes have been implemented in the Accounts Admin Console for this release:

  • Ability to associate the merchandising site navigation for an account. [SECOM-39513]
  • Ability to update appropriate comments while updating the account status. [SECOM-3628]
  • As an account admin, ability to update the existing contract (Catalog, Pricing, Merchandising, payment method, payment term, and/or credit limit) of an account. [SECOM-19251]
  • The following new features have been implemented as part of this story [SECOM-3613]:
    • As an account admin, ability to assign the account to an account representative for managing the account.
    • Ability to send an email notification to the account representative after associating with an account.
  • The following new features have been implemented as part of this story [SECOM-39449]:
    • Ability to trigger an invitation email when the account admin or account representative creates an account.
    • Ability to trigger an email to activate the buyer admin when the contract is created. 
    • Ability to trigger an email, when the account admin or account representative creates or updates the contract. 
    • Ability to trigger an email, when the account admin or account representative made any change in the account information or account status.
  • Ability to add or update the account details such as phone number and account size. [SECOM-3606]
  • Ability to view the list of accounts with buyer admin email address column along with Account Name, Account ID, Account Representative Name, Account Status, Payment Method, Payment Term, and Contract Expire Date. [SECOM-19272]
  • Ability to view the list of contracts for an account with contract ID and expiry date, and an option to update the contract. [SECOM-39514]
  • Ability to view all the account orders. [SECOM-41442]
  • Ability to view all the users of an account. [SECOM-41439]
  • Ability to index the combination of catalog, pricing, and navigation when updating an existing contract or creating a new contract. [SECOM-41432]
  • Ability to add multiple contracts per account at a different date range. [SECOM-41430]

Catalog Admin Console

The following new features or changes have been implemented in the Catalog Admin Console for this release:

  • Ability to set the subscription frequency for a subscribe-able SKU by an admin user. [SECOM-39569]
  • Handling standard roles and privileges for Catalog Admin have been provided. [SECOM-20892]
  • Ability to set the subscription order processing information for a SKU. [SECOM-39570]
  • The Accounts Admin console has been improved for better consistency and look and feel. [SECOM-39485]
  • The following changes have been implemented as part of this ticket [SECOM-41099]
    • The tab ‘NOTES’ has been added in the project’s Details page with an ability to add project notes when the project status is Open, Submitted, or Approval Failed.
    • Ability to add or update a default category ID in the Basic Information page for a product.
    • Ability to add a UPC ID (Universal Product Code) in the Basic Information page for a SKU.
  • Ability to add products that are approved (Default projects) or not yet approved (Current projects) in the Relations, Bundle, Fixed Bundle, SKU Kit, or Collection tab. [SECOM-41478]
  • Ability to display a progress bar while exporting all the catalog data. [SECOM-41477]
  • Ability to view the import history details for a collection in the Import tab. [SECOM-41326]

Customers (User) Admin Console

The following change has been implemented in the Customers (User) Admin Console for this release:

  • Ability to assign the Customer Admin role to the user and perform appropriate actions. [SECOM-39106]
  • Ability to delete the customer’s account as part of GDPR compliance in the CSR perspective. [SECOM-41247]

Foundation Admin Console

The following new features or changes have been implemented in the Foundation Admin Console for this release:

  • Ability to enable or disable subscription microservice while creating a business. [SECOM-31631]
  • Ability to associate subscription microservice for a store. [SECOM-31634]
  • Ability to trigger B2B related feeds when the user clicks on “Refresh Product Data” or “Refresh Catalog Data” button in the StoreOps page. [SECOM-41554]
  • The services will be displayed in the StoreOps page based on the associated privileges. [SECOM-41330]

Merchandising Admin Console

The following new features or changes have been implemented in the Merchandising Admin Console for this release:

  • Ability to delete an approved category within the project and when the category is not associated with any site navigation. [SECOM-35610]
  • Ability to view the import summary and download the failed items containing the reason for failure in an excel sheet to the local computer. [SECOM-35620]
  • Ability to export attributes, categories, site navigations, and milestones available within a collection or project. [SECOM-35621]
  • Ability to add products to a category by using keyword. [SECOM-37492]
  • Ability to clone a milestone within category and site navigation. [SECOM-35451]
  • Ability to create multiple site navigations within a project. [SECOM-35448]
  • Ability to view the list of site navigation created for the particular merchandising or collection. [SECOM-39890]
  • The following changes have been implemented as part of role-based access control in the Merchandising Admin console [SECOM-31855]
    • Merchandising Admin can perform all functionalities. 
    • Merchandising Editor can perform all functionalities other than approve, deny, or reopen a project.
  • Added Settings tab within the Merchandising admin console to manage collection properties and category attributes. [SECOM-35449]
  • Ability to import merchandising details (such as categories, site-navigations, and its milestones) by browsing or dragging and dropping the file via a project. [SECOM-35447]
  • Ability to download a sample sheet for importing attributes, categories, site navigations, and milestones along with the guidelines to import. [SECOM-35619]
  • Added option to create a milestone automatically while creating a category. [SECOM-36524]
  • Verified the privileges for import, export, and settings page. [SECOM-41329]
  • The following changes have been implemented as part of role-based access control in the Site Navigation Milestone page [SECOM-40995]:
    • Ability to move one or more categories by using pick and drop functionality.
    • Ability to search categories based on category ID.
    • Ability to show Category ID on hover over the category name.
    • Ability to render categories based on sequence and retain the same sequence. The sequence supports integer and float values.
    • Ability to see the grayed out disabled category rows.
  • The Category Builder page has been refactored for improved look and feel. [SECOM-41396]
  • Ability to see the import history in the import tab within the merchandising collection. [SECOM-40994]

Notification Admin Console

The following new features or changes have been implemented in the Notification Admin Console for this release:

  • As part of role-based access control, Notification Admin can perform all functionalities (such as creating notification events and/or searching the existing notification events by attributes) within the Notification Admin console. [SECOM-39393]
  • The Notification Admin console has been improved for better consistency and look and feel. [SECOM-39491]

Order Admin Console

The following change has been implemented in the Order Admin Console for this release:

  • Order Admin can perform all functionalities (such as viewing all the orders and/or searching the orders by attributes) within the Order Admin console. [SECOM-39390]

Pricing Admin Console

The following new change has been implemented in the Pricing Admin Console for this release:

  • As part of role-based access control, Pricing Admin can perform all functionalities within Pricing console and a Pricing Editor can perform all functionalities, except they cannot create or edit pricelist, add price types, and approve, deny, or reopen a project. [SECOM-19266]
  • The Import History page has been moved from the left navigation to the Import tab. [SECOM-41244]

Promotions Admin Console

The following new features or changes have been implemented in the Promotions Admin Console for this release:

  • Ability to download the promotion list to the local computer in the CSV format file. [SECOM-35396]
  • Ability to download the list of promo codes to the local computer in the CSV format file. [SECOM-35395]
  • Ability to click “View All Projects” button and view all the existing projects. [SECOM-35641]
  • As part of role-based access control, Promotion Admin can perform all functionalities within Promotion console and a Promotion Editor can perform all functionalities, except they cannot approve, deny, or reopen a project. [SECOM-39465]
  • Capability to support case insensitive search on providing a full name or partial name of the list or promocode list. [SECOM-41624]
  • The status field has been hidden when a promotion group or promotion has been expired. [SECOM-41206]
  • Capability to support UTF-8 characters for Project Name, Promotion Group Name, Promotion Name, etc. [SECOM-41295]

Subscription Admin Console

The following new features have been implemented in the Subscription Admin Console for this release:

  • Ability to retrieve the list of collections that are available for the Subscription service. [SECOM-39425]
  • Ability to refine or search and view the list of subscription requests, which is placed as part of an associated collection to the store. [SECOM-39394]
  • Ability to view a list of subscription requests, which is placed as part of an associated collection to the store. [SECOM-39395]
  • Ability to search and view the refined set of collections. [SECOM-39427]
  • Ability to edit a collection for the Subscription service. [SECOM-39424]
  • Ability to create a collection for the Subscription service. [SECOM-39423]
  • Ability to cancel an active subscription request. [SECOM-40600]

15 July 2019 (8.3.0)

Release Changes for Storefront Orchestration Service

The following new features or changes have been implemented in the Storefront Orchestration Service for this release:

  • Ability to set the unique username for the storefront user account. [SECOM-37522]
  • Ability to access the variable price in the cart page of the storefront user. [SECOM-31767]

Common Changes – Admin Console

All the admin consoles (except Foundation and Authorization) have been entirely refactored for better consistency and improved look and feel. [SECOM-36608, SECOM-36754, SECOM-36755]

Common Changes – Microservice

The following changes have been implemented across all Skava Commerce microservices:

  • Support for API gateway key has been provided for all the microservices. [SECOM-36704]
  • The collection ID parameter is included in the preauthorize call for all the microservices. [SECOM-36613]

Release Changes for Skava Commerce Infrastructure

The following new features or changes have been implemented in the Infrastructure for this release:

  • SOLR has been upgraded to version 7.7 in the Skava Cloud production environment. [SECOM-36898]

Release Changes for Skava Commerce Microservices

Accounts Service

The following new feature or change has been implemented in the Accounts Service for this release:

  • Ability to add the account specific privileges for all the standard roles. [SECOM-38020]

Authorization Service

The following new features or changes have been implemented in the Authorization Service for this release:

  • The duration for the session timeout is 1 hour for the business users like instance admin, business admin and other business users with specific roles. Also, the token will get refreshed based on certain duration which shall also be maintained as configuration. [SECOM-35274]
  • Support for Open Id – Implicit flow has been provided. [SECOM-36627]
  • All the session configuration properties which are common for storefront users and admin users have been moved from ZooKeeper to Collection properties. Also, the session is configurable per business requirement. [SECOM-36633]
  • Ability to create or update roles and privileges in a single API request. [SECOM-36632]
  • Ability to fetch all the privileges of a role. [SECOM-36534]
  • Ability to add the store ID as an additional attribute in the User Role request. [SECOM-36533]
  • Ability to set the admin user idle session timeout as 4 hours. [SECOM-36622]
  • A business admin should not have the privilege to disable another business admin. [SECOM-36177]
  • Ability to retrieve the collection ID and the service type. [SECOM-36993]

Catalog Service

The following new features or changes have been implemented in the Catalog Service for this release:

  • Ability to map default category ID for a product using attribute ID. [SECOM-36357]
  • A new attribute field type OptionalMultiList has been added, which allows adding custom values into a product apart from the predefined values. [SECOM-36525]
  • A user with the privilege catalog/readall/collection can load all the collections. [SECOM-38046]
  • The catalog message property file has been corrected to respond with the appropriate error message. [SECOM-38156]
  • The actual completion date of a project is automatically updated when a project status gets changed to approved or denied. [SECOM-34119]

Cart and Checkout Service

The following new features or changes have been implemented in the Cart and Checkout Service for this release:

  • Ability to add the cart and item level shipping tax. [SECOM-34795]
  • Ability to show the shipping charge split up in the cart. [SECOM-31691]

Feed Service

The following new features or changes have been implemented in the Feed Service for this release:

  • Ability to add custom list values to product and SKU. Earlier, it was allowed to add only the list values. [SECOM-36527]
  • Ability to reflect the category aliases in the categories by reindexing the category aliases. [SECOM-36697]
  • Ability to show the display name along with the attribute ID in the filter. [SECOM-36428]
  • Ability to reindex the categories sequence as it is authored in the Merchandising admin. [SECOM-37090 SECOM-36752]
  • Ability to honor the new fields keyword, alias category, and sequence number in the merchandise approval feed. [SECOM-38033]
  • Ability to import category, site navigation, etc. from the local computer to the Merchandising service. [SECOM-33092]
  • Ability to view the import summary and download the failed items containing the reason for failure in an excel sheet to the local computer. [SECOM-35696]
  • Ability to export the attributes, categories, site navigations, and milestones that are available within a collection or project. [SECOM-35697]

Foundation Service

The following new features or changes have been implemented in the Foundation Service for this release:

  • Storefront orchestration properties are renamed from  ‘Allow deletion’ and ‘Allow account deletion [text field]’ to ‘Allow customer deletion’ and ‘Retention period for customer deletion (GDPR)’ respectively. [SECOM-36600]
  • Provided an API (API calls: /stores, /stores/{storeId}, and /stores/{storeId}/associations) support to get the stores and their associated microservices based on the roles. [SECOM-36994]
  • Changed the default locale and default currency fields from mandatory to optional. [SECOM-37691]
  • Changed the storage link and CDN link from mandatory to optional. [SECOM-37669]

Merchandising Service

The following new features or changes have been implemented in the Merchandising Service for this release:

  • Ability to display categories in the storefront in the same order that has been authored in the Merchandising console. [SECOM-35690]
  • Ability to download a sample sheet for importing attributes, categories, site navigations, and milestones along with the guidelines to import. [SECOM-35695]
  • Option to migrate old filter format to a new filter format has been provided. [SECOM-36679]
  • The identifier for categories, milestones, site-navigations, and creatives have been made unique regardless of the case. [SECOM-36604]
  • Ability to add a category to multiple categories in the same Site Navigation tree (Alias Category). [SECOM-35689]
  • Ability to merchandise the products to different locales by the Merchandise admin. [SECOM-35692]
  • Added the separate privileges as follows [SECOM-38145]:
    • readall/collection privilege to Super Admin and Business admin.
    • read/collection privilege to  Merchandising Admin and Editor.

Notification Service

The following new features or changes have been implemented in the Notification Service for this release:

  • A user will be notified by email when business access is added or revoked. [SECOM-36366]
  • Ability to receive the confirmation email on partially canceling the order. [SECOM-37970]
  • Ability to receive the confirmation email on canceling the order. [SECOM-37969]
  • Ability to get the store level events while creating a notification collection. [SECOM-36276]

Pricing Service

The following new features or changes have been implemented in the Pricing Service for this release:

  • Ability to prompt a user to create evergreen price while schedule or tier price will be created. [SECOM-34883]
  • Ability to contain the same order of columns in both the export file and the downloaded sample sheet. [SECOM-36515]

Promotions Service

The following new features or changes have been implemented in the Promotions Service for this release:

  • Support for additional metadata/properties has been provided that will be useful while migrating existing promotion data from the other third-party systems. [SECOM-36570]
  • Ability to create a promotion offer targeting a specific set of products that match the business criteria configured and provide discounts against the summed up value of those specific items. [SECOM-1334]
  • Ability to set minimum and maximum discount amounts on the offer type ‘% Offer’. [SECOM-20119]
  • The Supported Locales and Default Locale options have been provided in the Collection Properties. [SECOM-36569]
  • Integration of notification service for triggering emails. [SECOM-38032]
  • Offer expiration date/time has been added in the Get Offers and Apply Offers response model. [SECOM-38015]
  • Ability to display only promotion applicable items in the Apply Offers response model based on the collection property value. [SECOM-37799]
  • The extension or plug-in capability has been provided which processes the item level and cart level promotions in a single request. [SECOM-37801]

Search Service

The following new features or changes have been implemented in the Search Service for this release:

  • Ability to run the complex queries including operations such as OR / NOT IN to find and manage products by the Merchandising Manager or Store Manager. [SECOM-36568]
  • Ability to map the product with the property defaultcategoryid, when the attribute includeAllCategories is set as false and there is no category specified in the request. [SECOM-36702]
  • Migrated the Search behavioral configuration and Catalog attribute configuration at SOLR classifier level instead of SOLR collection level. [SECOM-36804]
  • Added flag to represent whether the category is aliases or not. If it is an alias, the alias name has to be provided. [SECOM-37592]
  • When there is no category ID specified in the request, the category ID present in the product properties will be considered as the default category ID and will be sent in the response. [SECOM-36702]
  • Ability to see the categories sequence as it is authored in the Merchandising admin. [SECOM-35690]
  • Ability to group the search suggestions based on the attributes. [SECOM-36673]
  • Ability to return the product image along with the product list in the search suggestions. [SECOM-36674]
  • Ability to see the search suggestion and also suggest similar products for the given keyword or exact search criteria. [SECOM-36687]
  • Ability to return the products and the categories that match the search criteria. Earlier only product was returned in the search result. [SECOM-36672]
  • Added an optional field facetMinLimit in the “Find All Indexes” call to show the choices available for each attribute value upon selecting the attribute to be filtered. [SECOM-35922]

Customers (User) Service

The following new features or changes have been implemented in the Customers (User) Service for this release:

  • The Public Profile API returns user’s public profile, such as firstname/lastname for the given user identifier (email address or phone). [SECOM-36576]
  • Username identity support for login has been provided in addition to the existing email address and phone number as an identity for login. [SECOM-36575]
  • Username search capability has been included in the “Get All Users” call. [SECOM-38081]
  • Ability to send the user details in the Bearer token. [SECOM-37977]
  • A new API has been introduced to retrieve the user’s first name, last name, and type for a given collection. [SECOM-38151]

Release Changes for Skava Commerce Admin Consoles

Authorization Admin Console

The following new features or changes have been implemented in the Authorization Admin Console for this release:

  • Capability to invite multiple users with the same set of roles. [SECOM-19699]
  • As a business admin, ability to edit the existing business users and modify their roles as needed. [SECOM-36311]
  • As a business admin, ability to invite business users for the business with appropriate roles as needed. [SECOM-36310]
  • Ability to redirect to the appropriate landing page based on the user role. [SECOM-36601]
  • Triggering email notifications for the admin users when their roles are updated or deleted. [SECOM-36516]
  • The following changes have been implemented as part of this story [SECOM-36366]:
    • Ability to notify the respective business admin/user by email if new business access is given or the current business access is revoked.
    • Ability to notify the business user by email if a new role is assigned, the existing role is revoked.
  • Previously, the team menu appeared on the left navigation menu. Now, it will be visible only after navigating to a particular business. [SECOM-36374]
  • Ability to accept the terms and conditions from the Account Registration screen. [SECOM-36620]
  • Ability to set the admin user idle session timeout as 4 hours. [SECOM-36622]

Catalog Admin Console

The following new features or changes have been implemented in the Catalog Admin Console for this release:

  • A new attribute field type OptionalMultiList has been added, which allows adding custom values into a product apart from the predefined values. [SECOM-36526]

Foundation Admin Console

The following new features or changes have been implemented in the Foundation Admin Console for this release:

  • Ability to redirect to the landing page based on the user role. [SECOM-36601]
  • Ability to add links in the store properties and view the links in the StoreOps page by the Business Admin. [SECOM-36628]
  • Changed the business name and store name length to 255 characters. [SECOM-37498]
  • Changed the following fields from mandatory to optional [SECOM-37673]:
    • Storage Service Link
    • CDN Link
    • Default Locale
    • Default currency
  • Removed the export feature in the Business and Store Listing page. [SECOM-37698]

Merchandising Admin Console

The following new features or changes have been implemented in the Merchandising Admin Console for this release:

  • Ability to search category based on the category’s name. [SECOM-36602]
  • Ability to show the choices available for each attribute value upon selecting the attribute to be filtered while construct rule for category milestone. [SECOM-35922]
  • Ability to display the categories in a storefront in the same order that have been authored in the navigation builder. [SECOM-35608]
  • Ability to add a category to multiple categories (alias category) in the same site navigation tree structure. [SECOM-35622]

Pricing Admin Console

The following new features or changes have been implemented in the Pricing Admin Console for this release:

  • Ability to have left navigation menus for navigating to different pages. [SECOM-35677]

Promotions Admin Console

The following new features or changes have been implemented in the Promotions Admin Console for this release:

  • Support for additional metadata/properties has been provided that will be useful while migrating existing promotion data from other third-party systems. [SECOM-36571]
  • Ability to add multiple locales to a promotion where the message/description can be added according to the selected locale. [SECOM-24668]
  • The standard roles, such as Promotion Editor and Promotion Admin roles have been newly created where the editor can perform all activities except the project approval flow; whereas, a promotion approver can perform all activities. [SECOM-31648]
  • Ability to create a promotion offer targeting a specific set of products that match the business criteria configured and provide discounts against the summed up value of those specific items. [SECOM-38150]

Bug Fixes

This section highlights important bugs fixed in this release:

Service/Admin Name Description
Common Changes Handling of collections across all microservices have been made consistent for better user experience. [SECOM-35562]
Catalog Service The following changes have been implemented as part of this story [SECOM-36319]:

  • Ability to validate case insensitive unique Attribute ID, Product ID, SKU ID, and Sales Catalog ID. Previously, these identifiers were case-sensitive.
  • Ability to restrict the filterable attributes based on its datatypes. Previously, all datatypes were allowed as filterable attributes.
The Product/SKU filter and Age Limit filter are working appropriately now when an attribute field type is set as an integer. [SECOM-35983]
Feed Service The product or SKU reflects appropriately in SOLR based on the product or SKU’s status in the Catalog Admin. [SECOM-35652]
The categories in SOLR is reindexed appropriately even if the navigation milestone is not defined. [SECOM-36271]
Multi-locale support has been added to the catalog collection. Previously, the default locale was supported. [SECOM-35740]
Ability to honour the variable min and variable max price range in the reindexer. [SECOM-35626]
The case-sensitive issues in the field type value of the product, SKU, and attribute have been resolved. [SECOM-34907]
The rule issues have been resolved by changing the category to the independent category. [SECOM-36272]
The error has been resolved in SOLR when unused filterable attributes present in the Catalog. [SECOM-35366]
The queues creation issue has been resolved by separating the RabbitMQ virtual host at the business level. [SECOM-35931]
Category details will not exist in SOLR collection when the parent category does not have a milestone. [SECOM-35745]
The count mismatch issue of the SKUs and products has been resolved. [SECOM-34312]
The milestone priority issue has been resolved by considering the milestone based on the priority, recent start time, or end time. [SECOM-35748]
The support has been added to the catalog attributes to avoid the error. [SECOM-36161]
Pricing Service Ability to update floor price and/or bundle price while updating the price to null. [SECOM-36536]
The price overlap error message is displayed appropriately while creating or editing a price. [SECOM-35514]
Ability to accept decimals in the subscription percentage. [SECOM-36626]
Previously, only 50 prices were considered while retrieving the exact price. Now, the maximum of 1000 prices will be considered. [SECOM-36208]
Search Service The support has been added to the display name of the attribute based on the locale. [SECOM-36428]
Customers (User) Service Ability to redirect to Skava Commerce Login screen if the entered OTP is invalid after the configured number of attempts. [SECOM-36563]
The appropriate HTTP status code and the response message are displayed on entering an invalid user ID. [SECOM-34421]
Foundation Admin Associating the Authorization collection to the multiple store issue has been resolved as follows [SECOM-35219]:

  • Modify the authorization collection association of a store by a Store Manager. [SECOM-36598]
  • Edit the authorization collection name by the Business Admin. [SECOM-36599]
Super Admin can enable the business(es), which was disabled earlier. Previously, if a business ID is disabled, Super Admin cannot enable it. [SECOM-35783]
Business Admin can not add any new services that are not selected during business creation by the Instance Admin. [SECOM-36625]
Accessing the disabled microservices through Admin deep link has been restricted. [SECOM-33475]
Association of the Account microservice with B2C store has been resolved. [SECOM-36623]
Authorization Admin Ability to redirect to Skava Commerce Login screen if the entered OTP is invalid after the configured number of attempts. [SECOM-36563]
Business must be chosen only after which a user can be invited with a role. [SECOM-35939]
Merchandising Admin The status “Approval In Progress” and “Approval Failed” have been added as part of the Project modal. [SECOM-36206]
Pricing Admin Ability to continue exporting the details successfully even after the user is navigating to another page. [SECOM-35184]
Ability to add mandatory facets without selecting price type when creating a price list. [SECOM-34870]
Ability to move SKUs among temporary projects. [SECOM-36184]
Catalog Admin The Product/SKU filter and Age Limit filter are working appropriately now when an attribute field type is set as an integer. [SECOM-36531]
The appropriate HTTP status code and the response message are displayed on entering an invalid user ID. [SECOM-34421]

08 April 2019 (8.2.0)

Release Changes for Skava Commerce Infrastructure

The following new features or changes have been implemented in the Infrastructure for this release:

  • The components AWS EKS, Elasticache, RDS Aurora, Secret Manager, MongoDB Atlas are being used for Skava Cloud or Skava Enterprise deployments. [SECOM-32416]
  • MySQL DB is encrypted in both transit and rest. [SECOM-32430]
  • MongoDB is encrypted in both transit and rest. [SECOM-32431]
  • AWS API Gateway is being used for request throttling. [SECOM-32474]

Release Changes for Skava Commerce Framework

The following new features or changes have been implemented in the Skava Framework for this release:

  • Ability to rotate the API gateway and secret keys after a configurable number of days. The number of days is configured in AWS. [SECOM-33826]
    Note: This is applicable ONLY for the Skava Cloud instance.
  • Ability to upgrade or downgrade the MongoDB to different Platform releases. [SECOM-34478]
  • Ability to access SecretManager via IAM (Identity and Access Management) roles instead of the access key and the secret key of AWS. [SECOM-34480]
    Note: This is applicable ONLY for the Skava Cloud instance.

Release Changes for Skava Commerce Microservices

Authorization Service

The following new features or changes have been implemented in the Authorization Service for this release:

  • DML in the role table has been updated for standard roles. [SECOM-31737]
  • Ability to link standard role to a group privilege. [SECOM-31738]
  • Ability to group a set of privileges and assign that group privilege to a role. [SECOM-31740]
  • The token format has been simplified to manage standard roles. [SECOM-31741]
  • Capability to create multiple standard roles through API. [SECOM-31743]

Cart and Checkout Service

The following new features or changes have been implemented in the Cart and Checkout Service for this release:

  • In cart, privileges have been introduced to define what actions are applicable to a guest user and what is applicable to a registered user. [SECOM-31850]
  • An event is posted on any action that triggers a data change via a create, update or a delete function. These events can be used to audit or trigger notifications as required. [SECOM-31849]
  • In the previous versions, a bundled product could have Main, Mandatory, Optional products. Going forward, a bundled product, by definition, will have only Mandatory and Optional products. The relevant changes have been accommodated in cart. [SECOM-31848]
  • Ability to support extension points to the customizable cart calculation, which enables a client to develop their own calculation logic and/or validation logic. [SECOM-31846]
  • The details of the user will be persisted in the cart. [SECOM-31845]
  • Ability to merge a guest user’s cart to the registered user’s cart. While merging the cart, if the same product or SKU is available in the guest user cart and the registered user cart, the quantity in the guest cart overrides the quantity in the registered user cart. [SECOM-31844]
  • The store identifier is displayed in the header for all the APIs. [SECOM-31843]
  • Ability to calculate tax at the cart item level. [SECOM-31842]
  • Ability to calculate shipping charges at the cart and cart item levels. [SECOM-31841]
  • Ability to calculate discounts at the cart and cart item levels. [SECOM-31840]
  • Handles the overall math calculation of cart that includes item prices, promotions, shipping, tax, etc. [SECOM-31839]
  • This validation checks for communication preferences. Based on the preferred contact method chosen, the relevant contact details need to be captured. [SECOM-31838]
  • This validation checks for the shipping method and shipping related information. [SECOM-31837]
  • This validation checks for the age limit (min age) for a user to purchase the products that require such verifications. Based on the date of birth in the user profile or the date entered manually, the age of the user is verified. Only if the age of the user is greater than or equal to the prescribed age limit, the user will be allowed to purchase the product. [SECOM-31836]
  • This validation checks for min and max purchase quantity of a SKU added to cart. The system will not let the user proceed further if the cart quantity of the item is less than the min or greater than the max quantity defined for the item. [SECOM-31834]
  • This will be an API that is used to handle calculations such as shipping, discount, and other math calculations. [SECOM-31832]
  • This will be an API that is used to handle validations such as minimum quantity, maximum quantity, age verification, etc. [SECOM-31831]

Catalog Service

The following new features or changes have been implemented in the Catalog Service for this release:

  • An option product or SKU’s property value has been added in the dynamic image URL. [SECOM-31808]
  • IsDelete node has been added to the product or SKU properties to indicate the property will be deleted or not. [SECOM-31807]
  • Ability to specify whether a defined SKU can be subscribable or not. [SECOM-31711]
  • Introduced the two new status “APPROVAL_INPROGRESS” and “APPROVAL_FAILED” as part of the Project workflow. [SECOM-31410]
  • A new product type “SKUKIT” has been added, which allows creating a product based on the selected SKUs. [SECOM-31408]
  • A new product type “Fixed Bundle” has been added with mandatory products in a fixed bundle. [SECOM-31407]
  • Ability to add a bundle into a Collection Product. [SECOM-29616]
  • The following changes have been implemented as part of this story [SECOM-20814]:
    • The “Status” will be deprecated and the values, such as OPEN, SUBMITTED, APPROVAL_INPROGRESS, APPROVAL_FAILED, APPROVED, DENIED have been moved to the “State”.
    • The Start time and end time have been removed from the Attribute.
    • The enable and disable have been renamed as True and False respectively.
    • The Project Status and Notes have been deprecated.
  • Ability to support special characters such as hyphen (-) and underscore (_) in product ID and SKU ID. [SECOM-33058]

Customers (User) Service

The following new features or changes have been implemented in the Customers (User) Service for this release:

  • Capability to login using the existing Google account credentials. [SECOM-19643]
  • Capability to login using the existing Facebook account credentials. [SECOM-19644]
  • Capability that permits a user to use one set of login credentials for accessing multiple applications. [SECOM-19663]
  • Capability to support two-factor authentication mechanism as part of the login validation process. [SECOM-20419]
  • Capability to support two-factor authentication mechanism for scenarios like adding item(s) to cart, updating payment details, etc. [SECOM-31721]
  • Extension point support has been provided for authenticating a user. [SECOM-31763]
  • Ability to push events for Resend Activation. [SECOM-31783]
  • Capability to merge a user when there is an active user session already for another registered user when their identity matches. [SECOM-31907]
  • Ability to support multi-factor authentication by generating a unique random OTP. [SECOM-33761]
  • Ability to validate the entered OTP. [SECOM-33768]

Foundation Service

The following new features or changes have been implemented in the Foundation Service for this release:

  • Ability to display all the active collections to associate to a particular store. [SECOM-31224]
  • When a store is created, a unique naming convention for Authorization and Accounts services are generated automatically using a modified regex pattern. [SECOM-31227]
  • Ability to update the service status as “true” in an instance for the deployed services. [SECOM-31782]
  • Ability to notify a business admin post disabling a business that includes disabling the API gateway and secret keys generated for that business. [SECOM-34760]

Lists Service

The following new features or changes have been implemented in the Lists Service for this release:

  • Ability to support the configuration of a fulfillment plugin for every Order collection. [SECOM-31615]
  • Ability to merge the lists of two users. There will be validations around list types that can be merged, etc. [SECOM-31847]
  • In list, privileges have been introduced to define what actions are applicable to a guest user and what is applicable to a registered user. [SECOM-31851]
  • Maintains the store ID at the list item level. When a cart has two items from different stores and in case the user does a save for later (list), then the user needs to know the store IDs that the products came from. [SECOM-32016]

Merchandising Service

The following new features or changes have been implemented in the Merchandising Service for this release:

  • Capability to set default filterable attributes for all categories. [SECOM-20958]
  • Capability to enter ID by a user in the entry field for Milestone, Navigation, and Creative. The identifier has been made mandatory for all the entities. [SECOM-30853]
  • The following changes have been implemented as part of this story [SECOM-30854]:
    • Capability to map products to the categories based on rules wherein a user can see a list of special products, which are boosted/buried.
    • Capability to enter a rule for the category has been provided.
  • The two new status “APPROVAL_INPROGRESS” and “APPROVAL_FAILED” has been introduced as part of the Project workflow. [SECOM-31182]
  • A new node “Top Navigation” with the value “true” or “false” has been introduced for Site Navigation, which represents the top-navigation tree to be shown in the storefront. [SECOM-31601]
  • A new configuration property “milestonePageSize” has been introduced in ZooKeeper, which manages the number of items returned in the “get all milestone” call. The default value has been set to 100. [SECOM-33093]

Notification Service

The following new features or changes have been implemented in the Notification Service for this release:

  • Ability to configure notification with events and its actions for email and SMS. [SECOM-6129]
  • Ability to search and view all the notifications. [SECOM-6141]
  • Ability to edit the event name and its actions for email and SMS. [SECOM-31787]
  • Converted macro for notification service in SMS. [SECOM-31901]
  • Associated service name to source for the Event entity. [SECOM-31902]
  • Third party Email or SMS has been moved to the plugin jars for the Notification service. [SECOM-31903]
  • Previously, support was given only for “To” with single email ID. Now, support has been given to “TO”, “CC”, and “BCC” with multiple email addresses. [SECOM-32439]
  • DML script has been developed to support the respective events. [SECOM-33762]
  • Ability to add notification name while creating or editing an event. [SECOM-34288]

Order Service

The following new features or changes have been implemented in the Order Service for this release:

  • Ability to maintain fulfillment history at the order level and the item level of an order. [SECOM-32073]
  • Support to exclude shipping charges for digital products has been provided as there is no physical delivery involved. [SECOM-32055]
  • The following changes have been implemented as part of this story [SECOM-32054]:
    • Ability to return a digital item or a digital order for the end customer.
    • Ability to initiate refunds against these returns.
    • Ability to process refund against the original payment method only.
  • Ability for order administrator to move the digital products to a valid unsuccessful end state (such as Unable to deliver, etc.) via the BPM workflow when the order cannot be fulfilled and to initiate the refund. [SECOM-32053]
  • Ability for order administrator to move the digital products to a valid successful end state (such as Delivered, etc.) via the BPM workflow when there is no fraud detected on the order after fraud review. [SECOM-32052]
  • Ability for order administrator to support the addition of a new process in the BPM workflow so that fulfillment of digital items can be handled via the relevant plugin for fulfillment. [SECOM-32051]
  • Ability for order administrator to create a workflow for digital products such that the status changes from fraud review to a valid end state (such as Delivered, etc.) so that cancellation of digital products is not allowed. [SECOM-32050]
  • The business users will now have the ability to define their custom model in BPM, wherein they can track their own information like remarks, item status, labels, etc. [SECOM-33065]
  • The data saved via the custom model will be part of the order response. The data created will be validated against the order model for correctness. [SECOM-33066]
  • For various order item status changes such as Cancelled, Returned, Shipped, etc. events are posted and notifications can be triggered by listening to these events. [SECOM-33067]
  • The collection attributes provide business users with the option to extend the validations on different business use cases via the validator classes. [SECOM-33068]
  • For various order item status changes such as Cancelled, Returned, Shipped, etc. events are posted. [SECOM-33071]
  • A sample jar implementation has been done to validate the inclusion of new item status in the BPM workflow. [SECOM-33078]
  • A sample jar implementation has been done to validate the inclusion of new item status in the BPM workflow and the same has been deployed in the OMS services. [SECOM-33079]
  • A sample jar implementation has been done to validate fulfillment processing. [SECOM-33083]

Pricing Service

The following new features or changes have been implemented in the Pricing Service for this release:

  • For migration purpose, in the absence of an Evergreen price for a SKU, the maximum value of the transaction price is used to create an Evergreen price. [SECOM-29523]
  • The Evergreen price has been made as mandatory for a SKU. A user cannot delete an Evergreen price while importing prices. A user cannot update an Evergreen price with Tiers and Schedules. [SECOM-31187]
  • The “Approval In Progress” and “Approval Failed” values have been added to the project status. [SECOM-31193]
  • Ability to return a single price for a SKU by filtering when the request includes quantity as well. [SECOM-31605]
  • For temporary projects, the deleted price is responded in the “Get All” call; however, for the default project, it is not responded. [SECOM-31685]
  • In the Import feed, the Evergreen price has been made as mandatory for a SKU. A user cannot update an Evergreen price with Tiers and Schedules. [SECOM-31875]
  • The import and export formats have been updated to maintain consistency. [SECOM-33091]
  • Ability to clear cache after running the approval feed successfully. [SECOM-33210]
  • A new role “Editor” has been introduced. A user with the “pricelist/read/pricelist” privilege can view, create, and/or update project, price, price values, and notes. [SECOM-33654]

Promotions Service

The following new features or changes have been implemented in the Promotions Service for this release:

  • Support for updating all attributes of a particular list. [SECOM-20408]
  • Support for updating specific list attributes. [SECOM-20409]
  • Support for deleting an existing list. [SECOM-20412]
  • Support for clearing an existing list. [SECOM-20415]
  • Support for promotion lists in promotion conditions and action conditions. [SECOM-20436]
  • Rule engine support for handling promotion lists. [SECOM-20440]
  • Support to set role-based access controls, which provides appropriate permissions. [SECOM-20461]
  • Support to publish the approved promotion groups and promotions data from the staging environment to the production environment. [SECOM-28293]
  • Support to hard delete a promotion group or promotion within a project that is not yet submitted for approval. [SECOM-31585]
  • Support to approve a project depending on role-based access. [SECOM-31662]
  • Support to download a promotion list has been implemented. [SECOM-31753]
  • Support to upload a promotion list has been implemented. [SECOM-31754]
  • Event queue support has been provided for all API calls. [SECOM-31786, SECOM-28845]
  • Support to provide product suggestions in the promotion condition values automatically, which enables to narrow down the search. [SECOM-31919]

Search Service

The following new features or changes have been implemented in the Search Service for this release:

  • Implemented the changes to the API(s) to retrieve suggestions in the search. [SECOM-34532, SECOM-34533]
  • Ability to support search in Storefront Orchestration by consuming the relevant API to retrieve suggestions. [SECOM-34665]

Feeds Service

The following new features or changes have been implemented in the Feeds Service for this release:

  • Ability to check when the successful completion of Import, Approval, Sales Catalog Rules, and Publish feed, the event will be posted. [SECOM-29678]
  • The import feed has been optimized, which reduces the time taken for enriching the catalog. [SECOM-29740]
  • Ability to download the failed items with additional column ‘Error Description’ that describes the error. [SECOM-30822, SECOM-31822]
  • Ability to delete a product or SKU attributes in bulk. [SECOM-31312]
  • Ability to import product-SKU mapping row-by-row by using the sheet productskumapping. [SECOM-31804]
  • Ability to update the imageurl value in the imageswithtext sheet based on the entered value. If available, the same is updated; else, it is updated as blank to support dynamic URL generation. [SECOM-31823]
  • Ability to support the special characters such as hyphen (-) and underscore (_) in product ID and SKU ID of import feed. [SECOM-33060]
  • Ability to request access for Skava Commerce with the required service(s) and its seed data. [SECOM-33801]
    Note: This is applicable ONLY for the Skava Cloud instance.

Release Changes for Skava Commerce Admin Consoles

Authorization Admin Console

The following new features or changes have been implemented in the Authorization Admin Console for this release:

  • Ability to list the business users in the Team listing page. [SECOM-4613]
  • Ability to invite users by accessing the Team page from the left-navigation menu by an instance or business administrator. [SECOM-8947]
  • Capability to resend an activation email for the non-activated user(s). [SECOM-24953]
  • Capability to invite a user as instance or business administrator depending upon the logged in user role. [SECOM-25078]
  • Ability to edit an existing Admin user. [SECOM-25096]
  • Ability to authenticate users only if there is an appropriate API gateway key and secret key. On successful, processes the request for OTP generation. [SECOM-33763]
  • Ability to orchestrate the generated OTP and send out an email notification to the user who tries to log-in. [SECOM-33764]
  • Ability to enter OTP as part of log-in along with the credentials as part of multi-factor authentication. [SECOM-33765]
  • Ability to retry OTP as per the configurable number of times. [SECOM-33766]
  • Ability to resend OTP as per the configurable number of times. [SECOM-33767]

Catalog Admin Console

The following new features or changes have been implemented in the Catalog Admin Console for this release:

  • The import and approval statuses (such as In progress or Completed) is displayed when navigating from other screens as well. [SECOM-31718]
  • Ability to clear the microservice cache after the successful completion of the Import, Project Approval, and/or Sales Catalog Rules. [SECOM-31717]
  • Introduced the two new status “APPROVAL_INPROGRESS” and “APPROVAL_FAILED” as part of the Project workflow. [SECOM-31649]
  • In the Project > SKU tab, ability to view the SKU list from the approved project and current project. [SECOM-31638]
  • Ability to mark a SKU as eligible for a subscription so that subscription offers can be processed in the multiple services. [SECOM-31624]
  • Ability to view the Product & SKU information from the Product-SKU listing page. [SECOM-31623]
  • Ability to download the log file, which contains errors during import. [SECOM-31619]
  • Ability to display the deleted product or SKU property value in the grayed out format and in the disable mode in the Product/SKU Attribute tab. [SECOM-31418]
  • Previously, the Project was selected first before a user makes any changes to any product/SKU data. Now, all the possible actions on the data will be presented up front and when the user selects to edit, the project model is presented to enable the user to select the desired project. [SECOM-31388]
  • Ability to add the bundle products into the collection products. [SECOM-31241]
  • The Project Details Page has been modified as per the new creative. Previously, only user ID was displayed. Now, created by and updated by fields are displayed. [SECOM-30827]
  • Product and SKU listing page, option to filter project or SKU based on its properties. [SECOM-30825]
  • Honors Attribute Group in the Attribute page. [SECOM-30697]
  • A new product type “Fixed Bundle” has been added with mandatory products in a fixed bundle. [SECOM-29622]
  • A new product type “SKUKIT” has been added, which allows creating a product based on the selected SKUs. [SECOM-29621]
  • Ability to allow alphanumeric, special characters, such as hyphen (-) and underscore (_) in the product ID and SKU ID. [SECOM-33059]

Foundation Admin Console

The following new features or changes have been implemented in the Foundation Admin Console for this release:

  • Ability to view all the active collections for a service and associate a specific collection for a service within a store. [SECOM-31224]
  • In the release 7.5 until 8.1.0, while creating a business, all the business information, activating microservices, additional properties were stacked in a single page. Now, these have been segregated as separate tabs, such as [SECOM-31225, SECOM-33827, SECOM-33769]:
    • Business Information tab – Ability to create or edit the business metadata have been provided.
    • Available Microservices tab – Ability to enable or disable microservices have been provided.
    • Secrets & Events tab – Ability to view, add or terminate a secret key and API gateway key, and ability to view the key and value pairs of the RabbitMQ configuration. Part of business creation API gateway key and the secret key would be generated automatically.Note: The API gateway key feature is applicable ONLY for the Skava Cloud instance.
    • Advanced tab – Ability to add, edit, or remove additional properties have been provided.
  • In the release 8.1.0, in the StoreOps page, all the services were displayed on clicking on the Pancake menu. Now, the admin console services that are associated with a collection within a store will only be displayed on clicking the Pancake menu. [SECOM-31226]
  • Ability to create a collection with a unique name that was created automatically for Authorization and Accounts services. [SECOM-31227]
  • Ability to add a new or delete an API gateway or secret keys by an instance admin based on the request from the business admin. [SECOM-33770]Note: Adding a new API gateway key and deleting the existing API gateway key features are applicable ONLY for the Skava Cloud instance.
  • Ability to view the event configurations for the business by a business user. [SECOM-33772]
  • Ability to create an API gateway key automatically for a business. [SECOM-33799]Note: This is applicable ONLY for the Skava Cloud instance.
  • Ability to opt-in seed data for the enabled services while creating a business by an instance admin. [SECOM-33823]
  • Ability to disable a business, which includes disabling the API gateway and secret keys generated for that business. [SECOM-33824]Note: Disabling the API gateway key feature is applicable ONLY for the Skava Cloud instance.
  • All microservices honors business status or API gateway and secret key, only if it’s active response is sent. [SECOM-33825]Note: Honoring the API gateway key feature is applicable ONLY for the Skava Cloud instance.
  • Ability to notify a business admin post disabling a business that includes disabling the API gateway and secret keys generated for that business. [SECOM-34282]
  • Ability to notify a business admin post disabling a business that includes disabling the API gateway and secret keys generated for that business. [SECOM-34282]Note: Notifying on disabling the API gateway key feature is applicable ONLY for the Skava Cloud instance.

Merchandising Admin Console

The following new features or changes have been implemented in the Merchandising Admin Console for this release:

  • Ability to see all the available creatives listed within the creatives tab of the category milestone. Ability to add the required creative(s) to the template by clicking on the “Plus” icon. [SECOM-20983]
  • Ability to display the consolidated timeline in the Category Detail Page. Provision to expand and see the detailed view of the milestones for different priorities has been provided. [SECOM-20985]
  • Ability to display the consolidated timeline in the Site Navigation Page. Provision to expand and see the detailed view of the milestones for different priorities have been provided. [SECOM-20986]
  • To map products to the category, rules can be constructed either based on product attributes or product IDs. [SECOM-31174]
  • Project Approval workflow has been updated to accommodate two new status “APPROVAL_INPROGRESS” and “APPROVAL_FAILED”. [SECOM-31175]
  • Capability to override the default templates using a collection property “templates_and_widgets_repository_URL”. IDs for the templates are taken from the collection attribute “ids_to_be_used_in_template”. [SECOM-31492]
  • Capability to enter ID by a user in the entry field for Milestone, Navigation, and Creative. [SECOM-31601]
  • A category cannot be deleted if it has been added to active/unexpired navigation/milestone. [SECOM-31602]
  • Capability to set up sort order for a category’s milestone, which enables to view the products arranged based on the required sortable attributes. [SECOM-31775]

Notification Admin Console

The following new features or changes have been implemented in the Notification Admin Console for this release:

  • Ability to get all the notifications for a particular collection. [SECOM-33893]
  • Ability to create a notification with the event name and action details. [SECOM-33905]
  • Ability to edit the existing notification with event name and action details. [SECOM-33907]

Payment Admin Console

The following new features or changes have been implemented in the Payment Admin Console for this release:

  • Added the validators corresponding to payment service as collection attributes. [SECOM-31688]
  • Ability to display an appropriate error message to the user via the payment service when the failure responses received from Cybersource in transactions such as payment creation, token creation, CVV validation, etc. [SECOM-31793]
  • The following changes have been implemented as part of this story [SECOM-31797]:
    • Ability to allow multiple retries to the user for the failed charges with the same or alternate cards.
    • Ability to allow Admin to use a new transaction type ‘Credit’ for the failed refund.
  • Ability to allow only a single payment type’s provider master to a collection during collection provider creation. [SECOM-31805]
  • Ability to define the list of properties in which the attribute keys (for example, expiry month, year, or any of the payment related data) need to be defined. [SECOM-31806]

Pricing Admin Console

The following new features or changes have been implemented in the Pricing Admin Console for this release:

  • Ability to view the import history in the IMPORT HISTORY tab by displaying the import file name, import type, project ID, imported date and time, a user who has imported the file, success or failed status, option to view the summary, and option to export the failed items. [SECOM-10262]
  • Ability to display a summary of the Import document to identify if there are any failed items and reason for the failure along with the number of created, updated, removed, and/or failed items. [SECOM-10264]
  • In the project details page, updated the admin console, based on the latest creative. Improvised the user experience by displaying a tooltip for all call-to-action in the Project workflow. [SECOM-29522]
  • The start time and end time fields with seconds are displayed appropriately in the Prices page. [SECOM-30031]
  • The project feed flow has been updated to reflect APPROVAL_IN_PROGRESS and APPROVAL_FAILED. [SECOM-31194]
  • Ability to delete a price, except the evergreen prices by a pricing manager. [SECOM-31206]

Promotions Admin Console

The following new features or changes have been implemented in the Promotions Admin Console for this release:

  • Capability to clone an existing promotion within the same or any other non-expired promotion group has been implemented. [SECOM-14162]
  • Capability to display suggestions in the promotion condition values automatically, which enables to narrow down the search. [SECOM-28291]
  • Capability to hard delete a promotion group or promotion within a project that is not yet submitted for approval. [SECOM-29823]
  • Capability to create a new promotion list has been implemented. [SECOM-31651]
  • Capability to load or view all the existing promotion list has been implemented. [SECOM-31774]
  • Support for dynamic lists provided for IN and NOT IN operators in promotion conditions and action conditions query builder. [SECOM-31784]
  • Capability to update an existing promotion list has been implemented. [SECOM-31785]
  • Orchestration support for cloning a promotion has been added. [SECOM-31869]
  • Orchestration support for deleting a promotion group and/or promotion has been added. [SECOM-31870]
  • Orchestration support for dynamic lists that are used for IN and NOT IN operators in promotion conditions and action conditions. [SECOM-31871]
  • Orchestration support to display suggestions in the promotion condition values automatically, which enables to narrow down the search. [SECOM-32035]
  • The promocode list and promotion list have been moved to the left navigation panel. [SECOM-34536]
  • The store and collection navigations have been removed from the breadcrumb and Promotions has been updated as All Groups in the breadcrumb. [SECOM-35103]

Search Admin Console

The following new features or changes have been implemented in the Search Admin Console for this release:

  • Ability to check bundle and collection products and reindex in the storefront, Merchandise Admin, and Store Preview related SOLR. [SECOM-30816]
  • Ability to read a message, fetch data from the respective database, convert to SOLR documents, and push it to SOLR. [SECOM-31818, SECOM-31819]
  • Ability to create SOLR collection by using default and custom classifiers for Storefront, Merchandise Admin, and Store Preview. [SECOM-31826, SECOM-34531]
  • Implemented role (instance admin, registered user, and guest user) based access for Search service. [SECOM-31829]
  • Ability to filter the product based on the category rule by passing its attribute. [SECOM-31987, SECOM-31814, SECOM-31813]
  • Ability to create SOLR collection by using default and custom classifiers for Storefront, Merchandise Admin, and Store Preview. [SECOM-34531]
  • Implemented event listeners for the category SOLR feed. [SECOM-34534, SECOM-34535]
  • Ability to retrieve top categories from microservices. [SECOM-34658]
  • Ability to retrieve PLP from microservices. [SECOM-34662]
  • Ability to retrieve PDP from microservices. [SECOM-34664]
  • Ability to search the information based on the search criteria. [SECOM-34666]
  • Ability to search based on the semantic ID. [SECOM-34669]

Release Changes for Storefront Orchestration Service

The following new features or changes have been implemented in the Storefront Orchestration Service for this release:

  • Ability to merge the cart items from the guest account to the registered account. [SECOM-31269]
  • Ability to share the list (Wish List, Favorite, or Save for Later) via email. [SECOM-31272]
  • Ability to show an appropriate error message when there are inactive items available in the cart. [SECOM-31275]
  • Ability to search with order identifier, order date, and order status. [SECOM-31444]
  • Ability to return any specific SKU or return a specific number of quantities in a SKU. [SECOM-31664]
  • Ability to cancel any specific SKU or cancel a specific number of quantities in a SKU. [SECOM-31665]
  • Ability to return any specific order. [SECOM-31666]
  • Ability to cancel any specific order. [SECOM-31667]
  • Previously, the calculation logics were handled by the Storefront Orchestration service. Now, it is handled by the Cart service and has been removed from the Storefront Orchestration service. [SECOM-31694]
  • Ability to merge cart items from guest account to the registered account. [SECOM-31695]
  • Ability to access the variable price in the cart page and validate the Min-Max range. [SECOM-31767]
  • Ability to merge the list and its items from the guest account to the registered account. [SECOM-31890]

04 February 2019 (8.1.0)

New Features and Enhancements

The following features and enhancements have been implemented in this release:

Component Name Description
All microservices Ability to add a business identifier for all events across all microservices. [SECOM-31873]
DevOps Ability to upgrade selected or all microservices by System Admin at any time without having downtime. [SECOM- 31707, SECOM-31221]
Foundation Admin Console Ability to create a business in the “Business Listing” page for the Instance Admin. In an instance, only an instance admin can create a business. A business admin can only edit the business details. [SECOM-31112, SECOM-31212]
Ability to support Business Admin role in all the admin consoles in addition to the Instance Admin. [SECOM-31663]
Ability to create an authentication secret for each business when creating a business. [SECOM-31366]
Ability to display a business-specific secret key in the “Business Overview” page. [SECOM-31367]
Ability to subscribe to the respective events for the businesses in the Skava Cloud. It is the extension point for the business to customize in the Skava Cloud. [SECOM-31588]
Promotions Admin Console Ability to navigate to all enabled microservices within a business in the pancake menu. [SECOM-31096]
Promotions Service Ability to provide a discount for the bundle products against the bundle-shipping price. [SECOM-1324]
Ability to provide a discount for the bundle products against the bundle price. [SECOM-30956]
Skava Framework Ability to segregate the logs for the business based on the business ID. [SECOM-31364]
Skava Infrastructure Added support to MongoDB Atlas. [SECOM-31218]
Ability to display the dashboard for each business based on the business ID. [SECOM-31364]
Added support to Amazon RDS, ElastiCache, Secrets Manager, and MongoDB Atlas. [SECOM-31222, SECOM-31295]
Used RabbitMQ credential with Admin tag instead of management tag for access by a business-specific user. [INFRA-16030]
Enabled the Shovel plugin with RabbitMQ server for SaaS. [INFRA-16041]

Bug Fixes

This section highlights important bugs fixed for Security component in this release:

  • Migrated server username and password from ZooKeeper to AWS Secrets Manager. [SECOM-30875]

23 January 2019 (8.0.2)

New Features and Enhancements

The following features and enhancements have been implemented in this release:

Service/Admin Name Description
Catalog Admin Console In the Import and Feeds Rules pages, the left menu has been made always visible. When accessing the respective menus, the user must select a project that has the “Open” status and displays the import or Feeds Rules screen immediately. [SECOM-29608]
Ability to configure the product and SKU settings. [SECOM-7240]
The Swatch image section has been newly added displaying Swatch Image, Swatch Text, and Link columns. [SECOM-30824]
Inventory Service Enables a user to search a string with space. [SECOM-31046]
Merchandising Service For handling multiple templates, the fields, such as template ID and template URL have been newly added to the Milestone entity. [SECOM-30979]
Retrieves the start time and end time for the given time zone in the collection property. Previously, the start time and end time captured from the system time zone (UTC). [SECOM-30973]
Returns only the default locale properties along with the requestor locale properties. Previously, all the locale properties were returned. [SECOM-30102]
Merchandising Admin Console In the Site Navigation builder, the categories will be aligned to the left in the grid. Previously, the categories were aligned to the center. [SECOM-30877]
The “Search” button has been renamed as the “Apply” button in the Product tab of Category builder page. [SECOM-30976]
The presentation of Alert message has been improvised by changing the component, which displays Alert title and message. [SECOM-30978]
In the admin console, a temporary fix for the start date has been made where the milestone’s start date will be reduced by 2 days. [SECOM-31054]
Previously, a user had no options to choose a template for a category. Now, the user can choose one template among multiple templates. [SECOM-30975]
Order Service Enables the user to search a string with space. [SECOM-31043]
Previously, when SKU ID and/or Bin ID were null or empty, an error message was not displayed. Now, an appropriate error message will be displayed. [SECOM-31042]
Next possible status of the order will reflect appropriately once the order is shipped. [SECOM-31041]
The Audit field has been newly added for the audit log. [SECOM-31504]
Payment Service Enables a user to search a string with space. [SECOM-31045]
Pricing Service Previously, the Evergreen price was not returned in the Exact Price API when a schedule matches. Now, the Evergreen price is returned along with the other prices. [SECOM-30970]
Previously, the Tier price was not indexed. With this update, the Tier price has been removed from the seed data. [SECOM-31337]
Promotions Service The Audit log has been implemented for all the APIs. [SECOM-9399]
Reporting Service Enables a user to search a string with space. [SECOM-31044]
Search Service Able to retrieve response for multiple filters. [SECOM-31018]
Optimized the performance of reindexer, which reduces the time taken for reindexing the products. [SECOM-32017]
Storefront Orchestration Services Camel routes have been reorganized and regrouped for modularity. [SECOM-20596]
For the PLP calls, the Merchandizing template has been added in the response. [SECOM-30988]
Tax Service A new SKU type field has been added to the CalculateTax model in the Tax service, which is consumed by the storefront orchestration service. [SECOM-31462]

Bug Fixes

This section highlights important bugs fixed in this release:

Service/Admin Name Description
Catalog Admin Console When creating dynamic attributes through the admin console, the header validation field was not updated correctly. With this update, the header is validated appropriately. [SECOM-31315]
Catalog Admin Console honored microservice Load API changes. [SECOM-30105]
Previously, the product IDs and SKU IDs search were not working when those IDs are given in the integer. Now, this issue has been fixed. [SECOM-31023]
Clears the cache once the approval status returns success by the Feeds History call. [SECOM-30929]
The selection of attributes for the variant group is more appropriate with this update. [SECOM-30898]
Previously, a user was able to select only the date. Now, the user can select a date and time. [SECOM-30693]
Catalog Service Previously, when loading the product and SKU information, time-related fields were not converted into the required collection time zone. With this update, this issue has been fixed. [SECOM-30819]
The Load API has been updated to accept the locale parameter when loading all the products or SKUs and loading a product or SKU by ID. If the locale parameter is not given, then all the products or SKUs will be displayed. [SECOM-30103]
As per the Approval Workflow process, creating a product or SKU in the default project is not allowed. [SECOM-29831]
Feeds Service The time zone is retrieved from the collection properties in the Import or Export feed. [SECOM-31038]
When running the sales catalog rules feed, initially overwrite option was defaulted to false. With this update, this is set to true which resolves the Catalog admin issues. [SECOM-30953]
Previously, the Export feed exported only the default locale properties of products and SKUs. With this update, the given locale parameter is accepted and properties of the given locale will be exported. [SECOM-30908]
With this update, the special characters are not allowed in the product IDs. It accepts only characters and integers. [SECOM-30904]
Merchandising Admin Console While generating a Note, the project Reopened state is saved as the Denied state. With this update, the state Reopened is reflected correctly. [SECOM-30813]
An ID of the deleted category is reused while creating a new category. [SECOM-30806]
While creating a category milestone, a deleted category ID will not be used in this release. Previously, a deleted category was used while creating a category milestone. [SECOM-30804]
Previously ampersand symbol (&) and forward slash (/) were not allowed in the category name. With this update, these symbols are allowed in the category name. [SECOM-30762]
Localization has been newly implemented to filter collection properties based on the given locale in the request parameter. The response will include default locale collection properties along with the requested locale collection properties. [SECOM-30413]
The target completion date was not reflecting correctly after submitting the project. With this update, this issue has been rectified. [SECOM-31257]
Payment Service A restriction has been removed to update multiple transactions for the same payment ID. [SECOM-31048]
The transaction expiry time issue has been fixed. [SECOM-31047]
In the audit log, the PII data will not be captured. [SECOM-30949]
Promotions Service Upgraded Query DSL, which supports more operators with improvised filter format. [SECOM-31005]
Enabled pre-authentication for the promotion service calls. [SECOM-22414]
Search Service Previously, when a special character is present in the product name, the search was not retrieved properly. Now, this issue has been fixed. [SECOM-31050]
Previously, the newly added products in the Catalog were not retrieved when searching with product ID after reindexing. With this update, the newly added products are retrieved correctly when a search is made with the product ID. [SECOM-31030, SECOM-31559]
Ability to search a product by product ID. [SECOM-31031]
The default values have been rectified in the collection properties. [SECOM-31028]
The multiple filters issue has been rectified. [SECOM-31018]
Storefront Orchestration Services The X-Auth-Token has been removed from all the responses of Store Front orchestration calls. [SECOM-24566]
Ability to add more than 10 items (configurable) in the cart. [SECOM-31000]
The Tire price is now displayed appropriately in the storefront. [SECOM-30934]
Previously, the price and regular price were shown with null values in the add-to-bag response when providing both the values. With this update, the configured prices are displayed with appropriate price value for Tier Price and Scheduled Price. [SECOM-31591]

21 December 2018 (8.0.0)

Common Changes

The following changes have been implemented across all Skava Commerce microservices:

  • All Admin consoles have been completely revamped with a new look and feel. The layout is consistent across all Admin consoles.
  • Skava Commerce Framework has been introduced where each microservice uses the framework as its basic building block for development.
  • Implementation has been done using Spring Boot framework across all microservices for RESTful APIs.
  • The Product Information Management (PIM) microservice has been deprecated and instead Catalog, Pricing, and Merchandising microservices have been created separately and will be independent of each other.
  • The Cart microservice has been made as a separate microservice containing only cart and checkout features. Previously, Address Validation, Shipping and Tax features along with Cart and Checkout features were part of Cart microservice. Now, these have been created as separate microservices and act as utility microservices to the Cart microservice.
  • Storefront Orchestration and Admin Orchestration in Skava Commerce have been newly introduced in this release. For more information, see Storefront Orchestration and Admin Orchestration in this document.
  • The collection, collection properties, and collection attributes have been implemented for all microservices to manage multiple microservice instances.

Skava Commerce Framework

Skava Commerce Framework has been newly introduced in this release. It is an entry point, which provides all the required ready-made components for the microservices and Admin Orchestration:

Component Description Dependent Microservice(s)
AuditLogComponent This component provides audit-logging capabilities. All microservices
AuthorizationComponent This component enables role-based authorization for the APIs using the Spring security. All microservices
BPMNComponent This component handles business process modeling. Order
Camel This component maintains the dependency management of the Camel framework. Admin Orchestration
ContentRepositoryComponent This component stores contents (docs, images, etc.) into the repository like s3, fileserver, etc. Feeds, Foundation, and Admin Orchestration
CoreComponent This component includes exception handler and validator components. The validator component makes validations at the model level using custom annotations. The validators can be custom defined at the microservice level. All microservices
CryptoComponent This component handles encryption and decryption.
  • Address
  • Authorization
  • Cart
  • Shipping
  • Tax
  • Customers (User)
Event This component provides messaging capability using RabbitMQ. All microservices, except:

  • Shipping
  • Tax
  • Feeds
  • Search
HibernateComponent This component provides SQL database capability using MySQL. All microservices, except:

  • Promotions
  • Catalog
  • Lists
  • Merchandising
LocalizationComponent This component obtains localized messages based on the locale using the resource bundle. All microservices
LogComponent This component provides loggers to make application logging. All microservices
MongoComponent This component provides MySQL database capability using Mongo.
  • Catalog
  • Lists
  • Order
  • Promotions
  • Feeds
  • Merchandising
MavenPluginComponent This component provides a template, which converts source code Swagger documentation into the YAML file. All microservices
QueryDSL This component is used by either Mongo or Hibernate for searching/filtering in the JPA and Mongo repository.
  • Catalog
  • Address
  • Cart
  • Lists
  • Shipping
  • Tax
  • Pricing
  • Promotions
  • Search
  • Merchandising
RedisComponent This component provides caching capability using the Redis cache. All microservices, except Feeds
RestTemplateComponent This component makes HTTP remote calls to other services or third-party plugins.
  • Feeds
  • Notification
  • All Admin modules
RuleEngineComponent This component generates and executes business rules in a runtime production environment. Promotions
SolrComponent This component performs various search operations, such as full-text search, hit highlighting, faceted search, real-time indexing, dynamic clustering, database integration, etc. Search
  • Implementation has been done using Spring Boot framework across all microservices for RESTful APIs.
  • All Skava Commerce microservices are independent with each other and dependent on Skava Commerce Framework.

Admin Orchestration

The following new endpoints have been created as part of Admin Orchestration. The endpoints from the following microservices are used to integrate microservice APIs with Admin console. The request from Admin console is sent to the Admin Orchestration APIs and the appropriate resources from various applicable microservices are retrieved. The Admin Orchestration composes the response and sends it back to the Admin console.

  • Foundation (Business and Store) / Common Admin
  • Catalog
  • Order
  • Merchandising
  • Promotions
  • Feeds
  • Customers (User)
  • Collection
  • Pricing
  • Accounts
  • Authorization

Storefront Orchestration

In the 7.5 release, Skava Stream was used as a data management and orchestration layer that performed transformation and data capture for requests flowing through the Release 7.5 Skava Commerce. In the Skava Commerce 8 release, it has been replaced by Storefront Orchestration. It is an Apache Camel-based orchestration layer. This layer integrates various microservices together. It serves as a central place for customer-specific business logic and an integration point for the third party or client’s in-house microservices. The following are the features of this layer:

  • Accepts a request from the storefront and makes the request(s) to the concerned microservice(s) and aggregates the response.
  • Consists of configurable flows (sequence of actions).
  • Caches data to improve performance.
  • Uses eventing for asynchronous processes.

The following endpoints have been created as part of the Storefront Orchestration for Skava Commerce 8:

  • Customers (User)
  • Accounts
  • Catalog
  • Cart
  • Order
  • Lists
  • Notification
  • Pricing
  • Promotions
  • Merchandising

For more information, see API Endpoints of Storefront Orchestration.

Skava Commerce Microservices

Accounts

This microservice has been newly implemented in this release with the following functionalities:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.

Seller Organization can perform the following functions via Accounts APIs or Accounts Admin console:

  • Ability to create a buyer account, where the mandatory fields are DUNS number, tax ID, account type, account size, and buyer email address. The system considers the given email address as the buyer admin.
  • Ability to manage contracts between buyer and seller. The contract covers catalog, pricing, and payment method (credit and PO). If the payment method supports the PO, then the payment term is mandatory.
  • Ability to upload the contract document and the contract expiry date.
  • Ability to manage the buyer account of a client.
  • Ability to assign an account by an account admin to an account representative.
  • Ability to manage the account status (such as Pending, Active, Inactive, Suspended, and Close). Login cannot be performed if the account status is pending or close. If the status is inactive, the user can log in but cannot browse the products. If the status is suspended, the user can log in, and browse the products, but cannot add a product to the cart. The account goes to the suspended status automatically if the payment is not made as per the payment term.

Buyer Organization can perform the following functions via Accounts APIs or Storefront:

  • Support for self-on-board where buyers can onboard themselves.
  • Ability to create or manage the cost-center.
  • Ability to create or manage a team with the standard roles (such as buyer admin and buyer user).
  • Ability to invite users.
  • Ability to reset the password.
  • Ability to manage profiles.
  • Ability to view the contracts.
  • Ability to place an order.

Note: See Skava Store 8 Release Notes.

Address

In this release, the Address microservice has been newly introduced containing all the Address features that were part of Cart microservice in the 7.5 release.

The following features have been added to the Address microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to support extension points to the third party address service providers.
  • OOTB support for Cybersource as an address validation service.
  • Ability to support Fallback for default validation (in case of third-party service being down).

Authorization

The authentication and authorization that were part of both Corporate Admin and Customers (User) microservices have been moved to a new service called the Authorization microservice. The following functions can be performed via the Authorization APIs or Authorization Admin console as part of this release:

  • Ability to create a collection and its properties (only API support is available).
  • Ability to manage the collection and its properties.
  • Ability to establish and manage a session for the users created with the Customers (User) microservice.
  • Ability to generate a JWT token, which contains session information and role/privilege information, which is used as a security token for all microservices.
  • Ability to log in to Skava Commerce admin.
  • Ability to manage roles available for each microservice (only API support is available).
  • Ability to add standard/custom roles with a set of new or existing privileges (only API support is available).
  • Ability to assign or modify a role to any user who already exists or who are currently being invited (only API support is available).

Foundation

The Business Onboarding and Store were separate microservices in the 7.5 release. Now, both have been combined under the Foundation microservice.

The following functions can be performed via Business and Store APIs or Foundation Admin console as part of this release:

Business Service:

  • Ability to view existing businesses.
  • Ability to create new business and enable one or more microservices.
  • Ability to update the existing business.
  • Ability to add users and set of roles to an instance.
  • Ability to edit the properties of an existing business.
  • Ability to view the list of stores within each business.

Store Service:

  • Ability to create an online store (B2C/B2B).
  • Ability to manage an online store (B2C/B2B).
  • Ability to associate microservice(s) to a store.
  • Ability to manage custom properties per store basis.
  • Ability to manage storefront orchestration properties.
  • Ability to schedule recurrence feed/on-demand feed.
  • Ability to preview a store.
  • Ability to clear the cache.

Cart

In this release, the Cart microservice has been made as a separate microservice containing only cart and checkout features. Previously, Address, Shipping, and Tax features along with Cart and Checkout features were part of Cart microservices.

The following functions can be performed via Cart APIs as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to add, edit, or delete cart items.
  • Ability to add or delete promo codes.
  • Ability to add, edit, or delete custom properties to a cart or cart item.
  • Ability to add, edit, or delete communication preferences to a cart.
  • Ability to add, edit, or delete shipping details to a cart or cart item.
  • Ability to add payment details to a cart.
  • Ability to edit the existing payment details in a cart.
  • Ability to delete a particular payment detail from a cart.
  • Ability to capture delivery instructions and the latest delivery date.
  • Ability to use extension points for address validation, tax, and shipping services.
  • Ability to merge guest cart items when a customer logs in.

Catalog

In this release, the Catalog microservice has been newly introduced containing all the Catalog-related features that were part of PIM service in the 7.5 release. The PIM service has been deprecated in this release.

The following functions can be performed via Catalog APIs or Catalog Admin console as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Manage master and sales catalogs within the context of a project approval workflow.
  • Create, view, and update products and SKUs.
  • Create, view, update and delete Attribute and Attribute Group or Variant Group.
  • Maintain product versions.
  • Manage product types such as Bundle and Collections.
  • Manage assets digitally.
  • Manage semantic or SEO URLs.
  • Import products and SKUs with its attributes from the local computer in the .xls format file to the Catalog service.
  • Export products and SKUs with its attributes to the local computer in the .xls format file.
  • Sales catalogs can be generated from the master catalog by defining rules.

Customers (User)

The profile management was part of both Corporate Admin and Customers (User) microservices in the 7.5 release. Now, it has been combined and called as Customers (User) microservice. The following functions can be performed via Customers (User) microservice or Customers (User) Admin console:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create an instance collection, which holds all the admin user profile information.
  • The collections associated with stores/business holds customer profile information under the specific store/business.
  • Every valid user can log in, log out, view his profile and can update it with more information like shipping address, security questions, etc.
  • An admin with a valid role (for example, CSR) can additionally view the customers under each business/store.
  • Ability to search the existing customers based on the various attributes, such as first name, last name, email address, and/or status.
  • Ability to view, add, or edit one or more shipping addresses and set an address to default.
  • Ability to update password by resetting through email or security questions (only API support is available).
  • Ability to opt-in or opt-out to any consent, which is available under each collection.
  • Ability to track user consent history by tracking a user’s activity.
  • Ability to add, view notes for each user profile, which is stored against each profile (only API support is available).
  • Ability to freeze or delete a customer account as part of GDPR compliance.
  • Ability to view, add, or edit payment card details (via Customers (User) Admin console or Payment microservice).
  • Ability to view the order history (via Customers (User) Admin console or Order microservice).

Inventory

The following functions can be performed via Inventory APIs as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create bins.
  • Ability to create bin items.
  • Ability to create transactions (Add, Remove, Transfer, and/or Reconcile) on bin items.
  • Ability to import bins, bin items, and/or transactions.
  • Ability to export bins, bin items, and/or transactions.

Lists

The following features have been added to the Lists microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create lists of different types (Wishlist, Favorites, etc.).
  • Ability to create lists for different item types (Product, SKU).
  • Ability to manage items within a list.
  • Access type support for lists (public, private) for sharing.

Merchandising

In this release, the Merchandising microservice has been newly introduced containing all the Merchandise and related features that were part of PIM service in the 7.5 release.

The following functions can be performed via Merchandising APIs or Merchandising Admin console as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to view, create, edit, and delete a category.
  • Ability to view, create, and edit a navigation (only API support is available).
  • Ability to view (only API support is available) or create a milestone for a category.
  • Ability to view (only API support is available), create, and edit a milestone for a navigation.
  • Ability to customize category product mapping for a category milestone.
  • Ability to customize category attribute mapping for a category milestone.
  • Ability to customize a template for a category milestone.
  • Ability to customize category hierarchy for a navigation milestone.
  • Ability to add new creative (assets) and edit the existing creative.
  • Ability to manage categories by admin users within the context of a project approval workflow.
  • Ability to publish a merchandising collection (only API support is available).

Notification

In this release, the Notification microservice has been newly introduced containing all the notification features.

The following functions can be performed via Notification APIs as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to configure the events.
  • Ability to configure the third-party email provider and/or SMS provider.

Order

In this release, the Payment related features have been removed from Order microservice and made as a separate microservice.

The following functions can be performed via Order APIs or Order Admin console for Order microservice:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create orders (from the services, not from the admin console) with the flexibility of having alphanumeric or numeric order IDs
  • Ability to cancel order items (partial/full) (only API support is available).
  • Ability to return order items (partial/full) (only API support is available).
  • Ability to have customized order item status (via the BPM workflow) (only API support is available).
  • Ability to refund to the original payment method (store credits is not supported) (only API support is available).
  • Ability to add notes to an order (only API support is available).
  • GDPR compliance with user details anonymization on the deletion of a user account (only API support is available).
  • Ability to view the list of orders, search orders, and view order details (only API support is available).

Feeds

The following features have been added to the Feeds microservice as part of this release:

  • Ability to create a feed.
  • Ability to run a feed on-demand.
  • Ability to schedule a feed.
  • Ability to obtain feed status.
  • Ability to view feed history.

Payment

In this release, the Payment microservice has been newly introduced containing all the payment features. The payment features were part of Order service & Cart service in the 7.5 release.

The following features have been added to the Payment microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create provider master configurations (Cybersource, Braintree, Default payment processing, etc.).
  • Ability to add payments using multiple payment methods.
  • Ability to add payment items.
  • Ability to create transactions for payments based on cash/non-cash types.
  • OOTB support for Cybersource as a payment provider.

Pricing

In this release, the Pricing microservice has been newly introduced containing all the pricing features that were part of PIM service in the 7.5 release.

The following functions can be performed via Pricing APIs or Pricing Admin console as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create and edit price facets (price types).
  • Ability to create and edit pricelists by associating the price types and a currency.
  • Ability to filter pricelists by its ID, name, currency, status, etc.
  • Ability to manage pricelists by admin users with different privileges within the context of a project approval workflow.
  • Ability to associate SKUs with a pricelist for different price values.
  • Ability to update the price of a SKU.
  • Ability to import multiple SKUs into a pricelist using .xlsx file.
  • Ability to filter SKUs using its ID, project, status, created by, created time, and its different price types.
  • Ability to configure a variable price.
  • Ability to export a price into the local computer.
  • Ability to publish a price (only API support is available)

Promotions

The following new features or enhancements have been made to the Promotions microservice or Promotions Admin console as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to launch Promotions.
  • Ability to search the approved promotion groups based on the name of a promotion group.
  • Ability to use filters within promotion group landing page such as Project, Priority, Status, Date Range, and Stop Further Processing.
  • Ability to search the approved promotions within a promotion group based on the promotion name, message, description, or promo codes.
  • Ability to use filters within the promotion landing page such as Priority, Status, Date Range, Offer On (previously Rule Type) and Offer Type (previously, Action Type).
  • Ability to create, edit, update and delete operations of the promotion group and promotions within the context of a project approval workflow.
  • Ability to approve, deny, or reopen projects that are submitted for approval.
  • Ability to view all live promotion groups and promotions that are approved.
  • Ability to manage promotion groups and promotions.
  • Ability to set up or schedule promotion group and promotion for a specific period of time.
  • Ability to configure business rules or conditions, set up promo codes and one or more actions around each promotion as required.
  • Ability to configure the promotion types, such as Item Price Offer, Item Shipping Offer, BOGO Offer (Buy X Get Y, Buy X & Y, Gift with Purchase), Cart Price Offer, and Cart Shipping Offer
  • Ability to configure the following promotion offers, such as Percentage Offer, Fixed Offer, Amount Offer (previously, Currency Offer), Formula.
  • Ability to create custom promo codes, generate random promo codes, or upload pre-defined promo codes in the CSV/TXT format file.
  • Ability to reuse promo codes across multiple promotions by using Promo Code List.

Search

This release introduces the same features of Search microservice that were part of the 7.5 release. However, all APIs covering the following functions have been completely revamped as part of this release.

The following functions can be performed via Search APIs as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to search and suggest based on the keyword.
  • Ability to spell check for search and suggestions.
  • Ability to configure weightage for search and suggestions.
  • Ability to configure default suggestions.
  • Ability to configure group suggestions.
  • Ability to redirect URLs for each synonym map, which is locale based.
  • Ability to configure synonym and curation.
  • Ability to configure sort order (product boost based on keyword).
  • Ability to configure for personalized search.
  • Ability to configure typeahead minimum characters.

Shipping

In this release, the Shipping microservice has been newly introduced containing all the Shipping-related features that were part of Cart microservice in the 7.5 release.

The following features have been added to the Shipping microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to add shipping classes.
  • Ability to configure shipping methods with shipping cost calculation (flat rate or percentage) based on the shipping class.
  • Ability to configure shipping zones with the ZIP code-based restrictions.
  • Ability to associate shipping methods to shipping zones.

Tax

In this release, the Tax microservice has been newly introduced containing all the Tax-related features that were part of Cart microservice in the 7.5 release.

The following features have been added to the Tax microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Support for extension points to the third-party tax providers.
  • OOTB support for Cybersource as a tax provider.
  • Ability to support Fallback for default tax rate (in case of the third-party service being down).

 

Revision History
2022-04-13 | SW – Added Release 8.11.1 content.
2022-04-10 | JP – Fixed link and http issues.
2022-01-25 | AN – Added Release 8.11.1 content.
2022-01-04 | JP – Added Release 8.11.0 content.
2021-12-20 | JP – Added Release 8.9.5 content.
2021-03-22 | JP – Added Release 8.9.4 content.
2020-09-11 | JP – Added Release 8.9.3 content.
2020-07-06 | HM – Added Release 8.9.0 content.
2020-06-17 | JP – Added Release 8.8.1 content.
2020-06-05 | JP – Added June 2020 release 8.8.0 content.
2020-05-05 | JP – Added May 2020 bug fixes.
2020-04-08 | JP – Added April 2020 release content.
2020-02-03 | JP – Added February 2020 release content.
2019-10-31 | JP – Added November 2019 release content.
2019-09-26 | JP – Added September 2019 release content.
2019-07-11 | JP – Added July 2019 release content.
2019-05-03 | JP – Content uploaded.