- biGENIUS-X Knowledge Base
- Best Practices
- Business Rules
-
Getting Started
-
General Overview
-
Application Modules
- Administration
- Global Features
- Solutions
- Projects
- Branches
- Source Systems
- Dataflow Modeling - Overview
- Dataflow Modeling - Wizard Steps
- Dataflow Modeling - Terms
- Dataflow Modeling - Term Mapping
- Dataflow Modeling - Relationships
- Relationship Modeling
- Generate Artifacts
- Project Settings
- Data Marketplace
-
Generators
-
Discovery application
-
Best Practices
-
FAQs
-
Product Release Notes
-
Legal Documents
Not Cyclic Dataflow
Various Business Rules are checked after a change is made to a Model Object. These checks ensure the integrity and consistency of the model.
No Cyclic Dataflow
This Business Rule checks if a Model Object has a cyclic dataflow defined.
Example:
- Model Object A is a Source Object of Model Object B
- Model Object B is a Source Object of Model Object A
This check has no parameter.
If the Business Rule validation fails, the following message will be displayed as an Error Notification on the Model Object:
Model object '{ModelObject.Name}' of type '{ModelObject.ModelObjectType.Name}' has a cyclic dataflow defined.
Example: