Improved: logic to run the job successfully on clicking runNow(#147) #153
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issues
Related Issue #147
Short Description and Why It's Useful
This change will allow user to run the service directly without scheduling it in active state
Clicking runNow when the group does not have a scheduler configured(job is not already scheduled) results in an error. Improved support to check whether the scheduler is configured for the group or not, if not then before calling runNow service, scheduling the job as draft to configure the scheduler and then making the runNow request.
Added check to not allow user to select the schedule if the job is not present or job status is draft.
Screenshots of Visual Changes before/after (If There Are Any)
Contribution and Currently Important Rules Acceptance