This is one of those things that should be obvious, but the thought only occurred to me today.

When you are using FormSync to bring over APAR changes, (using a specific FormSync forms database as your source, like we talked about during my presentation) you may find that some third party form objects cause issues. The one that shows up constantly is StdFormPreDisplay, where Lake-Co has inserted a bunch of event handlers. These show up as conflicts, and usually require manual intervention during the FormSync process.

For Doc-Trak specifically, the way to avoid that is to log into the target configuration, open the “Forms Enabling For Refresh” form, filter for the form you are about to FormSync, and uncheck all the Enable boxes. Then run the “Form Refresh Utility” for Doc-Trak and that form, and it will remove all Doc-Trak code from the target form.

Then you can run FormSync, and it won’t trip over any Doc-Trak code. Finally, once you’re done vendorizing and patching, you can just re-enable those forms and run the “Form Refresh Utility” again to put the Doc-Trak code back in.