Thanks for taking the time to post, @marca1 

Likely related to this recent question/discussion: https://collaborate.pega.com/question/creating-reusable-date-formats

It would be great if the pyDateTimeFormat property that currently seems to drive this at the moment had a technique for delivery teams to add a Prompt List item that mapped to a Field Value rule where the preferred datetime format can be changed once and take effect everywhere.

For example:

1. Specialize Embed-Control-Mode.pyDateTimeValue into a client ruleset
2. Add a new entry to the Prompt Value list for the specialized property:
   1. Standard value: FieldValue-MyOrgPreferredDateTimeFormat
   2. Prompt value: MyOrg's standard corporate format
3. UI's that want to forever use their organization's "standard format" for date/time will store FieldValue-MyOrgPreferredDateTimeFormat in the rule configuration.
4. At runtime when a format starting with FieldValue-* is found in the rule configuration, Pega should rule-resolve (from the current instance showing this field) the Field Value rule identified in the rest of the format (MyOrgPreferredDateTimeFormat).
5. Whatever format string is implemented in the resolved Field Value rule becomes what is passed to the DateTime APIs to format the date.

This allows the delivery teams to configure UI's to say show this date time according to a particular company standard, without hard-coding the current standard into the rule configuration at design-time. The standard date/time format can:

• Adapt over time: Change one Field Value and all UI's that opted to 'subscribe' to this configuration observe the change
• Adapt based on the situational layer cake: As rule-resolution is responsible for sourcing the the format to apply.