When users are in the FME UI, changing the targeting rules for a flag to check against a DateTime attribute, the UI includes a date selector out of convenience. When, however, going to set that date, there's no indication of what time zone the matcher is being set against.

After experimentation, a team could figure out that it's UTC, but having that information up front would be better. An even better version of this feature would be a side-by-side comparison between the time being set in UTC and the time being set local time (in context to the author of the change).

i.e. I want my feature to be "on" when my attribute "CurrentDateTime" is > 05-12-2026 02:00:00 AM (local, eastern) and so ideally we'd see all the context:

05-12-2026 07:00:00 AM (UTC)

05-12-2026 02:00:00 AM (EST) (local to the author in this case)