Order ID includes a date different from the user's time zone when adding orders

Current Situation

• When adding ad hoc orders from the GUI then the Order ID does not match the JOC Cockpit time zone of the user.
  • The Order ID includes its creation date, for example: #2023-02-09#T94164229701-root
  • The creation date in the Order ID is calculated for UTC. If the user's time zone is different from UTC. For example if the user's time zone is UTC+5 then the date in the Order ID can switch back to the previous day if the current time is before midnight UTC.
• When adding orders from the AddOrder Instruction inside a workflow then the user's time zone is not considered. Instead the workflow's time zone is considered.
• When adding orders from File Order Sources then the user's time zone is not considered. A specified time zone in the File Order Source configuration is considered.

Steps to Reproduce

• For ad hoc orders
  • Switch the user's time zone from the Profile to  UTC+5
  • Assume that the user's current time is 4 hours after midnight.
  • The Order ID will carry the date of the previous day.
• For orders from an AddOrder Instruction
  • Choose a time zone different to UTC.
  • Create a workflow with a PostNotices, AddOrder and ExpectNotices Instruction.
  • The order log shows different days for the date in the Order ID and the time of workflow execution.

Desired Behavior

• The Order ID should reflect the daily plan's time zone.
• When users add ad hoc orders then the date in the Order ID is calculated for the daily plan's time zone.
• The same applies to orders resulting from AddOrder Instructions and File Order Sources: the Order ID carries the date matching the daily plan's time zone.