Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Multiplexer in the shop

Using the Multiplexer workflow event on shop triggers in Exponential - what it matches (sections, classes, excluded user groups, languages), what it can see on each shop trigger, practical uses such as skipping payment…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/e-commerce/checkout/multiplexer-in-the-shop.md

On this page

Multiplexer in the shop

This page is for developers and administrators who want a shop workflow to run only in some cases. The Multiplexer event (ezmultiplexer, kernel/classes/workflowtypes/event/ezmultiplexer/ezmultiplexertype.php) runs another workflow when its conditions match. It was designed for publishing, so on shop triggers it can see less than you might expect. This page says exactly what works.

Contents

  1. What the multiplexer checks
  2. What it sees on shop triggers
  3. Uses that work
  4. How the sub-workflow runs
  5. Limits

What the multiplexer checks

Condition (stored in the event)Matches when
SectionsThe content object's section is in the list, or "Any" is selected
ClassesThe object's class is in the list, or "Any" is selected
User groupsThe user is not in any of the listed groups: this list excludes
LanguagesThe version's initial language is in the selection (all by default)
Version optionFirst version only, all but the first, or all
Workflow to runThe workflow started when everything matches

If all conditions match, the chosen workflow runs as a child process. If not, the multiplexer accepts and the parent workflow continues.

What it sees on shop triggers

The multiplexer looks for an object_id (or node_id) in the process parameters to find a content object:

TriggerParametersObject found?What can be matched
addtobasketobject_id, option_list, quantity, basket_idYes, the productSection, class, excluded user groups
updatebasketitem_count_list, item_id_listNoExcluded user groups only, with sections and classes set to "Any"
confirmorderorder_idNoSame
checkoutorder_idNoSame

Without an object, a section or class condition other than "Any" never matches, so the sub-workflow never runs. On these triggers, set sections and classes to "Any" and use the user group list.

Uses that work

GoalTriggerMultiplexer settingsSub-workflow
Export placed orders to another system, except test orders made by staffcheckout afterSections and classes "Any"; exclude the "Shop staff" groupAn export event of your own
A check only when products of one class are addedaddtobasket beforeClass "Gift card", sections "Any"An event of your own that checks the item
A check only for products in one sectionaddtobasket beforeSection "Restricted", classes "Any"Same

Note

A payment gateway inside a multiplexer's sub-workflow is a different matter: the gateway's payment object belongs to the child process, and the provider's callback continues that process. We did not find this combination documented or tested in the repository. Keep the payment event directly in the checkout workflow, and if you must branch around payment, test the complete path, including the callback, in the provider's test mode.

How the sub-workflow runs

The child process gets the parent's parameters plus its own workflow id. Its result is passed up: a redirect (a payment provider) or a template (gateway selection) is passed to the customer as if the parent had produced it; a deferral to cron makes the parent wait; done means accepted, cancelled and failed mean cancelled and rejected.

Limits

  • One workflow per multiplexer event. For several cases, put several multiplexer events in the parent workflow.
  • The user group list excludes; there is no "only these groups" list.
  • No condition on order total, country or payment method. For those, write an event of your own (Writing a workflow event type).

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x