Until now, in GraphQL, it was not possible to create a query (or mutation) where the user could select the version to execute. Besides that, in case more than one endpoint had the same name but in different applications, you couldn’t select which one to use.

In order to make queries and mutations unique in GraphQL, we have created a new structure using a namespace with the following format:

Path + “_” + “v” + MayorVersion + “_” + MinorVersion ( 0 by default ).

query {

             structuredContents(siteKey: "20117") {

                    items {

                           title

                    }

              }

       }

VS

query {

         headlessDelivery_v2_0 {

                structuredContents(siteKey: "20117") {

                         items {

                                 title

                                    }

                          }

              }

}

Until now, for a translatable object fields, there was no way to get the values in different languages and always returned the default one. With this change, by adding the Accept-Language header, users can get the selected values properly. This change affects to Rest API and GraphQL.

Feature Status Change Use the platform's configurable purchasing rules to dictate which product options need to be purchased together when setting up products with options. You can set which product options must be purchased together and/or which product options cannot be combined together to create a valid product bundle. You can also limit the number of products from a particular group of products that can be purchased together.

Feature Status Change

The ability for a buyer or sales agent to edit a product bundle directly from the mini-cart has now been added. Previously, if a change had to be made the bundle had to be deleted from the cart and added again. This allows for more speedy alterations to be made before proceeding with check out.