IdStory Identity Manager

As it stands now, tree nodes are provisioned to every system which has a mapping for "Entity type" - "Tree". But the usual use case is to provision only a subset of them to a given system. We need to design a sophisticated system which will handle most of the common scenarios. The ideas we came up with:

1. When an entity is saved but before provisioning is done (before AccAccounts are created) fire an event for each system, that provisioning wants to be performed. The event will contain the entity, target system and also will have the option to cancel the provisioning operation for the given system. Advantage of this approach is, that the logic is performed in the processor and will suffice also for very complicated scenarios but it can't be configured from GUI.
2. Other approach is trough types. For example we create attribute "provisioningType". Then we configure which systems should be provisioned for which values. For example if the value is "Organisation", do provisioning to "System1" and "System2". If the value is "Workposition", do provisioning to "System2". This has the benefit that it can be easily configured by administrators.

The best would be do both of these approaches to be prepared for every situation. Also the first approach can be useful also for other object types than TreeNodes. Let me know your opinions on the subject.