Unused Feature Removal
Introduction
Configure feature-remove.map
to remove features that are no longer in use. This process removes outdated features that could hinder performance or create confusion.
Apply the configurations shown in the Open iT Core Server.
Configuring feature-remove.map
- Windows
- Unix
-
Open
feature-remove.map
in the Configuration directory, which is by default inC:\Program Files\OpeniT\Core\Configuration
.Notice that it contains instructions on how to edit the file.
-
Specify the feature to remove with the following syntax:
Mapping SyntaxMAP: feature_remove
<Product1\feature1 name>
<Product2\feature4 name>
...
<Productn\featuren name>The feature_remove must not be changed.
Empty lines are allowed — any line beginning with
#
as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimizing Rules to Speed Up Rename or Mapping page.In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Feature' and 'feature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: feature_remove
Product112\Feature11*
Product113\Feature11*This example removes all features starting with Feature11 under Product112 and Product113 from data processing.
You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
-
Save the changes.
-
Open
feature-remove.map
in the etc directory, which is by default in/var/opt/openit/etc
.Notice that it contains instructions on how to edit the file.
-
Specify the feature to remove with the following syntax:
Mapping SyntaxMAP: feature_remove
<Product1\feature1 name>
<Product2\feature4 name>
...
<Productn\featuren name>The feature_remove must not be changed.
Empty lines are allowed — any line beginning with
#
as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimizing Rules to Speed Up Rename or Mapping page.In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Feature' and 'feature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
ExampleMAP: feature_remove
Product112\Feature11*
Product113\Feature11*This example removes all features starting with Feature11 under Product112 and Product113 from data processing.
You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
-
Save the changes.
This mapping may affect the following data types:
Next Steps?
Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the historical reports.