To keep the customer segment up to date when using synced record types, which approach is recommended?

To keep the customer segment up to date when using synced record types, which approach is recommended?

• A. Create a separate scheduled job to recompute the segment.
• B. Add a custom record field to the custom record type that evaluates the three given attributes to define the customer segment.
• C. Use a database trigger to update the segment.
• D. Recompute on every page load.

Answer: (B)

When using synced record types, embed the segmentation logic directly in the record type as a derived (computed) field that uses the three attributes to determine the segment. This keeps the segment in sync with the underlying data automatically—any time the attributes are updated through the sync, the derived field recalculates, and the segment is readily available for filters and displays. This approach avoids the inefficiency of recalculating on every page load, the potential lag of a separate scheduled job, and the complexity of external database triggers. It leverages Appian’s data model to derive the segment in real time as part of the record’s data, ensuring consistency with the current attributes.

When using synced record types, embed the segmentation logic directly in the record type as a derived (computed) field that uses the three attributes to determine the segment. This keeps the segment in sync with the underlying data automatically—any time the attributes are updated through the sync, the derived field recalculates, and the segment is readily available for filters and displays.

This approach avoids the inefficiency of recalculating on every page load, the potential lag of a separate scheduled job, and the complexity of external database triggers. It leverages Appian’s data model to derive the segment in real time as part of the record’s data, ensuring consistency with the current attributes.