Adobe Commerce AD0-E722 Adobe Study Notes

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.

References:

• Source Selection Algorithm | Adobe Commerce Developer Guide
• Source Selection Interface | Adobe Commerce Developer Guide

The issue here is that the product price changes are not reflected on the storefront, even though the indexes are set to update by schedule and there are no items in the backlog. This indicates that there might be some problem with the changelog and indexing process, which are responsible for tracking and applying the data changes to the index tables. Therefore, the Architect should recommend the developer to check if any custom or third-party modules interfere with the changelog and indexing process, and disable or fix them if needed. Additionally, the Architect should recommend the developer to verify that the version_id for the price indexer in the mview_state table is consistent with the last entry for the same column in the changelog table, and re-synchronize them if they are out of sync. This will ensure that the indexer can process all the data changes correctly and update the index tables accordingly. References: https://experienceleague.adobe.com/docs/commerce- admin/systems/tools/index-management.html?lang=en#cron-groups-and-processes1 https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#m2devgde-mview 2

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.

References: https://experienceleague.adobe.com/docs/commerce-admin/b2b/purchase-orders/account-dashboard-approval-rules.html?lang=en#account-dashboard 1 https://experienceleague.adobe.com/docs/commerce-admin/b2b/purchase-orders/purchase-order-payment-method.html?lang=en#payment-method 2

These two options are both valid ways to manage routing for the bespoke news section and adhere to best practice. Option B leverages the existing URL rewrite functionality of Adobe Commerce, which allows creating custom URLs for any entity type and storing them in the database. This option requires creating a standard controller route for the news entity type, such as news/article/view/id/i, where i is the news article ID. Then, on saving each news article, a rewrite rule is generated that maps the internal URL to the desired SEO-friendly URL, such as news/{date}/{article_url_key}. The rewrite rule is stored in the url_rewrite table, which is used by the standard router to match and redirect requests.

Option C involves creating a custom router class that implements \Magento\Framework\App\RouterInterface and runs before the standard router in the routing process. The custom router class can match the news portion of the URL and extract the date and URL key parts from it. Then, it can look for and load a news articlethat matches those values using a model or repository class. If a match is found, it can set the request parameters accordingly and dispatch the request to a controller action that renders the news article page.

References:

• Routing | Adobe Commerce Developer Guide
• URL Rewrites | Adobe Commerce Developer Guide
• Custom Router | Adobe Commerce Developer Guide