[Feature-18550] Add interval trigger type for schedules

[liang-wenjie]

Summary

Add INTERVAL as a workflow schedule trigger type.

This allows workflows to run at a fixed interval without requiring a cron expression.

Changes

• Add CRON and INTERVAL trigger types.
• Support second-, minute-, and hour-based intervals.
• Support finite and unlimited repeat counts.
• Support interval preview and missed-fire policies.
• Persist triggerType and interval configuration through the schedule API, service layer, DAO, Quartz, and UI.
• Preserve existing cron schedule behavior.

Validation

• Add interval schedule unit test coverage.
• Add Quartz simple-trigger test coverage.
• Extend scheduler service tests.
• Add API coverage for creating and updating interval schedules.
• Verify that triggerType=INTERVAL is preserved when saving and querying schedules.
• Verify existing cron schedule behavior remains unchanged.
• Build the UI with npm run build:prod.

Closes #18550

[SbloodyS]

Feature like this require e2e test. Please add the api-test or e2e test cases to verify it.

[det101]

triggerType is sent as a top-level request field, but it is omitted from the schedule JSON.

Create/update APIs only accept @RequestParam("schedule") and deserialize that string into ScheduleParam. SchedulerController has no triggerType parameter, so this extra field is dropped. ScheduleParam.triggerType then defaults to CRON.

Preview works because it puts triggerType inside the schedule JSON (getPreviewSchedule). Saving does not, so INTERVAL schedules are validated and persisted as CRON. The interval JSON in crontab is then treated as a cron expression and the save fails, or Quartz registers a cron trigger instead of a simple trigger.

Please include triggerType in the schedule payload here, the same way preview does:

schedule: JSON.stringify({
  startTime: start,
  endTime: end,
  crontab: state.timingForm.crontab,
  timezoneId: state.timingForm.timezoneId,
  missedFirePolicy: state.timingForm.missedFirePolicy,
  triggerType: state.timingForm.triggerType
})

[SbloodyS]

You are using AI to help you do all the work, but you have not review its results. Before that, I won't waste time reviewing.

[liang-wenjie]

I have manually reviewed the AI-assisted changes locally and will push the follow-up fixes shortly.

The follow-up fixes have now been pushed in commit f48a528139565d103d2b64e76af5c2e3f3996632.

The changes include:

• preserving an existing INTERVAL trigger type when triggerType is omitted during update;
• rejecting an explicit null trigger type;
• validating interval expressions by requiring repeat and restricting minute / second to 0-59;
• adding service-layer and Quartz SimpleTrigger regression tests;
• fixing the Spotless formatting issue in SchedulerAPITest.

Local verification passed:

• SchedulerServiceTest: 18 tests, 0 failures, 0 errors;
• QuartzSimpleTriggerBuilderTest: 2 tests, 0 failures, 0 errors.

Please take another look when convenient.

[SbloodyS]

The description of PR is still messy.

[liang-wenjie]

The description of PR is still messy.

Thanks for the feedback.

I have cleaned up the PR description and organized it into Summary, Changes, and Validation sections.

I also manually reviewed the latest changes, including the triggerType persistence fix and the interval schedule API test coverage. The schedule payload now includes triggerType inside the schedule JSON for both create and update requests.

Please take another look when you have time.