Conditional scheduling rule description

This topic outlines the rules for conditional scheduling supported by Dataphin.

Dataphin's conditional scheduling allows for both AND and OR logical operations:

AND: Evaluates to true only if all conditions are met.
OR: Evaluates to true if at least one condition is met.

Conditional judgment types

Dataphin supports conditional judgments based on data timestamp and cross-edge zone parameters.

Data timestamp judgment types

Data timestamp can be evaluated using either the regular calendar or the public calendar properties.

Regular calendar: Corresponds to the Gregorian calendar and supports parameters such as date, month, and week. Conditions for these parameters include belongs to and does not belong to.
Public calendar: A custom calendar in Dataphin, accommodating parameters like date type (working day, holiday), tag, and financial periods. Conditions for tags are as follows:
Important
Financial periods are supported only when the public calendar is based on a financial calendar template.
- Date type: Includes working days and holidays.
- Tag: Criteria include all, contains any, and does not contain.
- Financial periods: Judged by whether they belong to or do not belong to a given period.

Cross-edge zone parameter judgment types

Judgments for cross-edge zone parameters are based on the type of value, including text and numeric types.

Text Type: Allows for conditions Is or Is Not.
Numeric Type: Supports numeric comparisons using operators such as =, !=, >, <, >=, <=.

Example description

Consider December 6, 2022, as an example, where conditions are configured with an OR operation:

First condition: December 6, 2022, is not a weekend day according to the regular calendar, rendering the first condition false.
Second condition: December 6, 2022, is marked as a holiday in the public calendar text01, making the second condition true.

The presence of or operations means that if any single condition is satisfied, the overall result is true, fulfilling the condition schedule. Consequently, the system will proceed to skip execution according to the specified execution schedule type. Below is a graph illustrating the preview of the scheduled run plan: