Ability to have now() as default input for date fields

[RobertJohansson]

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. 

[AustinAverill]

For Web Applications like Exb, Map Viewer, Survey 123, etc. I would think you would want to handle this in configuring your editing forms. Usually if there is a date field that should always be calculated as the current date or current datetime, I would add this to the editing form in my desired application as an invisible field that is auto-calculated using arcade (or whatever method is native to the specific application). You can also use this method to add/subtract a set amount of time from current or even a dynamic amount of time that is defined in another field if you wanted.

[RobertJohansson]

@AustinAverill your suggestion is based on structural input of data, but when the date could be random also, becuase its decided of when we get information and from when its going to be applicated, normal is now() or in near time, but using any calculation in a form would overwrite the user input with a new date.

example: lets say someone reports something that we need to add to the date field, we need to add the report date, but we have been on vacation for 3 weeks and need be able to set the correct report date in the app, then both attribute rules, editor tracking or arcade in forms wont work.