Which of the following scenarios would require a refresh of an aggregate?

The scenario that requires a refresh of an aggregate involves modifying input parameters. When input parameters for an aggregate are altered, it changes the context in which the aggregate is executed. Aggregates in OutSystems are essentially queries that pull data based on defined criteria, and any change in input parameters will necessitate re-evaluating the aggregate to reflect the new conditions.

For instance, if an input parameter that filters the data set of an aggregate changes, the output of the aggregate must be refreshed to ensure that it returns the correct data based on the updated criteria. This ensures that the application operates with the most accurate and relevant data whenever user interactions or application state changes occur.

In scenarios involving deleting a user session, changing application settings, or creating new user roles, the aggregates may not need to be refreshed immediately, as these actions do not directly alter the data being queried by the aggregate. Instead, they may affect user states or application configuration without necessitating an immediate update to the data retrieval process.