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]

Revision History

2019-04-08 | JP – Added Release 8.2.0 content.