The foundation of Flow information is the time context against which Flow aggregates, calculates and stores data. In order to configure how Flow creates the underlying time period context you need to create Flow Calendars and Shift Patterns.
For example, your reporting day may start at 06:00 in the morning, your reporting week may start on a Monday, and/or your reporting year may start in March.
To cater for the above-mentioned scenario, you need to create a calendar in Flow with that configuration. By default, your Flow instance is created with a calendar named Production.
If you only need one calendar, then modify/configure the default Production calendar by double-clicking on Calendars > Production in the Toolbox.
The general configuration of a calendar consists of:
||Short description of the Calendar.|
||By default Flow will manage a Calendar’s time period creation automatically based on the standard Gregorian calendar system, applying the applicable offsets where required.|
||Used to define the month in which the reporting year will start (e.g. financial year).|
||Used to define the day on which the reporting week will start.|
Default Refresh Offset
The Refresh Offset for a measure is the “delay” or offset from the “Period End” to the time the retrieval of a measure will be performed by the Flow Engines. For example, at the end of an hourly period, Flow will wait 60 seconds by default before querying any data sources for measure values.
Each calendar has a set of default refresh offsets that will be used when a calendar is first linked to a measure when that measure is created. The refresh offset for that measure can be edited independently of the Calendar setting if required.