Date with time

See also: Date range with time, Relative date with time, Date time field

Resolver – Abstract

Purpose: Defines an absolute time as a static 'Date with time' (DateTime) incl. time zone.


images/download/attachments/128386973/image2023-1-5_16-44-55-version-1-modificationdate-1676010585532-api-v2.png

►IMPORTANT◄ All resolvers for Static values ignore the input value. Within a resolver chain (see Verketteter Wertauflöser) this prevents the processing of all preceding resolvers (if any).

The Date with time resolver defines an absolute, statically defined value for a 'Date with time' (DateTime) in the context of a value configuration.

It appears by default as a suggestion for value configurations from which a DateTime value is expected.

Similar to the Date/Time element, entries or selections are possible for the components day, month, year, hour, minute, second, millisecond as well as for the time zone.

►NOTE◄

  • If the return value is not to be defined absolutely but relative to the system time or another time specification, the Relative date with time resolver is helpful.

  • A statically determined time period (From/To) can be defined as 'Date range with time' (DateRange) via the Date range with time resolver.

Configuration

As long as no configuration has been made for the 'Date with time', 'No value' ($null) is valid as return value.

The Date can be defined in different ways:

  1. The area marked with the text ►DATE◄ in the upper right of the image allows direct entry via the keyboard. Here, all date components (day, month, year) and the separator applicable in the context must be specified

  2. Clicking on the calendar icon on the far right of the Date/Time element opens the date selection, as in the image below right.

  3. If, starting from the initial state ($null), one of the components for the time is changed, the input is automatically combined with the current date (see images below).

Focus input area for the hour:images/download/attachments/128386973/image2023-1-5_16-51-3-version-1-modificationdate-1676010585521-api-v2.png

Input of '12' for the hourimages/download/attachments/128386973/image2023-1-5_16-51-44-version-1-modificationdate-1676010585508-api-v2.png

Direct input::
images/download/attachments/128386973/image2023-1-5_16-46-37-version-1-modificationdate-1676010585528-api-v2.png

Date selection:

images/download/attachments/128386973/image2023-1-5_16-49-46-version-1-modificationdate-1676010585525-api-v2.png


If the input area already shows a date, the displayed text can be edited. If the text is removed completely, the resolver is reset altogether. This also means that any settings made for the time and the time zone will be lost.

►NOTE◄ Settings for the time zone are offered by the second tab of the date selection (not selected in the image) which can be selected by clicking on the clock icon.

Example

A Field restriction identifies user accounts whose creation date (created) falls before a certain key date (01.01.2020).

images/download/attachments/128386973/image2023-1-5_16-53-18-version-1-modificationdate-1676010585497-api-v2.png

►NOTE◄ Since for a date comparison in Lobster Data Platform / Orchestration effectively the 'UTC milliseconds' are always decisive, the selection of the time zone for the time specification in the Date with time resolver can influence the result, provided that user accounts were created for the time near the specified key date.