When fData gathers data it can be asked to limit the data groups in the DSD to a list of data groups. fData looks at the DSD and switches off any data group that is not required by the data groups specified or any on which they are dependent. Abandon and Audit Log data groups are never excluded by this process. An option on each data group lets you force the data group to be gathered regardless of this process (but subject to the Execute If setting).
The contexts in which data is gathered are as follows:
The impact of this feature is that you can create large, multi-purpose DSDs and then use them in contexts that only need part of the data without wasting resources.
For example, you could have a DSD that holds all of your Lookup data groups in one place (for easier maintenance). By specifying the appropriate data group in the external input UI settings, only the data group required will be executed, along with any dependencies.
Another example is to have comprehensive DSDs that cover may data gathering requirements for a specific source. In fDocs Designer, this could offer the user a wide ranging list of tags to include in the document, with only the data groups required being executed. This is especially useful if there are common dependencies across data groups, which need only be specified once in this DSD and executed as necessary.
Note that the external inputs for such DSDs need to cover all requirements.