...
occurrenceDateTime: An activity that takes place once on a specified date and time.
occurrencePeriod: An activity that takes place once in a specified period.
occurrenceTiming: This is for ad-hoc and recurring activities , respectively.
Ad-hoc -with accepted fieldselements: Timing.repeat.count,Timing.repeat.countMax, Timing.repeat.frequency
Recurring event - with accepted fieldselements: Timing.repeat.period, Timing.repeat.periodUnit, Timing.repeat.duration, Timing.repeat.durationUnit,Timing.repeat.dayOfWeek, Timing.repeat.timeOfDay
When an activity is supposed to happen varies also:
...
| Expand |
|---|
| title | 🛈 Expandable section with Timing categories (Week-based and Frequency-based) prior release FUT-I 2024.4 |
|---|
|
Week-based measurement regimesThis type of regime is recommended for any activity that happens at least once pr. week. Examples: Week-based measurement regimes consist of a combination of dayOfWeek, timeOfDay, duration, and frequency: timeOfDay is optional. If it is not specified then the time component of boundPeriod boundsPeriod.start is used instead.
duration is optional. If not specified then the regime expects activities to be performed at a specific time.
frequency is mandatory and specifies the number of times the activity should be performed for each resolved timing.
Frequency-based measurement regimesThis type of regime is recommended for activities that happen less frequently than once per week. It can be used to specify more frequent activities, but it is recommended to use the week-based regimes instead in these cases. Examples: Once every 2 weeks Once every 10 days
Frequency-based measurement regimes consist of: frequency, period, periodUnit, boundsperiod.start, duration. period, periodUnit is mandatory and specifies the period between each resolved timing.
frequency is mandatory and specifies the number of times the activity should be performed for each resolved timing.
Each resolved timing will match the pattern: boundsperiod boundsPeriod.start + n * period * periodUnit There are some pitfalls to be aware of for the frequency-based measurement regime. Especially if the periodUnit is specified in days or hours. The boundsPeriod.start determines the starting point. This can make it complex to calculate the exact resolved timing. Example: “Every 10 days counting from January 1st 2020” Should I do this activity on April 27th 2021? If the periodUnit is specified in days, each resolved timing will fall on different week-days unless the period is a multiple of 7 If the periodUnit is specified in hours, each resolved timing will fall on different times unless the period is a divisor or multiple of 24 If the periodUnit is specified in hours, then timezone and/or summertime may affect the resolved timings.
|
...
...
| Expand |
|---|
| title | 🛈 Expandable section with Timing constraints prior release FUT-I 2024.4 |
|---|
|
Timing constraintsThe following table contains validations for Timing for recurring events: Timing.repeat Element | Validation | Is mandatory |
|---|
boundsPeriod.start
| | 
| boundsPeriod.end
| | | frequency
| | | dayOfWeek
| One or multiple day of weeks are allowed (Monmon|Tuetue|Wedwed|Thuthu|Frifri|Satsat|Sunsun) Can be combined only with period1 D d or no period specified For period greater than 2 Wk wk, dayOfWeek should be left empty and timing.repeat.boundPeriod.start aligned to the specific dayOfWeek If it is not specified, the day of week oftiming.repeat.boundPeriod.startis used instead
| | timeOfDay
| One or multiple timeOfDayare allowed Can be combined with period 1 D d or no period specified, for other types of periods period, timeOfDayshould be left empty and timing.repeat.boundPeriod.start aligned to the specific timeOfDay If no timeOfDayis specified, the time fromtiming.repeat.boundsPeriod.startwill be used by default.
| | duration
| When both are left empty, then the regime expects activities to be performed at a specific time The allowed values for durationUnitare: S s (seconds), MIN min (minutes), H h (hours), D d (days), WK wk (weeks), MO mo (months), and A a (years)
| | durationUnit
| period
| When both are left empty, the the action activity is assumed to occur daily (1 Dd) and is filtered by the specified dayOfWeek, if provided The timing.repeat. periodUnitcan be specified in S s (Seconds), MIN min (minutes), H h (hours), D d (days), WK wk (weeks), MO mo (months), and A a (years) If timeOfDaypresent, period and periodUnit can be left empty or set to 1 Dd If dayOfWeekpresent, periodand periodUnitcan be left empty or set to 1 Dd
| | periodUnit
| |
|
...
| Expand |
|---|
| title | 🛈 Expandable section with Timing constraints after release FUT-I 2024.4, as a consequence of CCR0212: Ensure that timing expressions that can be created in KAM are supported |
|---|
|
Timing constraintsThe following table contains validations for Timing for recurring events: Timing.repeat Element | Validation | Is mandatory |
|---|
boundsPeriod.start
| | | boundsPeriod.end
| | | frequency
| | | dayOfWeek
| One or multiple day of weeks are allowed (mon|tue|wed|thu|fri|sat|sun) If multiple days of the week are specified, it is recommended that theboundsPeriod.start occurs on a day and time earlier than all the provided dayOfWeekand timeOfDayvalues. Otherwise, the calculated timings may end up in different weeks in some cases (depending on the period, such as every 2 weeks). Can be combined with period such as 1 d, n wk (where n is a positive integer ) or no period specified If it is not specified, then the day of week ofboundPeriod.startis used instead
| | timeOfDay
| One or multiple timeOfDayare allowed If multiple times of day are provided, it is recommended that the time part of boundsPeriod.startoccurs earlier than all the specified timeOfDayvalues. Otherwise, the resolved timings may fall on different days in certain cases (depending on the period, such as every 2 days). Can be combined with period such as 1 d, n wk, n mo, n a (where n is a positive integer) or no period specified If no timeOfDay is specified, the time fromboundsPeriod.startwill be used by default.
| | duration
| If present, durationmust be a positive integer When both are left empty, then the regime expects activities to be performed at a specific time Both should be set, or neither should be The allowed values for durationUnitare: s (seconds), min (minutes), h (hours), d (days), wk (weeks), mo (months), and a (years)
| | durationUnit
| period
| If present, period must be a positive integer integer Both should be set, or neither should be When both are left empty, the action is assumed to occur daily (1 d) and is filtered by the specified dayOfWeek, if provided The periodUnitcannot be specified in seconds; the allowed values are: min (minutes), h (hours), d (days), wk (weeks), mo (months), and a (years) If timeOfDayispresent, periodand periodUnitcan be left empty or set to n d, n wk, n mo, n a (where n is a positive integer) If dayOfWeek ispresent, periodand periodUnit can be: left empty or set to 1 d or n wk (where n is a positive integer)
| | periodUnit
| |
Unresolved timingsThe Infrastructure will not resolve Timing for recurring events containing the following elements: |
...
In a given time period, this recurring regime will result in several resolved timings. For example, looking at April 2021 this will result in four resolved timings
...
| Expand |
|---|
| title | 🛈 Expandable section with resolved timings for Timing having timeOfDay, dayOfWeek, boundsPeriod.end and period 2 W, introduced after release FUT-I 2024.4, as a consequence of CCR0212: Ensure that timing expressions that can be created in KAM are supported |
|---|
|
“Once every Monday between 10-12 starting April 1st 2021, ending on May 6th 2021” can be expressed with the following values in a Timing structure in occurenceTiming: repeat.boundsPeriod.start: 1 April 2021, 08:30:00 CET (Thursday)
repeat.boundsPeriod.end: 6 May 2021, 08:30:00 CET
repeat.duration: 2
repeat.durationUnit: h
repeat.frequency: 1
repeat.dayOfWeek: mon
repeat.timeOfDay: 10:00:00
repeat.period: 2
repeat.periodUnit: Wk wk
The first resolved timing is not in the current week (March 29th - April 4th) because March 29th occurs before boundsPeriod.start. Therefore, the next Monday falls within boundsPeriod.  |
| Expand |
|---|
| title | 🛈 Expandable section with resolved timings for Timing having multiple day of weeks, introduced after release FUT-I 2024.4, as a consequence of CCR0212: Ensure that timing expressions that can be created in KAM are supported |
|---|
|
“Once every Monday and Thursday between 10-12 starting April 5th 2021, until April 25th 2021” can be expressed with the following values in a Timing structure in occurenceTiming: repeat.boundsPeriod.start: 5 April 2021, 18:00:00 CET (Monday)
repeat.boundsPeriod.end: 25 April 2021, 11:00:00 CET (Sunday)
repeat.duration: 2
repeat.durationUnit: h
repeat.frequency: 1
repeat.dayOfWeek: mon, thu
repeat.timeOfDay: 10:00:00
repeat.period: 1
repeat.periodUnit: D d
If multiple days of the week are specified, the first resolved timing will occur on any day from those specified that falls within or overlaps with the boundsPeriod. In this case, the first resolved timing is on a Thursday and not on a Monday.  |
| Expand |
|---|
| title | 🛈 Expandable section with overlapping resolved timing, introduced after release FUT-I 2024.4, as a consequence of CCR0212: Ensure that timing expressions that can be created in KAM are supported |
|---|
|
Overlapping resolved timingsTiming occurrences that overlap with the boundsPeriod, such as those starting before boundsPeriod.start and ending within the boundsPeriod, or starting within the boundsPeriod, but ending after boundsPeriod.end, are included after being adjusted to fit within the boundsPeriod. For example: “Once every Monday between 10-12 starting April 5th 2021, until April 26th 2021” can be expressed with the following values in a Timing structure in occurenceTiming: repeat.boundsPeriod.start: 5 April 2021, 11:00:00 CET
repeat.boundsPeriod.end: 26 April 2021, 11:00:00 CET
repeat.duration:2
repeat.durationUnit:h
repeat.frequency:1
repeat.dayOfWeek:mon
repeat.timeOfDay:10:00:00
Resolved timings are: Monday 5 April, 2021 11:00 (adjusted toTiming.repeat.boundsPeriod.start) – Monday 5 April, 2021 12:00 CEST
Monday 12 April, 2021 10:00 – Monday 12 April, 2021 12:00 CEST
Monday 19 April, 2021 10:00 – Monday 19 April, 2021 12:00 CEST
Monday 26 April, 2021 10:00 – Monday 26 April 2021 11:00 CEST (adjusted to Timing.repeat.boundsPeriod.end) 
|
...