Just getting started with FIM R2 RC here at the moment – and the first thing I’m excited about is outbound Sync Rule scopes!
When creating an Outbound Sync Rule now you are offered the enticing option to use an “Outbound System Scoping Filter”:
And now, instead of mucking around with Sets and MPRs, I can set a simple rule which says which objects I want this to apply to.
And it works!
The other thing that hasn’t appeared to clutter up my Metaverse is any EREs, though the DREs are still generated.
All up a definite improvement!
That is such good news. I have recently been in the process of translating a bunch of (overly) complex old style sync rules to the new declarative style. This is really very welcome.
Nice find Carole, does that mean that it is no longer necessary to attach the OSR to the user with an MPR and workflow, eliminating the need for EREs?
That’s right – no set, no MPR, no workflow – the triumverate of nuisance is gone! Also no EREs, but you do still get the DREs generated once it sees the object is there. I’d still prefer some kind of stamp on the object itself, but I guess I’ll live with it for now.
I really had no idea this was coming – they kept it quiet, a nice little surprise!
Agreed, this is a very nice little surprise. Eliminating the noise of EREs could significantly improve synchronization performance in large organizations.
Great feature, unfortunately deprovisioning users provisioned in this fashion is not possible, short of coding it out.
What a disappointment. I haven’t actually used SRs in any production environment – far too limited and with stupid limitations like that. Rules extensions continue to rule.