TVC Classic - 2026.1.0
# Example configuration for handling large datasets
tvc.core.db.table.evaluator.chunkSize=5000
tvc.core.db.table.evaluator.statementsThreshold=20TVC 2026.1.0 Release Information
23 January 2026
2. Core
2.1. Enhanced Database Table Evaluation System
In this release, we have introduced a comprehensive set of properties to control and optimize database table evaluations. These new configurations provide administrators with greater control over performance and resource utilization when handling large-scale database operations.
Properties
| Property | Description | Default Value |
|---|---|---|
tvc.core.db.table.evaluator.chunkSize |
Defines the size of chunks when processing database table evaluations. This enables processing of large datasets in smaller, manageable chunks to optimize memory usage and prevent memory overload issues. |
0 |
tvc.core.db.table.evaluator.statementsThreshold |
Sets the threshold for the number of statements enables automatic chunking only when the number of statements to evaluate exceeds the defined limit |
15 |
The chunking mechanism and configurable statement threshold improve performance and stability by breaking large evaluations into memory-efficient batches and enabling chunking only when the number of statements exceeds the defined threshold. This reduces peak memory and connection usage, prevents resource exhaustion during large operations.
Implementation Example
For large-scale operations, you can optimize performance by adjusting these properties in your configuration:
2.2. Optimized Session Bean Cleanup
Session cleanup handling has been optimized to ensure that server-side beans and resources registered for cleanup are removed more reliably when users navigate away from a page or when the page is unloaded. This prevents resource identifiers from lingering in the session longer than necessary and reduces unnecessary server-side resource retention.
The release enhances the cleanup mechanism by consistently invoking the cleanup service during the pageHide event using
a fail-safe approach. This optimization improves Java heap utilization by promptly releasing unused beans and resources, reducing memory retention,
lowering garbage collection pressure, and minimizing the risk of out-of-memory conditions in high-load or long-running sessions.
3. Structure Browser
3.1. Table Export Performance Improvements
This release introduces significant performance enhancements to the table export functionality in the Structure Browser. These improvements focus on optimizing database operations and reducing unnecessary evaluations during the export process.
A major optimization has been implemented through the existing ExcludeFromReport setting for columns. ExcludeFromReport setting is used to exclude the columns in export.
Columns marked with this setting will be automatically excluded from evaluation during export operations, resulting in reduced number of statements executed
with faster export processing time.
|
Consider marking columns with "ExcludeFromReport" if they contain complex evaluations that are not essential for exported reports. |
The table export process leverages the new evaluator properties (see Enhanced Database Table Evaluation System) to optimize large data processing. These improvements, combined with the smart column evaluation, provide significant performance benefits.
4. Mail Configuration
4.1. SMTP Authentication Support
TVC provides a built-in email feature that allows users to send emails for various use cases, such as:
-
Sending notifications related to business objects
-
Distributing collections.
Starting with this release, TVC supports SMTP authentication for sending emails. If the global property tvc.core.mail.smtp.auth=true is enabled, TVC will send emails using SMTP authentication. Default Value is false.
If this property is not enabled, the application will attempt to send emails without SMTP authentication, preserving backward compatibility
To enable SMTP authentication, define the following properties in the tvc.properties file:
| Property | Description | Default Value |
|---|---|---|
tvc.core.mail.smtp.host |
Specifies the SMTP server host name for sending emails, for example- |
|
tvc.core.mail.smtp.port |
Specifies the port number on which the SMTP server listens for email connections. Common values are |
25 |
tvc.core.mail.smtp.auth |
Enables or disables SMTP authentication. Set to |
false |
tvc.core.mail.smtp.user |
Specifies the email address used to authenticate with the SMTP server when authentication is enabled. |
|
tvc.core.mail.smtp.password |
Specifies the App password associated with the configured SMTP user. This value is used only when SMTP authentication is enabled. |
When these properties are configured, TVC will use them directly for SMTP authentication while sending emails.
Fallback Configuration via enovia.ini
If the SMTP properties are not defined in tvc.properties, TVC will automatically fall back to retrieving the configuration from the enovia.ini file using the following parameters:
| Property | Description | Default Value |
|---|---|---|
MX_SMTP_HOST |
Specifies the SMTP server host namefor sending emails, for example- |
|
MX_SMTP_PORT |
Specifies the port number on which the SMTP server listens for email connections. Common values are |
25 |
MX_SMTP_SENDER |
Specifies the email address used to authenticate with the SMTP server when authentication is enabled. |
|
MX_SMTP_PASSWORD |
Specifies the App password associated with the configured SMTP user. This value is used only when SMTP authentication is enabled. |
This ensures compatibility with existing Enovia-based configurations.
For the property tvc.core.mail.smtp.password and MX_SMTP_PASSWORD, an App Password must be used instead of the actual email account password. (for example, when using Gmail or other providers that enforce app-based authentication).
|
| Properties defined in tvc.properties take precedence over values configured in enovia.ini. |
Please refer Mail Configuration for more details.