tracker issue : CF-4183487

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

Require a separate function to differentiate between datetime Object and datetime String.

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): / ext-user (Dattanand M Bhat)

Created: 08/24/2016

Components: Language, DateTime Functions

Versions: 2016

Failure Type: Enhancement Request

Found In Build/Fixed In Build: 299200,300130,300131 /

Priority/Frequency: Normal / Most users will encounter

Locale/System: English / Win XP All

Vote Count: 2

Listed in the version 2016.0.03.300466 Issues Fixed doc 
Problem:  Require a function to differentiate between  datetime Object and datetime String as the current isDate() function returns true for both

Method:

Result:

Expected:

Workaround:

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

Watson Bug ID:	4183487

External Customer Info:
External Company:  
External Customer Name:  
External Customer Email:

Attachments:

Comments:

Hi Dattanand, Instead of an additional function(s), how about enhancing isValid()? Ex: isValid("datetimestring", ..) and isValid("datetimeobject", ..) Just a thought. Thanks!, -Aaron
Comment by External U.
1968 | August 29, 2016 02:01:59 AM GMT
+1 - Additional options for finer-grained validation are good, but I'd look into enhancing isValid() before considering new functions.
Vote by External U.
1971 | August 29, 2016 02:03:22 AM GMT
I agree with Aaron.
Vote by External U.
1972 | August 29, 2016 02:01:01 PM GMT
This is marked as Fixed in this release, but what was the fix? Did you enhance the isDate() function or follow Aaron's suggestion and modify the isValid() function?
Comment by External U.
1969 | October 03, 2016 03:32:48 PM GMT
Never mind. Looking at the release notes, it seems both fixes were implemented.
Comment by External U.
1970 | October 03, 2016 03:35:48 PM GMT
Hi Adobe, This ticket needs re-opened and fixed. Two Issues: 1) The request was for: isValid("datetimeobject", ..), not isValid("datetime_object", ..). For language consistency, underscores aren't used in new parameter/attribute names. Please read the full description of CF-4199894, including the ticket numbers mentioned in that ticket. 2) isValid("datetimeobject", now()) throws "Valid type arguments are: any, array, Boolean, date, numeric, query, string, struct, UUID, GUID, binary, integer, float, eurodate, time, creditcard, email, ssn, telephone, zipcode, url, regex, range , component, and variableName." That list doesn't include "datetimeobject", but should (it also doesn't include the erroneous "datetime_object"). Thanks!, -Aaron
Comment by Aaron N.
27271 | April 02, 2018 10:09:25 PM GMT