Zum Hauptinhalt springen
Deutsch
|
English

BUILDNUMBER - Detailed description

FM-Portal

IC2873
FM-Portal

Overview

Parameter:BUILDNUMBER
Category: Default
Default value: "0"
Product: eTASK.FM Portal

What does this parameter do?

This parameter stores the build number of the current portal installation. The build number is automatically entered after a successful update and is used for version control between the database and the application. It is also used for cache busting to ensure that browsers load new versions of JavaScript and CSS files after an update.

What is this parameter used for?

  • Version synchronization between the database schema and the program version

  • Ensuring compatibility after updates

  • Cache busting for static resources (CSS, JavaScript, images)

  • Preventing browser caching issues after updates

  • Diagnostics and support (identification of the installed version)

Technical details (for administrators)

Format: Numeric string
Default value: "0"

Valid values:

  • Any integer as a string (e.g., "64", "127", "345")

  • "0" = Default value for new installations or if no build number is set

Important notes:

  • The build number is set automatically during the update process

  • It corresponds to the third part of the assembly version (e.g., 7182 from 2025.3.7182)

  • Browsers interpret different URL parameters as a new resource and reload it

  • Manual changes are not permitted

Interaction with other parameters:

  • VERSION: Stores the complete version number (e.g., "2025.3.7182")

  • Both parameters together provide complete version information

When should you change this value?

Let the value change automatically (default) if:

  • You perform an update of the eTASK.FM portal

  • The update program is running and the database version is being updated

  • You follow the normal update procedure

Change the value manually if:

  • never

Important notes

  1. Automatic management via the update process
    The build number is set automatically during the update process. Manual changes are not required.

  2. Impact on browser cache
    A change to the build number causes all browsers to reload all static resources (CSS, JavaScript). This can lead to increased server load for a short time.

  3. Diagnostic tool
    The build number is an important diagnostic tool for support. Support requests often ask for the build number.

Security

Does changing this parameter affect security?

No, changing this parameter has no direct security implications. It is version information.

Note:

  • The build number is publicly visible in HTML source code (URL parameter)

  • Attackers can use this to determine the installed version

  • Outdated build numbers could indicate unpatched systems

Recommendation: Always keep your system up to date and let the update process manage the build number automatically. This ensures that security updates are applied correctly.

For all installations: Automatic management via the update process (default)

Reason:

  • The build number is set automatically during the update

  • Manual interventions are error-prone and not permitted

  • Automatic synchronization between program and database versions

  • Correct version information for support and diagnostics

  • Optimal cache-busting behavior

Exceptions (manual change):

  • Support instruction: Only upon explicit instruction from eTASK Support

War dieser Artikel hilfreich?