Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The skills builder user can format the date fields which are captured in various human readable formats at context such as today, tomorrow, and so on, while pushing the data and also while retrieving the data in response.For example, if you are scheduling a meeting through Luma and specify "schedule a meeting tomorrow at a specific time" followed by your email address, your calendar will be marked on the specific date and time even if you don't mention the date as 28/11/2018. But if you don't mention the time, by default, 11:30 IST will be captured. 

Following attributes are available to manage the date format:

  • attribute available in the context: <attribute_idenitifier>_iso_tz
  • attribute available in the context: <attribute_idenitifier>_iso_no_tz

Image Added

Example:

The attribute identifier = date_time

The supported date format is Epoch format (1560576600). The following strings can be used for APIs in the Outbound Mapping section to support:

ISO with time zone: 

        date_time_iso_tz -> ISO 8601 format with timezone (2019-06-15T11:00:00+05:30)

ISO without time zone:
        date_time_iso_no_tz -> ISO 8601 format with timezone (2019-06-15T11:00:00)

Usage in the text response:
"Here is the start date in epoch: @context.date_time and in ISO 8601 format: @context.date_time_iso_tz and iso without timezone format: @context.date_time_iso_no_tz"

Text response replaced with actual values:
"Here is the start date in epoch: 1560576600 and in ISO 8601 format: 2019-06-15T11:00:00+05:30 and iso without timezone format: 2019-06-15T11:00:00"