In OutSystems, actions are categorized and represented by different icons to denote their purpose and behavior. When you mention that an action is getting an aggregate but has a different category and icon, it is likely a Server Action that includes a built-in aggregate.

Here's a breakdown of the different types of actions :

1. Server Actions:

   • Icon: A cube with a right-pointing arrow.
   • Purpose: These actions are executed on the server side. They can contain aggregates, advanced SQL queries, or other server-side logic.
   • Usage: Typically used for data manipulation, business logic, and complex operations that need to be performed on the server.

2. Client Actions:

   • Icon: A cube with a left-pointing arrow.
   • Purpose: These actions are executed on the client side (browser or mobile app). They are used for operations that do not require server interaction, such as UI logic, local variable manipulation, or simple client-side calculations.
   • Usage: Used for actions that can be handled within the user's device without needing to communicate with the server.

3. Aggregates:

   • Icon: A table with rows.
   • Purpose: Aggregates are used to fetch data from the database using a visual query builder. They are optimized for retrieving and manipulating data in a straightforward manner.
   • Usage: Used within Server Actions, Client Actions, or even directly on screens to fetch data from entities.

Identifying the Different Actions:

• Server Action with Aggregate: If the action you are looking at is categorized as a Server Action and includes an aggregate, it means the aggregate is being used within the server-side logic to fetch or manipulate data before performing further operations.

• Why Different Icon?: The different icon helps developers quickly identify the nature of the action. A Server Action (cube with arrow) indicates it runs on the server, whereas a Client Action (cube with left arrow) indicates it runs on the client.

Example Scenario:

Suppose you have a Server Action named GetEmployeeDetails:

• Icon: Cube with a right-pointing arrow.
• Contains: An aggregate named FetchEmployeeData that retrieves employee details from the Employee entity.
• Purpose: The Server Action GetEmployeeDetails might fetch data using the aggregate and then perform additional logic like filtering, calculations, or transformations before returning the result.

Understanding the Context:

When you see an action with a different icon, consider its context:

• Server Actions: Usually involve database operations, business logic, and interactions that require server processing.
• Client Actions: Involve UI interactions, simple computations, and local data manipulations.
• Aggregates: Used to visually design queries that fetch data from entities.