6 Replies Latest reply on Mar 5, 2019 11:41 AM by jay borja

    Best Practices on Managing jobs in lower environments

    jay borja

      Currently my team uses the export/import strategy to promote code from lower environments to production environments.


      What this means is that our very specific schedules are defined in the lower environments.

      We are ensuring that jobs don't run in these lower environments using workload policies.

      There are also a series of locks to make sure that outgoing files are not run when the workload policy is disabled, keeps our users from receiving development reports through the production channel.


      What are the best practices in managing these lower environments?

      Should the schedules be removed and only added in the production environments?

      Build a custom calendar that does not run in lower environments?

      Turn off new day and only order jobs as necessary?