When we create a date field, it would be very usable to be able to have now() as the standard date, its pretty often thats the date and time we want when editing in arcgis pro, experience builder or in web maps, but not uncommingly we need to set another date for date fields, perhaps change the date a couple of days or hours, we havent found any good workarounds, esri people talk about editor tracking wich have another purpose in our organisation. attribute rules sort of works. but not in the visual part of the applications, we still end up with the user being presented with a calender at the date 1899-12-30 (even if attribute rule can correct it to now()). this is ugly and not user friendly wich is frustrating for not often users to change to lets say yesterdays date (when now() shouldnt be applied).
seems this only is an issue when date is needed to be filled in as seen below.
