IDN: dateFormat transform doesn't support ISO8601, dateMath output format

Dear IDN Team,

The transform dateFormat ( Date Format | SailPoint Developer Community ) supports only one format from the ISO8601 standard.

ISO8601: This is the date format corresponding to the ISO8601 standard. The exact format is expressed as “yyyy-MM-dd’T’HH:mm:ss.SSSZ”.
[…]
If no inputFormat is provided, the transform assumes that it is in ISO8601 format.

From what I can see, the only supported “ISO8601 format” for dateFormat is
yyyy-MM-dd'T'HH:mm:ss.SSSZ (seconds and exactly 3 digits for subsecond).

Other ISO8601 formats, including yyyy-MM-dd'T'HH:mm:ss.SSSSSZ, yyyy-MM-dd'T'HH:mm:ssZ, yyyy-MM-dd, output of dateMath, are not supported.

The documentation should make it clear that ISO8601 is not actually supported, and only one format is accepted. It makes little sense to link the Wikipedia page if the format is not actually supported.


Regarding https://developer.sailpoint.com/idn/docs/transforms/operations/date-math:

The output format for the DateMath transform is “yyyy-MM-dd’T’HH:mm”

From what I can see this is not always the case. If now or now/s is used, the output has a different format.

"expression": "now"   => 2023-12-15T15:48:26.164474Z
"expression": "now/s" => 2023-12-15T15:30:32Z
"expression": "now/m" => 2023-12-15T15:30Z
"expression": "now/h" => 2023-12-15T15:00Z
"expression": "now/d" => 2023-12-15T00:00Z
"expression": "now/M" => 2023-12-01T00:00Z
"expression": "now/y" => 2023-01-01T00:00Z

It is a pity that the output from one date transform can not be used directly with the other one (or itself).

Best regards,
Andrei