The current known limitations of triggers and actions are the following:
-
Composer does not verify the existence of the remote experiences, scenes or assets referenced by a user creating remote actions. As a result, spelling errors in the names of those remote experiences, scenes and assets will not be recognized or flagged.
-
Timers cannot be dynamically created at runtime.
-
Timers cannot be interrupted except when leaving the scene in which they have been defined.
-
Timers will only start when the associated asset is or becomes visible. Hidden assets will not fire timer triggers associated on them.
-
An Inactivity Timer starts when its associated asset or scene is first displayed and is restarted whenever a user touches that asset or scene. No other action restarts the Inactivity Timer.
-
Neither triggers nor actions are available for images or videos in the background of a scene.
-
In a carousel, asset flow, or asset grid, it is not yet possible to hide (or show) a contained asset using an action.
-
Triggers are raised only when assets/scenes are completely loaded.
-
The "Rewound" trigger is not raised by a looping video when it returns to the beginning.
-
Gestures and Visual Tags currently apply to scenes only, not assets.
-
When contradictory actions are applied to an asset by a trigger, the asset may enter an erroneous state.
-
The "Open URL" action requires the entered URL to be preceded by http:// or https://.
Comments
0 comments
Article is closed for comments.