Extraction activity inheritance

Parent Previous Next

Extraction Activity Inheritance



Description


In addition to the inheritance features described on the previous pages, the Extraction activity can also inherit content from extraction profiles in its parents.

Assuming the following setup, we have a parent and child rule each containing an Extraction activity and 2 different Extraction profiles:



The parent extraction profile contains 2 fields with some values defined.



The child extraction profile contains 2 of its own fields (local fields), but also inherits the 2 fields from the parent (this is the default behavior whenever an extraction profile is used on multiple levels).

The 2 inherited parent fields are marked as Inherited and their properties are disabled. Changing, adding or removing fields on the parent profile will also update the child profiles.


During execution both the inherited and specific fields are extracted, as if these fields were local fields.




Inherited fields are overridden by right click on the field and selecting Override



As a result the field is moved to the bottom of the fields list, enabled and marked as Overridden. The field can now be changed to specific settings and the parent field is ignored.


Inherited fields cannot be removed, but to obtain a similar result the field can be overridden and cleared.




Note

Inherited fields are generated during processing and are not stored in the child profile itself.

This allows that the profile can be used with multiple rules and even have multiple parent extraction profiles.