Without knowing any details about tested application, this is my personal opinion:
a) It is not a big deal to add one function call in ten places. Also this might be a good reason to refactor existing code. For example, replace the click over the 'Next' button with the call to, say, proceedNext() function. In this function perform click on the button and check if confirmation window appears. Handle it if it appears;
b) Depending on the type of tested application and notification window: you may consider OnUnexpectedWindow event that will trigger for desktop application if test code tries to interact (click, activate, set focus) with UI element that is blocked by some other window. If this is your case you may just handle this confirmation window within event handler's code.
Regards, /Alex [Community Hero] ____ [Community Heroes] are not employed by SmartBear Software but are just volunteers who have some experience with the tools by SmartBear Software and a desire to help others. Posts made by [Community Heroes] may differ from the official policies of SmartBear Software and should be treated as the own private opinion of their authors and under no circumstances as an official answer from SmartBear Software. The [Community Hero] signature is used with permission by SmartBear Software. https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame ================================