Fix #9907 - Workflow - Email action doesn't parse datetime field format and timezone correctly

[SinergiaCRM]

• Closes Workflow - Email action doesn't parse datetime field format and timezone correctly #9907

Description

This PR adds the code to parse date and datetime correctly when sending workflow action emails after modifying a record.

Motivation and Context

With this change the date and datetime fields will be always received in user format and timezone

How To Test This

1. Create a Datetime Field in Contacts module
2. Create an Action that send an email to a modified Contact. Add the Datetime field in the email
3. Create a Contact filling the Datetime field
4. Modify the Contact record to make the Workflow run and receive the email
5. Check that the email has the right datetime value format and timezone

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Final checklist

• My code follows the code style of this project found here.
• My change requires a change to the documentation.
• I have read the How to Contribute guidelines.

[clemente-raposo]

Hi @SinergiaCRM,

Thank you for your PR.

From what I understand this will use the $current_user as the base for getting the date time format.

What will happen if the emails is sent during a cron job? It will probably use db format or system format right?

[johnM2401]

LGTM, Checked each of the Date & Time formats in User Profile, all seemed to send as expected

[SinergiaCRM]

Hi @SinergiaCRM,

Thank you for your PR.

From what I understand this will use the $current_user as the base for getting the date time format.

What will happen if the emails is sent during a cron job? It will probably use db format or system format right?

Hi @clemente-raposo ,

If the emails are sent during cron job I believe the current_user will be used, that could be either the FdT assigned_user or the Scheduler assigned_user.

For us it's working fine til now.