Who is this article for?

All Ideagen Quality Management Admins with email permissions.

Ideagen Quality Management site accessis needed.

Customers may encounter issues with an email sent to users that has a custom date field blank or the environment variable is showing in the email received.

To make troubleshooting this issue easier to learn, this article is split into three sections so that you can either walk through the steps in sequence or you can jump to the section relevant to what you are finding:

1. Issue Experienced
2. Resolution
3. Further Reading

1. Issue Experienced

This section will explain what occurs when the customer is experiencing the issue.

The customer will have noticed users are receiving an email where there should be a custom date field but there is either not one there or the environment variable is showing. We usually find that they have a custom date field with a title that starts with Date or Date_ and have added the date field to a workflow step. They will then add that custom date field to an email action.

2. Resolution 

This section will provide the resolution for the emails not having a date.

1. The defect is in the code at line 2393 of WorkflowInstance.cs. There is a hard coded check that fields named Date or Date_ will give a false positive check to see if it is a transitional date field and therefore doesn't enter the correct side of the if statement.
2. For the email to send to users with the date populated, you will need to go to the custom fields and edit the name of the date field that is in the workflow. 
3. You will then need to update the email action to include the new custom field in place of the old one. 

3. Further Reading

This section will provide important links to further troubleshooting and resources. 

1. Aha Defect