*Background:* Customer isn't wanting us to write back data on the same
driver. We created a new view specific to a new driver to send updates
over the subscriber channel.

The customer is wanting everything to basically update the database via
a change log rather than build an association.

My recommendation was one row per user so that the built in associations
would allow for updates and then we just do a status change every time
we make a change, they could write a trigger to send the data or
manipulate the data as needed.

They are pushing back asking that we basically act as a change log,
where no association would be built, everything would basically be a
creation with not matching policy.

*Question:* Any ideas on how difficult this would be to make sure the
association isn't built when the object is created. I believe the
association is handled by the shim. Any thoughts?


--
fp_IDMWORKS
------------------------------------------------------------------------
fp_IDMWORKS's Profile: https://forums.netiq.com/member.php?userid=9869
View this thread: https://forums.netiq.com/showthread.php?t=56740