Create a derived indicator

Prerequisites

You have created business entities and business qualifiers. For more information, see Create and manage business entities and Create a business qualifier.

Procedure

1. On the Dataphin homepage, choose R&D > Data Development from the top menu bar.

2. From the top menu bar, select a Project (in Dev-Prod mode, you must also select an Environment).

3. In the left-side navigation pane, choose Standard Modeling > Indicators. In the indicator list on the right, click the icon.

4. In the Create Derived Indicator wizard, in the Define Derived Indicator step, configure the following parameters.

   Parameter		Description
   business definition		Enter a natural-language description of the indicator's business logic for business users. For example: The number of unique male customers who made a purchase at each store in the last day: This counts the number of male customers who completed at least one transaction in each store within the last day. Unfinished and canceled orders are excluded, and repeated purchases by the same customer in the same store are deduplicated. The business definition can contain up to 1,000 characters.
   Indicator Definition	statistical period	Select the statistical period for the derived indicator. The statistical period defines the time range of the source data used for calculation. You can select up to three statistical periods.
   	atomic indicator	Select the atomic indicator. Only atomic indicators with the same data timeliness are available.
   	business qualifier	Select the business qualifier. Only business qualifiers with the same data timeliness as the selected atomic indicator are available.
   Statistical Granularity Settings	statistical granularity	The timeliness of the statistical granularity is automatically determined by the selected statistical period. You only need to select the object granularity. You can add up to three object granularities.

5. Click Next.

6. In the Pre-generate Derived Indicators step, confirm the derived indicators to be generated and click Next.

   Parameter	Description
   Indicator English Name	The system automatically generates an English name in the format: {atomic_indicator_english_name}_{statistical_period_abbreviation}_{business_qualifier_english_name}. You can edit this name. The naming conventions are as follows: Must contain only letters, digits, and underscores (_), and must start with a letter. The maximum length is 100 characters. The English name must be unique within the indicator summary table.
   Indicator Name	The system generates this name automatically, but you can customize it.

7. In the Complete Indicator Information step, configure the parameters.

   Parameter	Description
   O&M engineer	Select the O&M engineer for the derived indicator. Click Set O&M Engineer to update the O&M engineer for all derived indicators in bulk.
   business owner	Select the business owner for the derived indicator. Click Set Business Owner to update the business owner for all derived indicators in bulk.
   scheduling settings	Click to configure scheduling settings for the derived indicator. The supported settings and their parameters are as follows: Scheduling Type: Derived indicators support only Normal Scheduling. Effective Date: Derived indicators do not support an effective date. Scheduling Cycle: Automatically set based on the statistical period. Supported values include Year, Month, Week, Day, Hour, and Minute. Year, Month, and Week are for compatibility purposes and cannot be selected directly. To schedule tasks by year, month, or week, use conditional scheduling. Note A derived indicator's statistical period is a financial period, and you cannot change the scheduling cycle by modifying it. Scheduling Run Plan: Click Preview to view the scheduling plan. The plan displays all scheduled instances for each day of a given month, along with their scheduling types. You can preview by business date or execution date (scheduling date). If a day includes multiple scheduling types, the calendar displays corresponding colors and instance counts for each type. For example, the following figure shows that on the 4th of a month, the task has 44 normally scheduled instances, 2 suspended instances, and 12 dry-run instances. Hover over a scheduling type block to view a detailed list of scheduled instances, including the scheduling type, condition, and condition name. Conditional scheduling: If you enable conditional scheduling, you must select a Configuration Method: Custom Settings or Scheduling Template. Important The system evaluates condition groups (up to 10) sequentially from top to bottom. When a condition is met, the system executes the corresponding action and stops evaluating further. If no conditions are met, the default scheduling settings are used. Conditional scheduling takes effect only when the scheduling type is Normal Scheduling. The scheduling conditions and start time are calculated based on the configured Scheduling Timezone. Custom Settings Click +Add Scheduling Condition. In the Edit Conditional Scheduling dialog box, configure the conditional scheduling settings. Condition Name: Any characters are allowed. Maximum length: 32 characters. Effective Status: Enabled by default. If disabled, the system ignores this conditional schedule. Meet the following conditions: Defines the evaluation rule. When the condition evaluates to true, the task is scheduled based on the Execute Scheduling configuration. For more information, see Conditional scheduling rules. Execute Scheduling: Options: Custom and Follow Scheduling Properties. Custom: When the condition is met, the task runs according to the specified Scheduling Type. Follow Scheduling Properties: Applies the main scheduling policy, equivalent to running the task without this conditional schedule. Scheduling Type: For configuration details, see Scheduling types. Click OK. After you configure conditional scheduling, click Preview Scheduling Run Plan to view matching dates on the calendar. Important After you submit and publish changes to conditional scheduling settings in the production environment, the new settings take effect immediately for instances in the Not Run state. Instances already in the Waiting for Run Time state are not affected. If a conditional schedule uses a cross-node parameter for evaluation, you must provide possible parameter values for the preview. Scheduling template After you select Scheduling Template, you can choose any conditional scheduling template configured in Planning > Common Definition > Offline Scheduling Template. If no template meets your requirements, click New Scheduling Template to create one. After selecting a template, you cannot add new scheduling conditions. Click the View Details icon next to each condition to view its details. Note The start time parameter in the referenced conditional scheduling template takes effect if the task's scheduling cycle is Day, Week, or Month. The parameter is ineffective if the cycle is Hour or Minute. upstream dependency: Upstream dependencies are automatically generated based on the derived indicator and cannot be modified or deleted. If you modify the dependency cycle to a time unit smaller than the indicator's data timeliness, a self-dependency is automatically added for the node.
   Description	Enter a description of the derived indicator, up to 1,000 characters.

8. Click Submit, enter your Submission Comments, then click OK and Submit to submit the derived indicator.

Next steps

If your project uses Dev-Prod mode, you must publish the derived indicator to the production environment. For more information, see Manage publish tasks.