Stop throwing a validation error for rules with past start dates

Forum|Forum|8 years ago
April 24, 2018
9 replies
108 views

This kills me every time:

It truly does not matter that the start date is in the past. If it's in the past, start it the next available time. If it's in the future don't start it until then.

It's absolutely baffling that the rule would need that input. Please change this.

rules

Best answer by srinivas_muthyam

Hi Scotty,

Thank you for the feedback. I'm assuming your image is referring to rule chain scheduling.

We are changing the Rule chain schedule page to behave the same way as the Rule Basic scheduler. This change we are doing to make it consistent for both rules and rule chains.

Today button is also in our consideration and will be available in near future.

scottyAuthor

Contributor ⭐️⭐️⭐️⭐️⭐️

At least give me a "today" button in the calendar input so I don't have to scroll through the two years of months since I had to last touch this rule.

cinco_coates

Contributor ⭐️⭐️⭐️

While I haven't experienced direct pain with this problem, I sit right next to Scotty and have to hear him complain about this. As such, I would very much like for this to be changed, as well.

brad_jennings

Contributor ⭐️⭐️⭐️

This seems like the biggest, easiest win.

dan_ahrens

Expert ⭐️⭐️⭐️

This suggestion makes a ton of sense, Scotty. Either a "today" button, or just default the start date to today's date seem like very reasonable requests.

VP of Customer Success at Forcepoint

manmeet_dosanjh

Helper ⭐️

+1 to this as I have had the same frustrations when scheduling!

srinivas_muthyamAnswer

Helper ⭐️

Hi Scotty,

Thank you for the feedback. I'm assuming your image is referring to rule chain scheduling.

We are changing the Rule chain schedule page to behave the same way as the Rule Basic scheduler. This change we are doing to make it consistent for both rules and rule chains.

Today button is also in our consideration and will be available in near future.