Increase options for Business Rules for Changes and Start/End Dates

Ran into this myself today. We are having issues where users submit a change for approval, but the date was left in the past instead of being updated (and not being a latent change). Would be great if we could block this at the business rule level. 

@ammon.nelson You could build in a check to an automator that returns a ticket with a planned start date before the current date/time back to the previous status, but this would be reactive instead of proactive. If you arent sure on the code I can show you an example via PM :)

I’d further add beyond the “Is at least X days away” etc a condition to do a length count on string fields to force minimum length.

Another nice thing would be the ability to only allow someone to select dates on a specific day of the week (Monday, tuesday, etc). This could be done via automator that checks day of week by number and does actions but being proactive is almost always better than being reactive.

Something else that would be good to add to business rules for changes:

We have a regulatory request to have agents validate if they have updated CMDB associations of an associated asset. This question would be required only if the asset associated is of a few specified types, but there is no ability to use the associated asset values as a condition in business rules so adding this as a field would be great.

Another option to add would be requiring an associated ticket.  For our emergency changes, by policy we require an incident to be associated. To ensure this is happening, it’d be nice to have an “associated assets” are not empty. I can do this via automator in parsing the ticket via API but since it’s an emergency change the goal is to be able to move quick to restore service and having the ticket revert to open after the agent sets the status to send approvals could lead to confusion.

If we could do it via toast (validate form on submission) that would be huge.