@sys.date-time entity has P0 bugs

[Divya Mamgai]

Hi,

I'm currently struggling with some intent processing in regards to 
@sys.date-time entity. Mainly for phrases like the following -

1. tomorrow after 5 pm - Only responds with a date object. Typically I would expected to get a date object with time range starting from 5 PM to EOD.

2. tomorrow before 12 pm - Responds with a date object and a time range object which is weird. The time range object has end time set at 12 PM (which is as expected), but the start time is set to the current time. Should be set to start of the day?

I'm not sure if others have faced a similar issue and found some way to patch this behaviour. The first example is severely broken. The second intent I'm currently patching the response manually (if end time is before start time, reset start time to start of the day), but would appreciate if it came as desired directly.

Thanks and regards.

Confidentiality Notice: The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender by replying to this message and deleting it from your computer. Thank you.

[Fabio De Angelis]

Hi,

this kind of issues many times depends on whether they have trained their agent properly, the more training phrases the better.
If you see that Dialogflow does not recognize the system entity-type correctly when providing the training phrases, I suggest to define/correct the entity type type manually.
It is possible by simply clicking on the word/phrase you want to assign to an entity type and then selecting it from the drop down list.

Read carefully entity types documentation to find the ones that fits better to your use case, It seems to me that the best option for your use case could be a combination of @sys-date and @sys-time-period but you can also test different options. 

Regards