Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Date circumstance rule

Updated on January 14, 2022

A date circumstance rule is a circumstance that is only resolved during a specified range of time.

When a date circumstance is applied, the value of the date property and the specified start and end date determine the time period during which the rule will be active.


  • Date circumstances can only be created for supported rule types. This is controlled by the Allow rules that are valid only for a certain period of time check box on the Class form.
  • You cannot override a final rule with a date circumstance rule.
  • When date circumstance rules are used in a multinode system, be sure to synchronize the internal clocks of all the server nodes in the cluster. Clock differences of less than a few seconds may lead to incorrect application results. Most operating systems offer facilities for such synchronization.
  • Using more than one time-qualified rule

    Your application can include multiple date range circumstances for the same base rule with overlapping (but not identical) date and time intervals. At run-time, rule resolution processing finds all the time-qualified rules with an interval that includes the current date and time. It then selects the best rule to run based on the following tests:

  • Contrasting time-qualified rules and historical processing

    Pega Platform offers two separate features that can cause processing to be dependent on a date or time value. Which of these to apply to best meet an application need depends on the nature of the rules affected and the requirements and environment of the application:

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us