We are in the process of migrating to 4.2 from 4.1, and we are having issues with our migrated Publication schedules. The publication schedules do not use Dynamic Recipients, and are sent directly to users via email. In order for this type of Pub schedule to work, there must be at lease one Enterprise recipient specified. Unfortunately, when our pub schedules were migrated, the Enterprise recipients were left out of the pub schedule configurations, hence they are broken.
Question 1: Has anyone else run into this issue when migrating from 4.1 to 4.2
Question 2: Does anyone have a suggestions for doing a mass remediation of these schedules (we have 2000+)
Richard_YUL (BOB member since 2019-08-21)