Apply data format convention to dateMath transform

Hi all,

IdentityNow uses ISO8601 as default date format on many locations. One can see this in transforms on the dateFormat transform. If one does not specify the outputFormat, the ISO8601 format will be used. If one does not specify the inputFormat, the ISO8601 format will be used. The dateCompare transform expects all data to be in the ISO8601 format for it to work.

It seems odd to me that the dateMath transform is not adhering to this standard. Although it does expect the input to be in the ISO8601 format for it to work, the output oddly uses a different format (yyyy-MM-dd’T’HH:mm). The documentation even mentions this and tells us to always nest this transform in another dateFormat transform as workaround to this break of convention.

I understand that since many tenant are currently using the transform in the way it works now, it would be difficult to fix this break of convention. But could we get another parameter in the dateMath transform, where we can specify the outputFormat directly? Then we do not have to nest our transforms each time we want to use the dateMath transform.

Kind regards,
Angelo

1 Like