The HR management team wants to aggregate data to show the number of employees across regions and to be able to drill down into the data. Which three…

 Data Source (A): The first step in building any report is identifying the source of the data.

Understanding where the data comes from is crucial because it affects how the data will be queried,

filtered, and displayed. It also impacts performance, security, and accuracy of the data. Appian

reports can pull data from various sources such as Appian databases, external databases, or even

from integrations with other systems. Documenting this information allows the development team

to connect the report to the correct data source, ensuring that the report reflects accurate and up-to-

date

information.

Reference: Appian Documentation - Data Sources

 Report Type (B): It is essential to define the type of report required. In this scenario, the HR

management team wants an aggregate view with drill-down capabilities. The report type will

determine how the data is visualized, whether it is a pie chart, bar graph, or tabular format. This user

story requirement ensures that the developers design a report that meets the HR team's needs and

expectations

for

viewing

and

interacting

with

the

data.

Reference: Appian Documentation - Creating Reports

 Role-Based Permissions (D): Role-based permissions are critical for ensuring that users see only the

data they are authorized to access. For instance, while an HR executive might have access to all

regions' data, a regional manager might only see data for their specific region. Defining these

permissions upfront is vital for security and compliance. The development team will use this

information to implement the correct access controls in the report, which is crucial for protecting

sensitive

employee

information.

Reference: Appian Documentation - Managing User Permissions