From 9171cf913bb1346d6e46ba4ee87f64c03ffe19b4 Mon Sep 17 00:00:00 2001 From: Manamohan Samal Date: Tue, 17 Mar 2026 13:56:08 +0530 Subject: [PATCH] Updated the hyperlinks for accept policy and accept expression --- modules/ROOT/pages/batch-filters-and-batch-aggregator.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/batch-filters-and-batch-aggregator.adoc b/modules/ROOT/pages/batch-filters-and-batch-aggregator.adoc index 679c15a9fc..55f2715d7f 100644 --- a/modules/ROOT/pages/batch-filters-and-batch-aggregator.adoc +++ b/modules/ROOT/pages/batch-filters-and-batch-aggregator.adoc @@ -13,8 +13,8 @@ You can apply one or more record filters as attributes to any number of Batch St To filter records, the Batch Step component supports one `acceptExpression` and one `acceptPolicy`. Both are optional, and no other Mule components accept these filters. If you use both filters on the same component, Mule evaluates the filters in the following order: -. Accept Policy: <> -. Accept Expression: <> +. Accept Policy: <> +. Accept Expression: <> [[accept_expression]] A Batch Step component that uses an `acceptExpression` attribute applies a DataWeave expression to each record that reaches the component and accepts a record for processing within the component only if the expression evaluates to `true` for that record. If the record evaluates to `false`, the Batch Step component skips the record, and that record becomes available to the next Batch Step component within the Batch Job component if one exists.