Business conditions define the scope of business statistics. You can create a business condition based on a business entity.
Prerequisites
Before you perform this operation, ensure that a business entity has been created. For more information, see create and manage business entities.
Procedure
-
On the Dataphin home page, single click the top menu bar Development. By default, you will enter the data Development page.
-
Follow the instructions in the figure below to enter the New Business Condition dialog box.

-
In the New Business Condition dialog box, configure the parameters.
Parameter
Description
Basic Information
Business Entity
Select a business object or business activity depending on whether the business condition applies to a logical dimension table or a logical fact table.
Data Domain
The data domain of the selected business object or business activity is populated by default.
English Name
-
As you type the English name, Dataphin matches it in real time against roots configured in the data standard. You can select a suggested root as the English name for the business entity. For more information, see create and manage roots.
-
The English name must meet the following requirements:
-
Only letters, numbers, or underscores (_) are supported.
-
Cannot exceed 64 characters.
-
Chinese Name
The naming requirements are as follows:
-
Any character is supported.
-
Cannot exceed 128 characters.
Description
A brief description of the business condition. Maximum: 1000 characters.
Calculation Logic
Business Condition Type
Supports Simple Condition and Composite Condition.
-
Basic Business Condition: An expression composed of fields from the logical table. Use fields in the source logical table model to set range conditions for metrics. Example:
is_wireless='Y' -- is_wireless is a field in the source logical table model -
Composite Business Condition: A combination of submitted business conditions joined by the AND, OR, and NOT operators. Two types of operators are used:
-
Rule Operator: Supports two rules: Match and Not Match (i.e., not).
-
Relational Operator: Supports two rules: And and Or.
-
Add Rule: Single click Add Rule to add a blank rule under the same level relational operator.
NoteRules can only select business conditions that have been submitted under the current main source table.
-
Add Relationship: Single click Add Relationship to add a sub-level relationship under this relational operator.
After you configure the composite business condition relationship, single click Preview Calculation Logical SQL to view the final SQL expression. For example:
--Small Size: size in ('XS', 'S') --Cute Style: style in ('Cartoon', 'Comic') --Synthetic Fabric: material_type in ('xxx', 'yyy', 'zzz') --Young Customers: customer_age_range = '5~10' (size in ('XS', 'S') and style in ('Cartoon', 'Comic') and not material_type in ('xxx', 'yyy', 'zzz')) or customer_age_range = '5~10' -
Reuse Other Data Timeliness: Single click Reuse Other Data Timeliness to overwrite the current data timeliness with the calculation logic of other data timeliness.
-
Data Timeliness
Select a data timeliness granularity for the business condition. Supported values: days, hours, and minutes.
-
-
After configuration is complete, single click Save And Submit to submit the business condition.
What to do next
In Dev-Prod project mode, you must publish the business condition to the production environment. For more information, see manage publishing tasks.