The current “Created Date” for forms is set when the draft is initially created.
However, this does not reflect the actual point in time when the form becomes part of a workflow (i.e. when it leaves draft state and is submitted).
In practice, the relevant timestamp is when the form enters the workflow, not when the draft was first created. A draft may exist for a long time before submission, making the “Created Date” misleading for tracking, reporting, and documentation.
Because of this, we are forced to implement workarounds (e.g. custom DatePicker fields triggered on status change from Draft → Active).
Introduce a system-generated field such as:
Submitted Date / Workflow Start Date
Alternatively:
Provide both timestamps:
Draft creation date
Workflow start/submission date
This would:
Improve traceability and auditability
Align timestamps with actual workflow events
Remove the need for custom workaround fields
Improve consistency across projects
Hello,

You can then select the Property assigned to the "Submitted Date" in my case "Submission Date" and set it to be populated with a specific number of days (or 0 days) after the form is transitioned.
I think you can get this by using existing features available in the system!
You would like a date field called something like "Submitted Date", that populates when the form is set to a specific status.
In the Workflow, if you would like the field to be set when the form leaves Draft status, you can set the Initialization Settings> Select the Transition button to edit it.
Hope this helps!
Note: I understand that “Draft” may no longer be a visible workflow state in newer configurations, and that the workflow effectively starts at the first active state (e.g. Open).
However, the issue remains the same: the system “Created Date” still reflects the initial form creation (draft stage), not when the form becomes an active workflow item.
This continues to create a gap between creation and actual workflow start, which impacts traceability and reporting.``