Use case:
We aim to enable the acceptance of multiple date formats within a single composite entity.
Example:
Subentity | Type | Entity Rules | Date Input Example |
---|---|---|---|
Date Format Slashes | Date | { range: { to: today }, preferredDateFormat: mm-dd-yyyy } | 09/01/23 |
Date Format Dashes | Date | { range: { to: today }, preferredDateFormat: yyyy-mm-dd } | 2023-09-01 |
Answer:
-
Within a composite entity, we individually identify and label the entities.
Additionally, the preferred date format comes into play only when ambiguity arises. -
However, employing multiple preferred date formats within a composite entity proves ineffective. For instance, incorporating both MDY and DMY formats introduces further ambiguity. In such scenarios, the system defaults to selecting the entity listed first in the defined patterns of the composite entity
Please Click Here for more information on using Composite Entity.