Date range with time

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

Resolver – Abstract

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

images/download/attachments/128386993/image2023-1-5_18-12-43-version-1-modificationdate-1676010617764-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 range element, entries or selections for the components: day, month, year, hour, minute, second, millisecond are all possible for the From and To time.

It is also possible to select the time zone applicable for both time points (From and To).

►NOTE◄

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

  • A statically determined point in time can be defined as a 'Date with time' (DateTime) via the Date with time resolver.

Configuration

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

For any change to the From or To time, it is mandatory to ensure that the chronology ('From less than or equal to To') remains guaranteed.

  • If the chronology would be violated by the new value of the changed parameter, the respective other parameter is also assigned this new value, so that 'From equals To' applies.

  • If the other parameter has not yet been assigned a value, it will also be assigned the new value of the changed parameter, so that 'From equals To' applies.

  • The From and To dates can therefore never be 'interlaced'. Figuratively speaking, the two 'boundary dates' of the date range behave like rings on a curtain rod when shifted.

The setting options for From and To regarding date and time correspond to those for Date with time:

The date can be defined in different ways:

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

  2. Clicking on the calendar icon on the far right of the Date/Time element opens the date selection, as shown 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 range for the hour:images/download/attachments/128386993/image2023-1-5_18-17-7-version-1-modificationdate-1676010617753-api-v2.png

Input of '12' for the hour:
images/download/attachments/128386993/image2023-1-5_18-17-46-version-1-modificationdate-1676010617744-api-v2.png

Direct input:
images/download/attachments/128386993/image2023-1-5_18-15-23-version-1-modificationdate-1676010617760-api-v2.png

Date selection:

images/download/attachments/128386993/image2023-1-5_18-16-20-version-1-modificationdate-1676010617756-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 time zone will be lost.

►NOTE◄ Settings for the time zone can be made via the button with the globe icon on the far right. They apply uniformly for From and To.

Example

A Field restriction identifies business objects whose current modification date (lastModified) falls within the time period of a specific night shift (07/04/2021 22:00 – 07/05/2021 06:00).

images/download/attachments/128386993/image2023-1-5_18-20-15-version-1-modificationdate-1676010617738-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 range with time resolver can influence the result. For the specific application, the time zone to which the period of the night shift in question refers should be selected.