Deutsch
|
English

DISPLAYTECHNICALNAMES - Detailed description

Administration

IC2879
Administrator
Administration

Overview

Parameter:DISPLAYTECHNICALNAMES
Category: Debug
Default value: 1 (technical names are displayed)
Product: eTASK.Other (Debug)


What does this parameter do?

This parameter controls whether the technical database table names are displayed when deleting a record if there are still links to other records. If you want to delete a record that is still linked to other data, the portal displays a message indicating which dependent records exist. This parameter determines whether, in addition to the user-friendly descriptions, the technical table names are also displayed in square brackets. These technical names are primarily relevant for eTASK Support to provide faster assistance in case of unexpected behavior.


What is this parameter used for?

  • Display of technical database names in deletion prompts

  • Assisting eTASK Support with error analysis

  • Accelerating support requests for deletion issues

  • Diagnosis of unexpected dependencies


Technical Details (for Administrators)

Format: Integer (0 or 1)
Default value: 1 (technical names are displayed)

Valid values:

  • 0 = Technical table names are NOT displayed (descriptions only)

  • 1 = Technical table names are displayed (default value)

Important notes:

  • Applies only to notes when deleting records with links

  • Displays database table names in square brackets after the description

  • Format when enabled: "Description - [TABLE NAME]"

  • Format when disabled: "Description"

  • Has no effect on standard user interfaces

Functionality:

When a user wants to delete a record, the system checks for links to other records. If links exist, a message is displayed with a list of all dependent areas.

When DISPLAYTECHNICALNAMES = 1:
- The following is displayed: "Room bookings - [RE_RAUM_TERMIN_T] (5 records)"
- Technical name enables eTASK Support to perform precise analysis

When DISPLAYTECHNICALNAMES = 0:
- The following is displayed: "Room bookings (5 records)"
- Only the user-friendly description is shown


When should you change this value?

Set the value to 0 (hide) if:

  • You prefer a clean user interface without technical details

  • Users should not be confronted with the database structure

  • Technical names are perceived as confusing or distracting

  • A strict separation between the application and the database is desired

  • End users should work exclusively with application logic

Leave 1 (display) if:

  • You want to provide precise information in support tickets

  • You want to facilitate the analysis of deletion issues

Recommendation: Set to 0 (hide technical names)

End users and administrators typically do not need to know the database structure. The user-friendly descriptions are sufficient for daily operations. Technical table names are primarily relevant to eTASK Support, which can determine this information as needed even without it being displayed in the portal.


Important Notes

  1. Note, not an error message
    If relationships exist, the portal displays an informative note, not an error message. Deletion is prevented to ensure data integrity.

  2. Primarily relevant for eTASK
    Support The technical table names are mainly useful for eTASK Support when analyzing unexpected behavior, less so for daily operations.

  3. No impact on data integrity
    The parameter only changes the display, not the behavior of the links or data integrity.

  4. Cleaner user interface
    With a value of 0, the interface appears more professional and less technical, which increases user acceptance.

  5. Support can help even without it
    If necessary, eTASK Support can determine the relevant table information even without it being displayed in the portal.


Security

Does changing this parameter affect security?

Yes, this parameter has indirect security implications.

Note:

  • Displaying technical information can provide attackers who are already active in eTASK with additional information about the application.

Recommendation: Avoid displaying technical information in the user interface.


Practical example

Initial situation: A facility manager wants to delete a room from the system because it is no longer in use. However, the room is still listed in room bookings, inventory lists, and cleaning schedules. The portal prevents the deletion and displays a note regarding the existing links.

Situation with DISPLAYTECHNICALNAMES = 1 (default, not recommended):

Note when attempting to delete:

Problems with this display:

  • Facility manager sees cryptic designations such as "RE_ROOM_DATE_T"

  • Technical names are confusing and appear unprofessional

  • Gives the impression that technical knowledge is required

  • Distracts from the actual information

  • Looks like an error message instead of a helpful hint

Situation with DISPLAYTECHNICALNAMES = 0 (recommended):

Note when attempting to delete:

Advantages of this presentation:

  • Clear, understandable descriptions without technical jargon

  • The user immediately understands: "There are still 15 room bookings"

  • Professional, uncluttered presentation

  • Focus on information relevant to the task

  • No confusion caused by database terminology

  • User-friendly guidance instead of technical error messages

Communication to users:

No communication is required during the transition because:
- The change only removes
technical details - All relevant
information remains
visible - User-friendliness is improved - No functionality is lost


For production systems:0 (hide technical names)
For development/test systems: 0 (also hide, unless for specific debugging purposes)

When a value of 1 might be temporarily useful:

  • Only upon specific request from eTASK Support for special analyses

  • Temporarily for debugging purposes in case of recurring deletion issues

  • After the issue is resolved, the value should be set back to 0


War dieser Artikel hilfreich?