[JonBons]

The API side is in the tacticalrmm PR. This is the form, the table, and the toast.

You can put Jinja expressions on the schedule. Same variables as the template. Empty means always run. Changing the template clears the list so you don't keep predicates that belonged to the old one.

The table shows last status and how many conditions are set. A manual run that skipped used to say it ran and then send you to history. It didn't write a history row. That toast now says it skipped.

This will not work against an unpatched API. /run/ still looks like success if the backend never returns skipped.

How I tested

• Pick a template. The conditions section shows up
• Save with none, Run. Success toast and a history row
• Condition False. Skip toast, Last Status skipped, no history
• Condition True. Success again
• Change the template. Conditions list clears
• {% for %} is rejected on save
• undefined_name errors, it does not skip