Adding an activation condition to an intercept flow ?

[Tom Zeller]

Mostly Scott,

Given a deployer (e.g. CANARIE) that wants to conditionally run the attribute-release intercept flow iff an attribute is present, they would need to override the activation condition for the intercept flow (in profile-intercept.xml) using an AND to join their custom activation condition with the default activation condition (in system/conf/profile-intercept-system.xml). 

Quite doable, but, obviously, the default/system activation condition may change, so ideally the AND would refer to the default/system activation condition (rather than being a copy). But I don’t know how to wire that, especially when the parent flow descriptor is abstract.

Hope I’m making sense. I’m looking for the least XML to add a custom activation condition to an intercept flow. Any ideas ?

Thanks !