1H2023,PMU-19328 -Automatically Fix Document Transfer and Change Engine Issues Caused by RBP Refresh

[Izabela_P]

In 2H 2022 a similar feature was released that introduced a daily backend job run by the Check Tool where document transfer and change engine issues that are caused by the RBP refresh failure were automatically fixed every day (PMU-18497).

In 1H2023 we see that this isn't automated anymore unless we enable this setting in Performance Management Feature Settings.

Can you please explain what has changed regarding this feature since 2H2022?

[Luka]

Hi @Izabela_P 

In 2H 2022, this feature was only deployed and enabled on preview environment for all customers and there's no admin switch available for customers to turn this feature on/off.
And for production environment, it was only enabled for early adoption customers during that stage.

In 1H 2023, this feature is enhanced and can be turned on/off by admin user through the admin switch "Automatically Fix Document Transfer and Change Engine Issues" in "Performance Management Feature Setting" admin page and this feature will also be released to production environment for all customers in the coming 1H 2023 production release so customers can decide the best time to turn this feature on production instances.

For those preview instances that have already enabled this feature in 2H 2022, technically after 1H 2023 release this newly added "Automatically Fix Document Transfer and Change Engine Issues" admin switch should be automatically selected, but we found an issue recently that a script was failed to run to select this admin switch for those instances. Engineering team is working on a fix and plan to rerun the script.  Customers can either go to below admin page and enable this feature on Preview again manually or wait for engineering to re-run the script and select this admin switch  in coming days.

Please be noted that for those production customer instances that haven't enabled this feature before 1H 2023, we will still not turn this admin switch on by default because we hope to leave the choice to customers to manage your own best time to turn on this feature in production through following admin setting.

Regards,
Luka