Skip to main content
Skip table of contents

startTime

Available from version1.24.0
Usage

/startTime <message start time>

Description

This argument specifies the message start time.

The start time can be defined using variables, which can be processed additionally using a modifier.

Evaluating variables

The start time is evaluated as follows:

  1. Replacing the variable values (without calculation)
  2. Generation of a complete start time (date + time)
  3. Apply the calculation in the following order
    1. Calculation from the variable {now}
    2. Calculation from the variable {year}
    3. Calculation from the variable {month}
    4. Calculation from the variable {day}
    5. Calculation from the variable {hour}
    6. Calculation from the variable {minute}

Available variables


Examples

IBI.aws.Admin.exe /startTime "2019-05-08T20:00"
The message starts on 08.05.2019 at 20:00 o'clock.

IBI.aws.Admin.exe /startTime "{now}"
The start time of the message is the current time (the time of the call).

IBI.aws.Admin.exe /startTime "{year}-{month}-{day}T{hour}:{minute}"
The start time of the message is the current time (the time of the call).

IBI.aws.Admin.exe /startTime "{year}-{month}-{day}T{hour}:00"
The start time of the message is the current date at the current full hour (the minutes are fixed at "00", which is why the full hour is always generated for the time)

IBI.aws.Admin.exe /startTime "{year}-{month}-{day}T12:00"
The start time of the message is the current date at 12 o'clock (the hours are fixed at "12", the minutes at "00", which is why 12:00 is always generated for the time)

IBI.aws.Admin.exe /startTime "{year}-{month}-{day}T{hour+12}:{minute}"
The start time of the message is in 12 hours - e.g. if the call is executed on 15.04.2020 at 15:00, the start time is 16.04.2020 at 03:00.

IBI.aws.Admin.exe /startTime "{year}-{month+1}-01T{hour}:{minute}"
The start time of the message is the 1st of the next month at the current time.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.