Private content blocks are sections of the page that are specific to each customer and are not cached

by the server. To update these blocks when a customer performs an action, such as adding a gift

registry item to the quote, the Adobe Commerce Architect needs to specify the new action in a

sections.xml configuration file. This file defines which blocks need to be updated for each action and

how often they should be updated. By doing this, the Architect can ensure that the private content

blocks are refreshed with the latest data from the server. Reference:

Private content | Magento 2 Developer Documentation

Configure private content | Magento 2 Developer Documentation

According to the Adobe Commerce documentation, the Source Selection Interface is the main

interface for implementing custom source selection algorithms. The interface defines a method

called execute(), which takes a list of items to be shipped and a stock ID as parameters, and returns a

SourceSelectionResultInterface object, which contains the recommended sources and quantities for

each item. The Architect can create a new class that implements this interface and provides the logic

for finding the lowest-cost warehouse that is open for each item. The Architect can then register the

new class as an option for the source selection algorithm in the di.xml file of the custom module.

Reference:

Source Selection Algorithm | Adobe Commerce Developer Guide

Source Selection Interface | Adobe Commerce Developer Guide

To create an integration test that executes different logic in different store views, the Architect needs

to do the following steps:

Create one test class that extends \Magento\TestFramework\TestCase\AbstractController or

\Magento\TestFramework\TestCase\AbstractBackendController, depending on the type of controller

being tested1.

Create one test method that uses the @magentoDataFixture annotation to specify the data fixture

file that creates the product2.

Use the \Magento\TestFramework\Store\ExecuteInStoreContext class to execute the fixture and the

tested logic in different store views. This class has a method called executeInStoreContext, which

takes two parameters: the store ID and a callable function. The callable function will be executed in

the context of the given store ID, and then the original store ID will be restored3. For example:

PHPAI-generated code. Review and use carefully. More info on FAQ.

public function testSomeLogic()

{

// Get the product from the fixture

$product = $this->getProduct();

// Get the ExecuteInStoreContext instance from the object manager

$executeInStoreContext

=

$this->_objectManager-

>get(\Magento\TestFramework\Store\ExecuteInStoreContext::class);

// Execute the fixture in store view 3

$executeInStoreContext->executeInStoreContext(3, function () use ($product) {

// Do some operations on the product in store view 3

});

// Execute the tested logic in store view 4

$result = $executeInStoreContext->executeInStoreContext(4, function () use ($product) {

// Call the tested logic on the product in store view 4

return $this->someLogic->execute($product);

});

// Assert that the result is true

$this->assertTrue($result);

}

Reference:

Integration tests | Magento 2 Developer Documentation

Data fixtures | Magento 2 Developer Documentation

Magento\TestFramework\Store\ExecuteInStoreContext | Magento 2 Developer Documentation

According to the Adobe Commerce documentation, the best way to add a custom tax calculation to

all orders is to declare a new total collector in the “etc/sales.xml” file of a custom module. This way,

the

custom

tax

logic

can

be

implemented

in

a

separate

class

that

extends

the

\Magento\Quote\Model\Quote\Address\Total\AbstractTotal class and overrides the collect() and

fetch() methods. The collect() method is responsible for calculating the tax amount and adding it to

the quote address, while the fetch() method is responsible for displaying the tax amount in the cart

and checkout pages. The new total collector can be assigned to any area of the order totals, such as

before or after the subtotal, shipping, or grand total.

Reference:

Customizing order totals

How to add custom fee or discount to order totals in Magento 2

According to the Adobe Commerce documentation, the output of a GraphQL mutation is declared by

specifying the type of the data returned by the mutation. The type can be either a scalar type (such

as String, Int, Boolean, etc.), an object type (such as Cart, Product, Customer, etc.), or a union type

(such as SearchResult, which can be either Product or Category). A union type is used when the

mutation can return more than one possible type of data, depending on the input or the logic of the

mutation. In this case, the mutation can return either a Cart type or a ConfigurableProduct type,

depending on the number of variants of the configurable product. Therefore, the output of the

mutation should be declared as a union type that includes both Cart and ConfigurableProduct types.

Option B is the only option that correctly declares a union type using the pipe symbol (|) to separate

the possible types. Option A and Option C are incorrect because they use brackets ([ ]) and curly

braces ({ }), which are used for declaring list types and input object types, respectively.

Reference:

GraphQL API - Adobe Inc.

Schema language with GraphQL | Adobe Commerce

Using an iframe system for payment integration can help reduce the PCI scope and compliance

burden for the merchant, as the payment data is collected and processed by the payment service

provider (PSP) within the iframe, without touching the merchant’s website or server. This way, the

merchant can leverage the PSP’s PCI certification and avoid storing or transmitting any sensitive

cardholder data on their own system. The iframe also provides a secure barrier between the host

webpage and the loaded page, preventing any access or manipulation of the payment data by

malicious actors. To implement this approach, the merchant needs to embed the PSP’s payment

form in their checkout page using an iframe element, and configure the communication between the

iframe and the host page using JavaScript123.

The issue here is that the Approval Rules tab does not appear in the Company section in the

Customer Account Menu when the Architect logs in using the Company Administrator account. This

is because the Approval Rules feature requires two settings to be enabled: the Purchase Orders

feature and the Purchase Order payment method. The solution is to set ‘Enable Purchase Orders’ in

the B2B Admin to TRUE and make sure that the ‘Purchase Order’ payment method is active. This will

allow the Architect to create and manage Approval Rules for orders.

Reference:

https://experienceleague.adobe.com/docs/commerce-admin/b2b/purchaseorders/account-dashboard-approval-rules.html?lang=en#account-

dashboard1 https://experienceleague.adobe.com/docs/commerce-admin/b2b/purchaseorders/purchase-order-payment-method.html?lang=en#payment-method2

This action is necessary to make the attribute available for content staging and preview. According to

the Adobe Commerce documentation, the catalogstaging_category_update_form.xml file defines

the fields that are displayed in the Scheduled Changes section of the category form. The file extends

the category_form.xml file and adds additional fields that are specific to content staging, such as

start and end dates, campaign name, description, etc. To include a custom category attribute in the

Scheduled

Changes

section,

the

attribute

must

also

be

declared

in

the

catalogstaging_category_update_form.xml

file

with

the

same

configuration

as

in

the

category_form.xml file.

Reference:

Content staging | Adobe Commerce Developer Guide

Create a category attribute | Adobe Commerce Developer Guide

This solution ensures that the data returned by the GraphQL queries is up to date, while also

maintaining performance. By specifying a $cache(cacheidentity: Path\To\identityclass) directive for

each GraphQL query, the relevant brands and associated products will be added as cache tags.

The issue here is that the sales totals in Sales Orders report show £0.00 for the new UK website. This

is because the currency rates for GBP and USD are not configured, so the system cannot convert the

order amounts from GBP to USD. The solution is to configure the currency rates for GBP and USD, so

they are not empty. This will allow the system to calculate the sales totals in USD for the

report. Reference:

https://experienceleague.adobe.com/docs/commerce-admin/stores-sales/sitestore/currency/currency-update.html?lang=en1