Which two statements about the a!queryEntity() function are true? (Choose two.)

The a!queryEntity() function is a fundamental component for retrieving data from a data store entity in Appian.

Option C is correct because the entity parameter of this function requires a direct reference to a Data Store Entity object, which must be passed as a constant. This ensures that the query target is statically defined, allowing Appian to perform necessary validations and optimizations.

Option D is correct because the fetchTotalCount parameter, when set to true within the a!pagingInfo() configuration, triggers a second, separate query to count all records matching the filter criteria. Avoiding this extra database call by setting fetchTotalCount to false (which is the default behavior) improves performance, especially for large datasets.

A. Queries executed within an interface context, including a!queryEntity(), are subject to a 30-second timeout to ensure system stability and a responsive user experience.

B. By default (when no pagingInfo is provided), a!queryEntity() attempts to return all matching records up to system-wide limits, not a constrained subset like a specific page of results.

1. Appian Documentation: a!queryEntity() Function:

For Answer C: Under the "Parameters" section for the entity parameter

the documentation states: "The data store entity to query

specified using a constant." This directly confirms that the entity must be a constant.

For Answer B: In the "Usage Considerations" section

it notes: "If paging is not provided

all data is returned." This contradicts the claim that a subset is returned by default.

2. Appian Documentation: a!pagingInfo() Function:

For Answer D: The description for the fetchTotalCount parameter states: "When fetchTotalCount is true

a separate query will be executed to retrieve the total number of entries. This may have a slight performance impact." This supports the conclusion that setting it to false improves performance.

3. Appian Documentation: SAIL Performance:

For Answer A: This page details various system timeouts. Under the "Timeouts" section

it specifies: "For example

expression evaluations in an interface will time out after 30 seconds." This confirms that queries are not unlimited in their execution time.