anchor.diff:  * It is necessary to compile the transformation up front and deploy it to Kafka Connect.
   * Every change needs code recompilation and redeployment, leading to inflexible operations.
   
  +// Type: concept
  +// Title: Example: {prodname} basic filter SMT configuration
  +// ModuleID: example-basic-debezium-filter-smt-configuration
  +[[example-basic-filter-configuration-example]]
  +== Example: Basic configuration
   
  -// Type: concept
  -// ModuleID: example-of-configuring-filter-conditions
  -// Title: Example of configuring filter conditions 
  -== Example
  +You configure the filter transformation in the {prodname} connector's Kafka Connect configuration.
  +In the configuration, you specify the events that you are interested in by defining filter conditions that are based on business rules.
  +As the filter SMT processes the event stream, it evaluates each event against the configured filter conditions.
  +Only events that meet the criteria of the filter conditions are passed to the broker.
   
  -To filter change event records, configure the filter transformation in the Kafka Connect configuration for the {prodname} connector.
  +To configure a {prodname} connector to filter change event records, configure the `Filter` SMT in the Kafka Connect configuration for the {prodname} connector.
   Configuration of the filter SMT requires you to specify a regular expression that defines the filtering criteria. 
   
  -For example, you might add the following configuration in a `.properties` file:name: value
  +For example, you might add the following configuration in your connector configuration.
   
   [source]
   ----
  
positive.code: An expression can invoke arbitrary methods on its variables. 
  Expressions should resolve to a Boolean value that determines how the SMT dispositions the message.
  When the filter condition in an expression evaluates to `true`, the message is retained. 
  Whenthe filter condition evaluates to `false`, the message is removed.
  
  Expressions should not result in any side-effects. That is, they should not modify any variables that they pass.
  
  
negative.code: 
  The way that you express filtering conditions depends on the scripting language that you use.
  
  For example, as shown in {link-prefix}:{link-filtering}#example-basic-debezium-filter-smt-configuration[], when you use `Groovy` as the expression language, 
  the following expression removes all messages, except for update records that have `id` values set to `2`:
  
  [source,groovy]
  