The most efficient and standard Appian design pattern for this requirement is to use a database view. A view creates a virtual table by joining the [appian].[document] and [appian].[caseData] tables. Appian can then use this single view as the data source for the record type. This approach avoids data duplication, ensures data is always current, and centralizes the join logic within the database, which is optimized for such operations. This allows Appian's query engine to efficiently filter, sort, and page the combined data for the record list.

A. Creating a trigger to copy data results in data duplication. This is inefficient, increases storage requirements, and introduces potential data integrity and maintenance complexities.

B. An SSIS package is a batch process that runs on a schedule. This would introduce data latency, meaning the record list would not display real-time information.

D. An Appian record type cannot directly use a stored procedure as its queryable data source. Record types require a table or view that Appian can dynamically query for filtering, sorting, and paging.

1. Appian Documentation

Record Type Object: "The source of a record type can be a process model

a database table or view

or a Salesforce object." This confirms that a view is a valid and intended data source.

Source: Appian 23.4 Documentation

"Objects" -> "Record Type Object".

2. Appian Documentation

Database Schema Best Practices: "Use views to pre-join or de-normalize data. If you have a normalized schema

create views to de-normalize the data for use in Appian... This is the most common and recommended way to create a read-only data source for records and read-only grids."

Source: Appian 23.4 Documentation

"Data" -> "Database Schema Best Practices" -> "Denormalization".