Salesforce Loyalty Management processes transactions from the Transaction Journal object to award points. This can be automated using two primary models: real-time and batch processing.

A Schedule-Triggered Flow is used for the batch processing model, where the flow runs at a predefined schedule (e.g., daily) to process a large volume of unprocessed transaction journals.

The term "Evaluation Flow" refers to the real-time processing model. In this model, a flow is triggered to evaluate a single transaction as soon as it is created (functionally equivalent to a Record-Triggered Flow). This flow evaluates the transaction against the loyalty program rules to accrue points immediately.

B. Autolaunched Flow (No Trigger): This flow type contains the processing logic but lacks an inherent trigger. It must be invoked by another process (like a Record-Triggered Flow or Apex), making it a component of the solution rather than the complete automation pattern itself.

D. Screen Flow: This flow type requires user interaction through a user interface. Automating points accrual from a ticket purchase is a backend process that should not require manual user input.

1. Salesforce Help, Document: Process Transaction Journals with Flows.

Reference: This document explicitly outlines the two primary automation methods. It states, "You can create a flow that is triggered when a transaction journal is created or run a flow on a schedule to process a batch of transaction journals." This directly supports the real-time ("Evaluation Flow") and batch (Schedule-Triggered Flow) models.

2. Salesforce Help, Document: Flow Core Action for Loyalty Management: Process Loyalty Ledger.

Reference: This document describes the invocable action used within the flows. It explains that the Process Loyalty Ledger action "Processes a member's eligible, unprocessed transaction journals and updates the member's points balance." This action is the core engine used by both Schedule-Triggered and real-time evaluation flows.

3. Salesforce Help, Document: Flow Types.

Reference: This documentation defines the different types of flows. It describes a Schedule-Triggered Flow as one that "launches at a specified time and frequency," confirming its use for batch processing. It defines a Screen Flow as requiring a user interface, confirming it is unsuitable for this backend process. It defines an Autolaunched Flow as needing to be invoked by another process, clarifying why it's a component rather than a complete triggering automation in this context.