Rules - Actions Overview

Introduction to Actions

Actions are powerful tools that allow you to create dynamic behaviors and interactions within your 3D configurator. They serve as commands that execute specific operations in response to triggers, enabling you to control various aspects of your product visualization and user experience.

Make sure you have read Understanding Triggers and Actions Rules in Mimeeq to understand the principles of the triggers and actions.

What Are Actions?

Actions are predefined operations that can:
Modify the 3D view
Control object visibility
Manage camera positions
Handle animations
Manipulate materials
Change interface elements
Modify parameters and options

How Actions Work

Each action performs a specific task when triggered
Actions can be combined to create complex behaviors
Actions respond to user interactions or system events
Actions execute in a defined sequence when triggered

Core Functions

Visual Control: Show, hide, or modify 3D elements
Camera Management: Control viewpoints and zoom levels
Interface Manipulation: Modify UI elements and parameters
Animation Handling: Control dynamic movements and transitions
Material Management: Change appearances and textures

Action Conditions and Execution Settings

Each action in the Mimeeq 3D configurator can be customized with specific conditions that determine when and how they run. These conditions provide granular control over the behavior of your configurator across different devices and scenarios.

Device Scope

Actions can be targeted to specific device types:

Scope	Description
All Devices	Action will run on all device types (default)
Desktop only	Action will only run when the configurator is viewed on desktop devices
Mobile only	Action will only run when the configurator is viewed on mobile devices
AR only	Action will only run when the configurator is viewed in AR mode

This allows you to create device-specific experiences. For example:
Hide certain meshes in AR view but show them on desktop
Apply different material overrides based on the viewing device
Customize the UI layout for mobile users

Execution Timing

Control when actions are triggered:

Timing	Description
Always	Action will run whenever its trigger conditions are met (This default and most common action condition)
On load	Action will only execute once when the configurator first loads
After load	Action will execute after the initial loading process completes

Example use cases:

On load: Set an initial camera angle, open a specific group in the options panel, or start auto-rotation when the configurator first loads
After load: Execute secondary actions that should happen after initial loading actions, preventing action conflicts
Always: Apply actions continuously whenever trigger conditions are met (standard behavior)

Execution Delay

The Delay time (ms) setting allows you to introduce a time delay (in milliseconds) before an action executes.

Example use cases:
Start an animation 500ms after a configuration change
Create a sequence of actions that happen in order by setting different delays
Allow the scene to stabilize before applying additional changes

Execution Count

The Run number of times setting controls how many times an action can execute.

Example use cases:

* Show an introductory animation or message only once

Limit the number of times a particular effect occurs
Create a finite sequence of automated actions

Action Compatibility

Actions are compatible with different types of triggers:

Trigger Type	Description
Option Change Trigger	Activates when users change configuration options
Event-Based Trigger	Activates based on specific events like button clicks or scene loading

Best Practices for Conditions

Device Targeting: Use device scope to optimize the experience across platforms
Timing Control: Carefully consider when actions should run to create a smooth user experience
Sequential Actions: Use delays to create sequences of actions that build on each other
Testing: Always test your configurator on all target devices and platforms

List of available Actions

Camera & View Control Actions

These actions manage camera positioning, zoom levels, and view rotation to control how users see the product.

Action Name	Description	Option Change Trigger	Event-Based Trigger
Apply camera zoom all	Zooms the camera to fit the product into view	✅	✅
Apply Custom Zoom	Applies a custom camera zoom	✅	✅
Select View	Select/Switch the 2D view (works for 2d Layers)	✅	✅
Set Canvas Ratio	Fixes the canvas rotation to a predefined rotation	✅	❌
Start autorotation	Starts the auto-rotatation of the camera	✅	✅
Stop autorotation	Stops the auto-rotatation of the camera	✅	✅

Scene Management Actions

These actions control the overall scene configuration and animations.

Action Name	Description	Option Change Trigger	Event-Based Trigger
Change Scene	Switches to a different 3D scene	✅	❌
Clear scene	Restarts the canvas (used with advanced Animation Logic such as morph targets)	✅	❌
Show 2D Layers	Shows 2D image layers within the 3D Canvas for "Fusion View"	✅	❌
Play Animation	Plays an animation with multiple controls such as speed, frames, direction and number or times to play	✅	✅

Mesh & Material Control Actions

These actions handle the visibility, position, and material properties of 3D meshes.

Action Name	Description	Option Change Trigger	Event-Based Trigger
Hide meshes	Hide a models mesh / meshes	✅	❌
Hide Meshes Dynamically	Hides Meshes based on naming conventions, useful when there is hundreds or thousands of meshes	✅	❌
Show Meshes	Show a mesh that is hidden by default	✅	❌
Show Meshes Dynamically	Shows Meshes based on naming conventions, useful when there is hundreds or thousands of meshes	✅	❌
Invert meshes	Changes a Meshes rotation, inversion	✅	❌
Snap Meshes		✅	❌
Override Materials	Overrides the material assigned to meshes	✅	❌
Override Material Parameters	Overrides the materials parameters, such as the Albedo colour, glossiness, bump texture	✅	❌
Sync Option Sets	This allows you to set keep always to option sets in sync, so for example if you select leather backrest, you will need a leather seat, but the leather color can be different, it works as a by directional sync so changes can be applied on any of the connected option sets	✅	❌

Option & Parameter Management Actions

These actions control the configuration options and parameters available to users.

Action Name	Description	Option Change Trigger	Event-Based Trigger
Sync Options	Syncs options as long as they share the same option set or option code, essentially allowing you to select the same option in different widgets	✅	❌
Change Block Name	Renames the block	✅	❌
Disable Option Blocks	Disables selection of Option block (Grey's out the selection but does not hide it)	✅	❌
Disable Option Sets	Disables a specific option set (Grey's out the selection but does not hide it)	✅	❌
Disable Options	Disables parameters (Grey's out the selection but does not hide it)	✅	❌
Disable Options by Filter	Disabled parameters based on the option set (Grey's out the selection but does not hide it)	✅	❌
Hide Option Blocks	Hide an entire Option block	✅	❌
Hide Option Sets	Hides a specific option set or sets	✅	❌
Hide Options	Hide specific options from option set	✅	❌
Hide Options by Filter	Hides parameters based on filter attribute	✅	❌
Select Options	Select a specific option set parameter	✅	✅
Show Components Dynamically		✅	❌

UI & Information Display Actions

These actions manage the user interface elements, information displays, and widget properties.

Action Name	Description	Option Change Trigger	Event-Based Trigger
Show Hotspot	Shows a hotspot with content inside such as videos, images, text	✅	❌
Hide Hotspot	Hides the Hotspot from Showing	✅	❌
Hide UI Elements	Hides specific UI elements	✅	❌
Open group	Opens a group on the side panel	❌	✅
Rename Tooltip	Renames a tooltip assigned to hotpsot	✅	❌
Scroll to option	Scrolls to a specific option	❌	✅
Override Widget Settings	Dynamically changes properties of widgets, Engrave/Emboss, Message, Upload Texture	✅	❌

Updated on: 13/04/2025

Was this article helpful?

Thank you!