You need to add a new attribute to your database-backed synced Acme employee record. What should you do?

The standard, low-code procedure for adding a new attribute to a database-backed synced record type is performed directly within the record type's data model. By adding a new source field and ensuring the "Update Table" checkbox is selected when saving, you instruct Appian to automatically apply the necessary schema change (i.e., add the new column) to the underlying database table. This maintains synchronization between the Appian record definition and the database source without manual intervention in the database itself.

A. This manual, two-step process is not the standard Appian workflow. The record type designer is designed to manage and apply schema changes directly to the database.

C. Adding a relationship is used to define connections between different record types (e.g., Employee to Department), not for adding a new attribute to the current record's source.

---

1. Appian Documentation, "Modifying a Database-Backed Record Type": This document explicitly details the process for schema management from within the Appian Designer. It states, "When you add, remove, or update a source field in a synced record type, you can also choose to have Appian automatically update your database table... To apply the schema changes to your database table, select the Update Table checkbox." This directly supports option B.

Source: Appian 23.4 Documentation, "Record Types," "Database-Backed Record Types," "Modifying a Database-Backed Record Type."

2. Appian Documentation, "Record Type Relationships": This page clarifies the purpose of relationships, explaining they are used to "connect related data from different record types." This confirms that adding a relationship is not the correct action for adding a new field to the existing record, invalidating option C.

Source: Appian 23.4 Documentation, "Record Types," "Record Type Relationships."