Workspace Date Format vs. Contract Title in Emails

What This Skill Debugs

Customers configure Date Format at workspace and entity level (SettingKey.date_format_config). Some surfaces respect that config; others historically did not. A common pattern:

• Emails (review, signing, notifications that include contract title) show dates in MM-DD-YYYY (or another wrong pattern).
• Activity Log / audit trail shows the correct workspace format (e.g. DD-MMM-YYYY).

That split is a strong signal that the problem is not “email delivery” and not “user misconfigured the workspace,” but how the contract title (or other email context) was built vs. how audits format dates.

Primary historical cause (contract title): {CREATION_DATE} in the contract title template was substituted using a hardcoded strftime("%m-%d-%Y") in BuildContractTitleFromRegexUseCase, so the stored contract name contained the wrong date format. Every email that echoes contract title inherited that baked-in string.

Additional fixes (email body / key pointers / datetime context): Separate changes ensure executed_at and DATE key pointers in email context use GetUniversalConfigUseCase where applicable (see Related PRs).

When to Use / Not Use