Conditional scheduling rule description
Dataphin conditional scheduling uses AND/OR logic to evaluate conditions based on data timestamps or cross-edge zone parameters, determining whether a scheduled task runs.
Conditional scheduling rule description
Conditional scheduling supports 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
Conditions can be based on data timestamp or cross-edge zone parameters.
Data timestamp judgment types
Data timestamps can be evaluated against a regular calendar or a public calendar.
-
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 that supports parameters such as date type (working day, holiday), tag, and financial periods. Conditions for tags are as follows:
ImportantFinancial 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
Cross-edge zone parameters are evaluated based on value type: text or numeric.
-
Text Type: Allows for conditions Is or Is Not.
-
Numeric Type: Supports numeric comparisons using operators such as =, !=, >, <, >=, <=.
Example description
The following example uses December 6, 2022, with conditions configured using an OR operation:
-
First condition: December 6, 2022 is not a weekend day in the regular calendar, so the first condition evaluates to false.
-
Second condition: December 6, 2022 is marked as a holiday in the public calendar text01, so the second condition evaluates to true.
Because an or operation is used, the overall result is true when any single condition is satisfied. The system then skips execution based on the specified execution schedule type. The following graph shows a preview of the scheduled run plan:
