There is a requirement - If user is having Group1 and Group2, now if user has modified his account and added Group3 and removed Group2 then only the final set of groups must be provisioned to target i.e. Group1 and Group3.As per the ideal behaviour (ISIM v6.0 - Dispatcher v6.x) Group2 and Group3 would be sent with respective value operation codes.

Depending on the type of the target, I wonder why don't you follow the operation value that ISIM is sending?For example: ISIM sends 'delete' operation for Group2, then you call a delete membership process for Group2; in the same attribute, ISIM would also sends 'add' operation for Group3, then you call add membership process for Group3.

Post by yn2000Depending on the type of the target, I wonder why don't you follow the operation value that ISIM is sending?For example: ISIM sends 'delete' operation for Group2, then you call a delete membership process for Group2; in the same attribute, ISIM would also sends 'add' operation for Group3, then you call add membership process for Group3.Rgds. YN.

Yes, that I know but in our requirement we want to send the final set of values of the attribute in account object.

It was happening because of caching so I fixed it, THIS IS RESOLVED NOW.