Hello,
We are switching from RSWUWFML2 to Extended Notifications. I have configured everything in SWNCONFIG but noticed that after every change the job(SWN_SELSEN) sends all the Old Notifications again, even though they have been sent before. After the first run, everything's fine and it looks only for the delta.
I want to know how to handle this in Production. I understand from one of the threads that during cut-over, emails can be turned off and then once the first run of SWN_SELSEN is over, delete those emails from SOST and then turn back the emails on for next run onwards. Is that a right approach or there is something else I should be doing?
I don't know why it looks for all the history when I have configured only Delta filter(for only New or changed workitems for specific tasks) with only one Selection Schedule. I have tested this 3 times in Dev. The same happens in Quality also. These are my filter & schedule settings:
Filter ZALL_DELTA:
MAIN_FILTER = BLANK | Cleanup(Delete Old Notifications) = 'X' | Delta = 'X' | Task = total 11 Tasks
Schedule - ZSCHEDULE:
Filter = ZALL_DELTA | Weekdays = all days checked | From 00:00:01 to 23:59:59 | Interval = 15 Mins
I am afraid, if we add more tasks under filter Settings in future and transport, the 1st run will send all the notifications again. That will be a disaster.
Please guide me how to handle this. May be I am doing something wrong?
Thanks.