tracker issue : CF-4065543

select a category, or use search below
(searches all categories and all time range)

[ANeff] ER for: cfschedule startdate and starttime default to now for non-chained tasks

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 09/28/2015

Components: Scheduler

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Normal / Unknown

Locale/System: English / Platforms All

Vote Count: 0

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on September 05, 2019 using build 2016.0.01.298513
Interval doesn't make sense for chained tasks. Thus, if interval is specified, then user is creating a non-chained task. In this case, startdate and starttime can both default to now.

Related ticket: 3928030

Currently, when interval is specified, an error is thrown if startdate is specified w/o starttime or if startime is specified w/o startdate. Thus, there is no backward compat issue. Both can default to now.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4065543

External Customer Info:
External Company:  
External Customer Name: Aaron Neff
External Customer Email:



Transferring to Hima
Comment by Uday O.
5702 | December 04, 2015 01:23:08 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). Thanks!!, -Aaron
Comment by Aaron N.
31285 | September 05, 2019 11:36:10 PM GMT