Right now the disabling of report schedules when we refresh lower environments from production is a manual process that we would like to automate. Deleting rather than disabling report schedules would also be fine.
Has anyone successfully automated this?
How exactly do you refresh lower environments from Production? Are you also refreshing the Jaspersoft database as well?
If yes, please note that we do not actually recommend refreshing the Jaspersoft database to lower environments as it can delete any reports you have been developing in Dev, for instance.For On Premise customers with same tenant name on all environments, we recommend using the export feature in Jaspersoft console with a superuser account. This can allow you to export the reports you would like, without bringing the report schedules and jobs ( there is an option to include/ not the report jobs)
Here is an example:
Hope this helps -Nika
Yes, currently we are refreshing the Jaspersoft database also. Thank you for the example, we will try this out during our next refresh.
This was helpful, Laura
Sometimes your lower environments get out of sync with prod when you have an organization take over support and significant development is occurring, and the new organization has few controls. I have seen this and it is the most frustrating situation as you no longer know how each environment is configured. The clean up and impact on development is substantial.
Thank you for sharing this business scenario. If this is something that tends to happen, I'd probably suggest to have a backup of a new clean environment (Jaspersoft database), without any schedules on it, that then can be re-used to restore a clean copy on lower environments.
Then any additional custom developments and reports can be backed up and exported/imported where they're needed.
The important note here would be to take care and not replace the Jaspersoft database if custom reports and views were not backed up, as this may potentially lead to loss of work.