Where should you place logic to derive a computed attribute for a synced record type, such as a customer segment?

Where should you place logic to derive a computed attribute for a synced record type, such as a customer segment?

• A. In a custom record field on the record type
• B. In the interface
• C. In the data source
• D. In a separate process

Answer: (A)

When working with a synced record type, derive attributes belong in the record model itself by adding a custom record field on the record type. You can compute its value from existing fields (for example, a customer segment derived from revenue and industry) and expose it as part of the record payload. This makes the derived attribute available across all interfaces, grids, and logic that use the record, and keeps the calculation centralized in Appian rather than tying it to the UI or the data source. Putting the logic in the interface would limit its use to a single UI and require duplicating logic elsewhere. Implementing it in the data source couples business rules to the database and complicates maintenance, while a separate process adds unnecessary complexity and risk of drift.

When working with a synced record type, derive attributes belong in the record model itself by adding a custom record field on the record type. You can compute its value from existing fields (for example, a customer segment derived from revenue and industry) and expose it as part of the record payload. This makes the derived attribute available across all interfaces, grids, and logic that use the record, and keeps the calculation centralized in Appian rather than tying it to the UI or the data source. Putting the logic in the interface would limit its use to a single UI and require duplicating logic elsewhere. Implementing it in the data source couples business rules to the database and complicates maintenance, while a separate process adds unnecessary complexity and risk of drift.