Kickout Exclusions

There are cases where certain dimension may want to be excluded from the kick-out handler.  For example, in the case of an account dimension that is auto built via BPM Connect, and a fact feed that runs subsequent to it, it does not make sense to have the kick-out handler incur the overhead of  checking the account dimension.  Kick-outs are an expensive operation from a performance perspective, so excluding unnecessary dimensions can boost performance, especially on large dimensions and fact tables.

Other dimension that are candidate for exclusion are "data source", "audit trail" or "category" dimensions.  These dimensions are usually hard-coded into the feed, and kick-out processing against these dimensions in many cases is redundant.   Each instance should be analyzed for the appropriate exclusions depending on the scenario.

When  applying exclusions, while this may boost performance, keep in mind, these dimension are in essence not be checked for kick-outs.  If this capability is misapplied, dirty-data may enter into the fact table thus causing the cube processing to fail during.  Use exclusions cautiously.

Exclusions are added in via global settings in the Config Builder and transcend the whole instance of BPM Connect.  Note: you cannot apply exclusions feed by feed, these exclusions will affect all feeds across any given instance.

The following is an example of how the configuration can be set up against a hypothetical account and category dimension:

This capability is available in DBObjects version 3.3.0 and higher, or can be applied via this SQL patch  kick-outs 3.0