biGENIUS-X offers the option to modify the default behavior of a Generator Configuration using Advanced Settings.
More details about how to manage the Advanced Settings are in the article Understand the Advanced Settings overview.
There are height customizable configurations available:- Default Values
- Default Terms
- Custom Default Terms
- Naming Rules
- Custom Properties
- Template Modules
- Warnings
- Documentation
Default Values
In a Generator Configuration, each Property comes with a Default Value.
For instance, the Property determining the Target Object Type for a Stage Object is initially set to "Table" by default by setting the Implementation Type to Cached.
So, whenever you create a Stage Model Object, this property will automatically be set to Cached, resulting in the creation of a table.
You can manage the Default Values of Properties within the Advanced Settings.
This will replace the Default Value coming with the Generator Configuration.
You can also manage the default values of Custom Properties within the same Advanced Settings.
For more details, please refer to the article Manage Default Values.
Default Terms
A Generator Configuration includes Default Terms for each Model Object Type.
For instance, in Data Vault modeling, each Model Object of type Hub will have a default term called BG_LoadTimestamp and containing the load date of a row.
The list of all existing Default Terms is available on the Generator documentation section.
You can change the data type of a Default Term or define a Naming Convention using some placeholders.
This will replace the Default Term proposed by the Generator Configuration.
For more details, please refer to the article Manage Default Terms.
Custom Default Terms
Within the Advanced Settings, you can define Custom Default Terms to suit your specific requirements.
For instance, you may be interested in storing the SQL User who created a record in your target system.
For more details, please refer to the article Manage Custom Default Terms.
Naming Rules
A Generator Configuration includes Naming Rules for each Target Object.
For example, in Data Vault modeling, each Table for a Model Object of type Hub will be prefixed with "RDV_HUB_XXX" where XXX is the Hub name.
You can set a different Naming Rule using Advanced Settings.
This will replace the Naming Rule set by the Generator Configuration.
For more details, please refer to the article Manage Naming Rules.
Custom Properties
A Generator Configuration includes Properties that determine its behavior.
For instance, for a Model Object, you can specify whether the generated object will be a view or a table, thanks to the Implementation Type Property.
Additionally, you have the flexibility to define Custom Properties to cater to your specific requirements.
You can define Custom Properties within the Advanced Settings.
These Custom Properties can then be incorporated into your Custom Template Modules, allowing you to tailor their behavior to align with your specific needs.
For more details, please refer to the article Manage Custom Properties.
Template Modules
A Generator Configuration includes Template Modules to define which code will be generated.
For instance, for a Model Object of type Stage, a Template Module written in C# will define that if the Implementation Type Property mentioned earlier has the value 'Cached', it will generate the SQL code to create a table.
But if the same Property has a different value, such as Virtual, it will generate the code to create a view only.
Using Advanced Settings, you have the option to define various Template Modules.
These Custom Templates Modules will replace the Default Template Modules provided by the Generator Configuration.
However, it's essential to note that creating a Template Module requires a deep understanding of the default behavior of the Generator Configuration in order to make smooth modifications.
While it's technically possible to customize a Generator Configuration using Advanced Settings, it's strongly discouraged.
This approach typically requires thorough checks and tests after each Generator Configuration version upgrade, which can be time-consuming and prone to errors.
Instead, it's recommended to explore standard options that can adequately meet your needs.
For more details, please refer to the article Manage Template Modules.
Warnings
A Generator Configuration includes checks for Business Rules.
If a Business Rule is not followed, an error or warning notification is displayed in the application.
Users have the option to hide warnings if they believe they are consistent with their context.
In the Advanced Settings, you can manage the hidden warnings and choose to display them again.
For more details, please refer to the article Manage warnings.
Documentation
biGENIUS-X includes a template for Documentation generation.
In the Advanced Settings, you can customize this template to meet your specific needs.
For more details, please refer to the article Manage Documentation.