For Advanced Agents, the administrator could taylor the schedule using the Agent Schedule, based on the Production Environment specific requirement, without having to update the Agent Rule. This also helped when the Administrator would need to force the agent to run at a specific time: one could update the Agent schedule with a new schedule, wait for the change to apply, then, after successful outcome, revert to the previous schedule.
For Job Scheduler, I don't see this option. Is there something that I miss?
For agents - especially those that ran at large time intervals, we used to use the Agent Schedule in order to test in Staging environment that the Agent was running as expected and doing what it had to do, without having to wait for the specific moment it ran. How can we test Job Schedulers from this perspective?
Are there any prospects to provide the same flexibility for Job Schedulers in future versions?
I think the above questions apply to queue processors as well.
***Edited by Moderator Marissa to update Content Type from Discussion to Question; updated Platform Capability tags***
@IoanaTudor I can't tell you anything about future enhancements. But you are right, that option is missing for testing purposes, sadly. But if you want to test whether or not the process triggered by the job scheduler is performing as expected, you can just run the activity with the same parameters as the job scheduler would do. Do keep in mind that you're running the activity with your user (security) context. If that is an issue, then the easiest option for now is to temporarily modify the job scheduler and revert it back to the original settings when done testing.
@Michel Kraaij This is how we are doing the testing, for now - but for UAT, I don't know if playing with the set-up is ok in principle, checking out rules, etc. This is why I originally started this conversation as a discussion, rather than a question.