OK, I had actually thought of that and did not want to beat up performance, so was looking for a way around it. However it appears that WM has actually thought of this and here is how to do it:
Create your own Trigger, Sequence, and Buffer Table, similar to what gets created by a regular Update Notification. Include both the OLD and NEW key fields in the buffer and trigger.
Create a BASIC notification on your buffer table, and make sure that the delete rows box is checked. Create the rest of your flow, publish, subscribe as you normally would. In the Subscribe Adapter use the OLD key columns in the Where Tab and the NEW key and dimension columns in the Update Tab.
#Integration-Server-and-ESB#webMethods#Flow-and-Java-services