TASK REPORT EXERCISES
Exercise 1: Task Reports
In this exercise you will build a task report that will return all of the tasks for a specific process.
Note: You must have at least one process with active tasks. If have not created any processes
in your system, download the Case Application from Forum and run the data loader to easily
create several active tasks (make sure to replace 16.1 with the current Appian version as
necessary): [Link]
_Installation_Manual.html
Create a new process report and make sure the report includes the following fields: Process
Name, Status, Task Name, Start Time, Task Owner, Task ID, and Overdue.
Once you create the process report, create a paging Grid to display task information. The
paging grid should display all of the fields above except for Task ID (use the task ID to create a
link to the task from the task name).
Step-by-step
1. Create a process report
a. Create a process report in the Appian designer called D203 Process Model
Task Report and select “Task” as the report type and “Tasks by Process Model”
as the context type. Note: If you do not already have a document hierarchy, you
may need to create it before creating your process report.
b. By default, the report should include Name, Status, Process, and Start Time. Add
the additional fields to the process report as well:
i. Task Owner (tp!owner)
ii. Overdue (is_task_overdue())
iii. Task ID (tp!id)
c. Make sure to save the process report when you make those changes.
2. Create two constants to reference the task report and the relevant process model
a. The first constant should reference the process report. Name this constant
D203_PROCESS_REPORT. Hint: Process reports are of data type document.
b. The second constant should reference the process model you would like to
reference for tasks. Call it D203_PROCESS_MODEL.
3. Create a new interface to create the task report and define it as a dashboard.
a. Use a with variable to save the data from the task report, and query the task
report using the a!queryProcessAnalytics() function.
i. Add a reference to the constants for the task report and process model to
the appropriate parameters for the function.
ii. Define the paging info for the grid to use a batch size of 10 inside of a
load variable and add the paging info inside of the query for the process
report.
b. Add a paging grid to display the fields of the report. Hint: the fields are available
based on columns (e.g. c0, c1, c2, etc.) where c0 is usually the first column in the
report.
c. Add the following fields to the paging grid:
i. Task Name - This field should also include a task link to the appropriate
task using a!processTaskLink() and the Task ID
ii. Status - The status displays as an integer by default. To see how to
convert the integer to a text value, see the following link the Task Report
Tutorial:
[Link]
mat_the_Status_Column
iii. Start Date - The date the task was assigned
iv. Owner - The task owner
v. Overdue - True or false whether the task is overdue
4. Stretch Goal: Add a filter based on status of the task.
a. Create a local variable to store the selected status.
b. Add a dropdown menu to the report that will allow a user to select from a list of
statuses.
c. Use the selected status to filter the data using the a!queryProcess Analytics
function. Hint: Consider what happens if the selected status is null. You may
need to include an if statement around the a!queryFilter() to manage this case.