Foundations for supporting AI integrations, with alternative text generation during content editing.

The framework will allow for more features to be quickly and cleanly implemented and at the same time allow partners and customers to reuse it for their own purpose.

Gen AI action type that allows to submit any text to AI services for improvements.

It triggers when editable text is selected while editing any editable text, and replaces the selected text with the result.

The date and time attribute type allows you to represent date and time values as part of the product specification in the Product Information Management system.

It's released as an LTS update that you can install on top of your current project to expand the capabilities of your Ibexa DXP, starting with version v4.6.17 and higher.

You can use it to store, for example, manufacturing dates, expiration dates, or event dates, all with specified accuracy.

In the Page Builder block, allow users to search for all campaigns in the Campaign block.

When the user creates/edits a content item including rich text, then a Campaign custom tag will be available in the Editor.

To set up a Custom tag including selected campaign (as iframe embed) the following data must be provided:

• Campaign - drop-down with search to select specific campaign. The list should include campaigns that are planned (future) and in progress (current),

• Size - size of the iframe in this tag as embed

  • Width - in px, %

  • Height - in px, %

Assign and manage segments over REST.

More here: https://doc.ibexa.co/en/latest/api/rest_api/rest_api_reference/rest_api_reference.html#segments

In order to make upgrades easier, Ibexa should provide Rector rulesets for every relevant version.

This package provides a set of Rector rules to allow automatic upgrades between Ibexa DXP versions.

more here: https://github.com/ibexa/rector/tree/4.6?tab=readme-ov-file#ibexa-dxp-rector

Allow to use Ibexa Connect as a handler for any AI action type.

As a Commerce manager, I want to sell non-tangible products e.g. warranties, services.

Virtual products will contain a dedicated checkout workflow without shipping methods and shipping address.

As the user, I want to be able to view, edit/customize and track URLs for each product included in any catalog.

Requirements:

• Every product has its own URLs automatically generated based on a pattern that says which field or fields are used to build the URL.

• Product can have multiple URLs if it is included in many catalogs and exposed to many sites

• separate tab in product details to display all URLs of a single product

Aggregation API is a foundation for business features like facets search, dashboards, and data analytics.

Aggregation API in Product Catalog was introduced in version 4.5.

It will be enhanced with Range aggregation for product stock.

As the Admin, I want to configure VAT rates for specific countries for selected product type in order to decide what is the VAT rate for this type in a specific country.

It includes UI/UX changes to make it more intuitive and visible in product type.

Management of prices over REST. The following methods are planned to be introduced:

• Get price in given currency

• Get price in given currency and customer group

• Get prices list

• Create price for given product

• Update price for given price

• Update custom price

Once an order is created, a shipment is automatically created in the system. The store manager can check the current status and its details, search and filter shipments. Based on configured shipping workflow the user can process each shipment.

Possibility to attach context data to Cart and Cart Entries e.g. coupon code field, extra field for notes.

The goal is to provide integration with payment gateway(s), that enable to use most popular online payment methods e.g. credit card, PayPal, SEPA direct debit

A trigger email is a series of automated emails audience receives depending on certain actions or events they perform (online behavior). Trigger emails are designed to encourage end users to take further action. 

Trigger-based email marketing campaigns fire emails automatically based on specific customer actions known as triggers. These triggers or actions are based on the end-user behavior and provide recommendations following rules and patterns for each type separately.

Support for shipments, shipping methods and shipping methods types.

Add CDP configuration for pushing data about both products and content items to the CDP in a unified way.

Example: category. Independently of how the category is implemented (taxonomy for products and tree for content), we are able to send the same category metadata to the CDP for both content and product, as long as we can come up with a mapping.

Benefit Enrich profiles based on interactions with both products and content. Example: a user has registered for an event about industrial 3d printers, and/or viewed industrial 3d printers on the site and/or downloaded a whitepaper about it.

Manage Corporate Accounts using the Ibexa DXP REST API.

Edit B2B portals from the admin interface using the page builder.

New revamped Order management including:

• order history (back office)

• order status workflow configuration

• payment status

• shipping status

• invoice generation

• permissions to manage orders

• Rest API

The goal is to replace the current payment bundle (not supported anymore) and provide a new solution, that:

• offers compatibility with Symfony

• supports key B2B payment methods popular in our target markets

• is customizable

• ensures extensibility.

The goals of the New revamped Shipping management are:

• allow the user/admin to configure shipping methods and related costs for active countries (regions), cart value, parcel weight, etc.

• enable the buyer to view and select shipping methods and costs in the Checkout step relevant to his/her country

• ensure extensibility for Shipping component

The goal is to improve search capabilities in the Main catalog.

As the user, I want to filter products in the Main catalog by category.

The goal is to introduce Product Aggregation API as a foundation for product facets, dashboards, and stats.

As the backend developer, I want to use:

• Product Type Term Aggregation

• Product Price Range Aggregation

• Product Category Aggregation

• Product Availability Term Aggregation

• Product Attribute Aggregation

As an Editor, I want to configure the page block „Bestsellers” to display a list of top-purchased products.

The Bestseller block will be based on the Personalization engine.

Allow the Editor to configure the product block „Catalog” which displays products from the specific catalog for a selected customer group. You can also set up a default catalog for customers who aren't assigned to any group.

This block enables an Editor to create a curated list of products either by manually entering the product codes or browsing through the product list (Universal Discovery Widget)

As an Editor, I want to use a page block „Recently added” to display products based on the predefined Personalization scenario.

This block utilizes our powerful recommendation engine to suggest products based on a selected scenario.

OTB we have the following scenarios defined:

• Last viewed by the user

• Last viewed by others

This block utilizes our powerful recommendation engine to suggest products based on a selected scenario.

OTB we have the following scenarios defined:

• Last purchased by the user

• Last purchased by others

The configurable checkout enables you to customize the steps in the checkout flow.