# Policy for Deprecated Configurations

**URL:** <https://forum.alumio.com/t/policy-for-deprecated-configurations/212>\
**Category:** General\
**Tags:** faq\
**Created:** [October 10, 2022, 1:22pm UTC](https://forum.alumio.com/t/policy-for-deprecated-configurations/212 "2022-10-10T13:22:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alumio\_Bot](https://forum.alumio.com/user_avatar/forum.alumio.com/alumio_bot/32/1824_2.png) [@Alumio\_Bot](https://forum.alumio.com/u/Alumio_Bot)\
**Post date:** [October 10, 2022, 1:22pm UTC](https://forum.alumio.com/t/policy-for-deprecated-configurations/212/1 "2022-10-10T13:22:09Z")

</div>

### **Table of Contents**

- Purpose
- Why the Configurations Become Deprecated
- Examples of Deprecated Configurations and Their Replacements
- The Logic of Value Condition Filter

### **Purpose**

This guide explains the policy of deprecated configurations and how they should be treated.

### **Why the Configurations Become Deprecated**

Prototypes are marked as deprecated when we want to improve or simplify the way those prototypes work but when we cannot do this without breaking backward compatibility. As for now, these deprecated prototypes are not deleted and will be kept with the mark [deprecated].

However, it is intended to automatically set up automatic updates for the configurations of clients to the new versions in the future.

### **Examples of Deprecated Configurations and Their Replacements**

1. _[Deprecated] Filesystem CSV Subscriber_ - has been replaced with _Filesystem: listing subscriber_.
2. _[Deprecated] Filesystem XML Subscriber_ - has been replaced with _Filesystem: file subscriber._
3. _[Deprecated] Json: Decode to object_ - has been replaced with _Serialize/Deserialize JSON._
4. _[Deprecated] Oauth2 authentication_ - has been replaced with _Oauth2 authentication._
5. _[Deprecated] Value condition - has been replaced with Value condition._

### **The Logic of Value Condition Filter**

The logic of the _Value condition_ filter was changed. Let’s say you want to execute a transformer, but only when a field matches a value (e.g. name = foo). The deprecated condition would still execute the transformer when this field is not available in the data. This logic has been changed in the new version so that the transformers are only executed when the field is available and matches the value.