Where are activity-based actions typically assigned to templates?

Where are activity-based actions typically assigned to templates?

• A. Template Editor
• B. Menu Browser
• C. E2U master file
• D. Epic Menu

Answer: (A)

Activity-based actions are configured at the template level, so you attach them in the tool that edits and defines how a template behaves. The Template Editor is designed for creating and modifying templates and for assigning the actions that should run in response to activity within a template. It centralizes the behavior tied to a template, making it the correct place to set up those actions. The other options aren’t the right fit: the Menu Browser is for navigating and managing menus, not for linking actions to templates; the E2U master file isn’t about template behavior and isn’t where you bind actions to a template; and the Epic Menu refers to a menu interface rather than a template-action configuration tool.

Activity-based actions are configured at the template level, so you attach them in the tool that edits and defines how a template behaves. The Template Editor is designed for creating and modifying templates and for assigning the actions that should run in response to activity within a template. It centralizes the behavior tied to a template, making it the correct place to set up those actions.

The other options aren’t the right fit: the Menu Browser is for navigating and managing menus, not for linking actions to templates; the E2U master file isn’t about template behavior and isn’t where you bind actions to a template; and the Epic Menu refers to a menu interface rather than a template-action configuration tool.