May be used if legacy behavior is desired for Rosters that are children of custom AlarmDatabase tags.
A Roster that is a child of a custom AlarmDatabase will not report alarms that have a matching area but are in a different AlarmDatabase. This is desirable in most cases, but you have the option to change the behavior so that all will be searched. Note that if you have a large number of custom AlarmDatabases, searching all can cause a significant delay.
When LimitRosterToParentDB is 1 (default) a Roster that is a child of a custom AlarmDatabase will see only alarms in that database. If set to 0, the Roster will report alarms that have a matching area but exist in a different AlarmDatabase.
Section: System
Default: LimitRosterToParentDB = 1
