Data Modeling & Integration Flashcards

Which source types can a record type use in Appian?

Answer: Database, process, Salesforce, or web service

Record types can be backed by databases, processes, Salesforce, or web services via integrations.

An analyst notices a CDT contains a nested list of addresses. What is a common recommendation for relational data modeling?

Answer: Store addresses in a separate table related by a foreign key

Normalizing one-to-many data into its own table keeps the model flexible and queryable.

What does a!toJson() do?

Answer: Converts an Appian value into a JSON string

a!toJson() serializes Appian values into JSON text, often for integration request bodies.

A Web API needs to return a custom status code and body to the calling system. Which function builds that response?

Answer: a!httpResponse()

a!httpResponse() sets the status code, headers, and body returned by a Web API.

Which approach best supports data security so that users only see Case records for their region?

Answer: Configure record-level security on the record type

Record-level security rules filter which records each user or group can see.

An integration must call an API that requires a different API key per environment (dev, test, prod). What is the best practice?

Answer: Store the credentials in the connected system and configure them per environment via import customization

Connected systems keep credentials secure and import customization files set environment-specific values.

Why might an analyst recommend a synced record type with a sync filter?

Answer: To sync only the subset of rows that the application needs

Source filters limit synced rows, keeping the cache within limits and relevant.