The rewards catalog uses the configuration CONF_ENABLE_ORG_TIMEZONE to control timezone behaviour. This ensures that all time-based evaluations in the module are calculated using the organisation’s timezone.

Enabling the configuration

By default, this configuration is disabled. To enable it, create a JIRA ticket for the Capillary Product Support team. Impact of enabling The following table shows the behavior when the flag is enabled and disabled :

Impact of enabling

The following table shows the behavior when the flag is enabled and disabled :

Scenario	Default behaviour (disabled)	Behaviour when enabled
Time calculation	Uses the server’s timezone for all time-based reward calculations.	Uses the organisation’s timezone for all time-based reward calculations.
Reward start/end	Reward times may not match the intended local time because they are converted to the server’s timezone.	Reward times follow the organisation’s timezone, so the start and end of the reward happen exactly as configured.
Daily limit reset (fixed window rewards)	Resets at midnight in the server’s timezone, which may not align with the organisation’s day.	Resets at midnight (00:00) in the organisation’s timezone.
Weekly/monthly limit	Windows start based on the server’s calendar.	Windows start at midnight on the first day of the period in the organisation’s timezone.

Notes:

Daylight Saving Time (DST): All time-based evaluations will adjust according to the organization's local time to ensure continuity.

Historical Data: This feature does not retroactively modify historical data. It applies only to reward evaluations and transactions processed after the configuration is enabled.

Data Migration: During data migration, the validity periods of the historical rewards will be interpreted based on the organization's timezone.