What are the two categories for end-user actions in a Reporting Workbench template?

What are the two categories for end-user actions in a Reporting Workbench template?

• A. Real-time-based or batch-based
• B. Extension-based or activity-based
• C. Distribution-based or view-based
• D. User-based or system-based

Answer: (B)

At its core, end-user actions in a Reporting Workbench template are grouped by how the action is introduced versus how the user interacts with the template. The two categories are extension-based actions and activity-based actions. Extension-based actions are those provided or enabled through added extensions or custom functionality plugged into the template, expanding what the user can do beyond the built-in features. Activity-based actions are the routine operations users perform while working with the template—things like applying filters, sorting and grouping data, drilling into details, exporting results, saving views, and refreshing data. This distinction helps separate actions that come from design-time extensions from those that arise from day-to-day usage. Other options describe different ideas that don’t fit this classification. Real-time-based or batch-based refers to how data is processed, not how end-user actions are categorized. Distribution-based or view-based relates to how results are delivered or displayed. User-based or system-based focuses on who performs actions rather than the nature of the actions themselves.

At its core, end-user actions in a Reporting Workbench template are grouped by how the action is introduced versus how the user interacts with the template. The two categories are extension-based actions and activity-based actions. Extension-based actions are those provided or enabled through added extensions or custom functionality plugged into the template, expanding what the user can do beyond the built-in features. Activity-based actions are the routine operations users perform while working with the template—things like applying filters, sorting and grouping data, drilling into details, exporting results, saving views, and refreshing data. This distinction helps separate actions that come from design-time extensions from those that arise from day-to-day usage.

Other options describe different ideas that don’t fit this classification. Real-time-based or batch-based refers to how data is processed, not how end-user actions are categorized. Distribution-based or view-based relates to how results are delivered or displayed. User-based or system-based focuses on who performs actions rather than the nature of the actions themselves.