When a related action is initiated from a record, Appian passes contextual data from that record into the designated process model. This data is received as process parameters, which are then stored and accessed within the process instance as process variables. The pv! domain prefix is the correct syntax used in Appian expressions to reference these process variables throughout the process model's lifecycle.

A. ac!

This prefix references activity class parameters, which are variables scoped to a specific node (e.g., a user input task) within a process model, not the overall process variables.

C. rv!

This prefix is used exclusively within the record view's interface definition to reference the record's data (e.g., rv!record). It is not used within the process model itself.

1. Appian Documentation, Process Variables: "Process variables are used to store data that is used by a process. They are referenced using the pv! domain... Process variables are defined in the process model properties." This confirms pv! is the domain for data at the process level.

2. Appian Documentation, Configure a Related Action: In the "Configure the action context" section, the documentation illustrates passing record data (like the identifier) into a process parameter. Once inside the process model, this parameter becomes a process variable, accessible via pv!. For example, a parameter named recordId would be referenced as pv!recordId.

3. Appian Documentation, Expression Language: This page lists the various domain prefixes and their scopes. It explicitly defines pv! for Process Variables, ac! for Activity Class Parameters, and rv! for Record View variables, clarifying their distinct contexts of use.

Each Appian design object serves a distinct purpose in application development. A Record Type is a cornerstone of Appian's Data Fabric, designed to unify and present a holistic view of business data from various enterprise sources. A Process Model graphically defines a business workflow, orchestrating the sequence of human and system tasks. An Interface is used to build the user-facing forms and dashboards that display information and capture user input. Finally, an Expression Rule encapsulates a piece of reusable business logic or calculation, which can be called from other objects to ensure consistency and maintainability.

Create a new data type: This describes the function of a Custom Data Type (CDT), which is a separate design object used to define a specific data structure.

1. Record Type: Appian Documentation, "Record Type Object". This page states, "A record type is a design object that you use to define a holistic view of your business data... Appian Records allows you to unify data from across your enterprise."

2. Process Model: Appian Documentation, "Process Model Object". This source explains, "A process model is the primary tool for defining a business workflow in Appian. It is a graphical representation of your business process..."

3. Interface: Appian Documentation, "Interface Object". The documentation specifies, "Interfaces are the primary way you can show users your applications and data... You'll use interfaces to display information to users and to allow them to enter information in your applications."

4. Expression Rule: Appian Documentation, "Expression Rule Object". This document notes, "Expression rules are used to store a single expression that can then be called from other expressions... This reusability saves development time and improves application maintainability."

5. Custom Data Type (CDT): Appian Documentation, "Custom Data Types (CDTs)". This reference clarifies, "A custom data type (CDT) is a developer-defined data structure. CDTs are used to store a collection of related data in a single variable." This confirms that creating a new data type is the function of a CDT, not the other listed objects.

A user filter is the correct configuration because it meets both requirements. By creating a user filter on the "status" field and setting a default value to "active", the record list will initially display only the active vehicles as desired. Because user filters are interactive, users can then modify or clear the filter selection at any time to view the complete, unfiltered list of all vehicles (both active and inactive), fulfilling the on-demand auditing requirement. This approach provides the necessary default view while maintaining flexibility for the end-user.

A. Visibility on the Status column controls whether the column itself is displayed, not which records (rows) are filtered from the list.

B. A source filter permanently filters the data at the source level. Users cannot change or remove this filter from the interface to see the unfiltered list.

1. Appian Documentation, "Configure Filters on the Record List": This document details the two main types of filters. It states, "User filters allow users to apply filters to the record list on an ad hoc basis." It also specifies that you can "set a default value for a user filter," which directly supports the configuration in option C.

2. Appian Documentation, "Configure Filters on the Record List": In the section describing source filters, the documentation clarifies, "Source filters are applied to the record type source...Users cannot see or change this filter." This confirms why option B is incorrect as it does not allow users to see the unfiltered list.

3. Appian Documentation, "Record List": In the section on configuring the list view grid, the showWhen parameter for columns is described. This parameter controls the visibility of a column, not the filtering of rows, which demonstrates why option A is incorrect.

The "Write to Data Store" smart service is configured to write data to a specific database table, which is represented in Appian as a data store entity. The node requires two primary configurations on its Data tab:

1. The target Data Store Entity must be selected. This tells Appian which table to write to.

2. The data to be written must be provided in the Value to Store input. This input must be a process variable of the corresponding Custom Data Type (CDT), in this case, ACMEvideo.

A. You provide the data as a single variable of the CDT type, not as separate inputs for each individual field of the CDT.

C. This is imprecise. You must specify the specific data store entity (the table), not just the data store (the database connection).

1. Appian Documentation, "Write to Data Store Smart Service": Under the "Data Tab" section, the documentation specifies the configuration. It states that a "Data Store Entity" must be selected from a dropdown list. It also details the "Value to Store" input, which is defined as "The data to be stored... based on the CDT you've mapped to your data store entity." This confirms that both the entity and a CDT-typed input are required.

2. Appian Academy, "Appian Developer" Learning Path, "Data with Appian" Course: The module on "Writing and Deleting Data" demonstrates the configuration of the Write to Data Store smart service. The instructional videos and materials show that the developer first selects the target data store entity and then maps a process variable of the corresponding CDT type to the node's "Value to Store" input.

The primary purpose of an Appian interface object is to create the user interface (UI) through which end users interact with the application. Interfaces are used to build all user-facing components, such as forms for data entry, reports for data visualization, and dashboards for displaying key information. They are the fundamental building blocks for creating an engaging and functional user experience, allowing users to view, input, and manipulate application data.

A. This describes the function of an Integration object, which is used to call external systems and APIs.

C. This is handled by objects like record types, query rules, and data store smart services, not directly by the interface object itself.

1. Appian Documentation, "Interface Object": "Interfaces are the primary way that your users will interact with your applications. Every form, dashboard, and landing page is an interface. You'll design, build, and test all of your interfaces in the interface object." (Appian 23.4, Design Objects > Interface Object)

2. Appian Documentation, "Integration Object": "Integration objects are used to call external systems (web services, APIs) from Appian. Integrations can be used to either retrieve data from other systems or to send data to them." (Appian 23.4, Design Objects > Integration Object)

3. Appian Documentation, "Record Type Object": "The record type is a powerful design object that allows you to connect your business data to your Appian applications... you can easily connect to your enterprise data in a database, Salesforce, or other web service..." (Appian 23.4, Design Objects > Record Type Object)