Handlers are objects that are responsible for the heavy lifting of objects and processing of business logic. In the B2B architecture, handlers take control right after the REST API receives and initially processes the request. Each handler is part of a larger handler chain that operates on specific objects. When a handler chain is executed, each handler in the chain is executed in a configured order until no more handlers are available in the chain. Below are some existing handler chains that showcase just some of the use cases for handlers.
- GetCartHandler chain - This chain retrieves and returns the cart object for the currently authenticated user or using a specific cart identifier. This chain also includes handlers that retrieve cart-related data, like cart lines, shipping costs, taxes, and available carriers. This chain is executed indirectly throughout the Storefront, including when a user visits the Cart page, navigates to the Checkout Address page, and proceeds to the Review and Pay page.
- GetProductHandler chain - This chain retrieves a product given a product identifier. This chain is executed when a user visits the Product Detail page or searches for a product on the Quick Order page.
Handler chains make it possible to add new handlers and insert new business logic into the chain. You can read further to learn how to add a new handler to a handler chain.
Download this PDF to view documentation on all Epi B2B Commerce handlers and pipelines.
Last updated: Dec 11, 2020