Business conditions are used to define the scope of business statistics. This topic describes how to create a business condition.
Prerequisites
Before you proceed with the operation, ensure that a business entity has been created. For more information, see or 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 based on whether you need to create a business condition on a logical dimension table or a logical fact table.
Data Domain
The subject area where the business object or business activity is located is selected by default.
English Name
As you enter the English name, Dataphin will perform a real-time match against the configured roots within the data standard based on the provided data. You can then choose the suggested root to serve as the English name for the business entity. For more information, see create and manage roots or .
The English name must comply with the following naming conventions:
Only letters, numbers, or underscores (_) are supported.
Cannot exceed 64 characters.
Chinese Name
The naming conventions are as follows:
Any character is supported.
Cannot exceed 128 characters.
Description
Provide a brief description of the business condition, within 1000 characters.
Calculation Logic
Business Condition Type
Supports Simple Condition and Composite Condition.
Basic Business Condition: The calculation logic is an expression composed of fields from the logical table. You can set the range conditions for the required metrics based on the fields in the source logical table model, such as:
is_wireless='Y' -- is_wireless is a field in the source logical table model
Composite Business Condition: A business condition obtained by combining other submitted business conditions through three operators: and, or, not. Composite business conditions are divided into two types of operators:
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 completing the configuration of the combined business condition relationship, single click Preview Calculation Logical SQL to view the final SQL expression of the combined business condition. 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
You can select data timeliness for the business condition based on the business situation. Data timeliness includes 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 or .