Introduction

Triggers and Actions are powerful tools within the Mimeeq system that allow you to create dynamic product configurations with conditional logic. This guide will walk you through the basics of setting up and using these features.

What are Triggers and Actions?

Triggers are conditions that, when met, activate one or more actions.
Actions are changes that occur in your configurator when a trigger condition is met.
Together, these create "if-then" rules for your product configurations: "If this happens (trigger), then do this (action)."

Accessing the Rules Section

To begin working with triggers and actions:

Navigate to the Product Admin area
Click on the Rules tab

Creating Rule Containers

Rule containers help you organize your rules for better management:

In the Rules tab, click the Add Container button
Name your container according to its purpose (e.g., "Fabric Dependencies," "Pricing Rules," etc.)

Adding a New Rule

To create a rule within a container:

Select your rule container
Click the Add Rule button
Enter a descriptive name for your rule (e.g., "Velvety Fabric - Metal Legs")

Setting Up Triggers

Every rule needs at least one trigger condition:

Click Add Trigger
Select the trigger type from the dropdown menu

Trigger Types

Mimeeq offers several trigger types:

Always Active: Rule is constantly applied (good for defaults, zoom settings, etc.)
Events: Activated by specific user interactions (e.g., clicking hotspots)
Filter: Based on filter attributes
Option Set: Activated when specific option sets are selected

For detailed information on each trigger type, please refer to our dedicated trigger documentation. (Coming soon)

Example: Option Set Trigger

To create a trigger based on an option set selection:

Select Option Set as the trigger type
Choose the specific option set (e.g., "Fabric")
Select the option value that will activate the trigger (e.g., "Velvety")
Set the Inclusion Type:
Is one of: Trigger activates when the selected option(s) are chosen
Is not one of: Trigger activates when anything EXCEPT the selected option(s) are chosen

Adding Actions

Once you've set up your trigger(s), you need to define what happens when the trigger conditions are met:

Click Add Action
Select the action type
Configure the specific parameters for that action

See our triggers guide for a full list of Triggers (Coming Soon)

Example: Select Parameter Action

To automatically select another parameter when your trigger activates:

Choose Select Parameter as the action type
Select the parameter to modify (e.g., "Leg Type")
Choose the value to be selected (e.g., "Metal")
Click Save

Multiple Triggers and Actions

You can create complex logic by adding multiple triggers and actions to a single rule:

Multiple Triggers: All trigger conditions must be met (they work as AND conditions)
Multiple Actions: All actions will execute when the trigger conditions are met

Testing Your Rules

After creating your rules:

Click the Preview button in the top right corner
Test your configuration by interacting with it
Verify that your triggers and actions work as expected

Example Use Case

In our example:

We created a rule that triggers when the "Velvety" fabric is selected
The action automatically selects "Metal" as the leg type
When testing in preview mode, selecting the Velvety fabric option automatically changes the leg type to Metal

This simple example demonstrates how you can create relationships between different configuration options to enhance your customer's experience or enforce specific product rules.

Best Practices

Give your rules clear, descriptive names
Organize related rules into dedicated containers
Test your rules thoroughly after creation
Consider the user experience when creating automatic selections
Document your rule logic for team reference

Important Rules for Avoiding Trigger Loops

Check for Circular Dependencies: Ensure triggers and actions don't create infinite loops where one rule activates another, which then activates the first rule again.

Watch Out For:

Bidirectional Rules
Avoid creating opposing rules like:
Rule 1: If Fabric = Velvet → Set Legs = Metal
Rule 2: If Legs = Metal → Set Fabric = Velvet

Chain Reactions
Be cautious with cascading rules where:
Rule A triggers Rule B
Rule B triggers Rule C
Rule C might trigger Rule A

Parameter Cross-Dependencies
Monitor rules that modify multiple parameters simultaneously
Verify that parameter changes don't trigger conflicting rules

Further Resources

For more detailed information on specific trigger types and actions, please refer to our dedicated documentation:

Trigger Types Documentation (Coming Soon)
Action Types Documentation (Coming Soon)

Updated on: 16/03/2025