PLANTA customizer 27

2682

Auxiliary packages for transferring module customizations to the Web Client modules

As of DB 27, every standard module is also available as a Web Client module. Individual customizations made to the desktop modules before the update are missing from the Web Client modules. Two new help packages transfer these customizations:

• Wi2682_webclient_diff_report (report): Identifies new data areas and data fields as well as modified standard data fields, data areas, and assignments in the desktop modules, and writes to the log, grouped by module, data area, and data field, what is missing in the Web Client module, what already exists, and what is in conflict. The report does not change anything.

• wi2682_webclient_diff_transfer (transfer): Transfers all missing customizations that can be applied without conflict to the Web Client modules and lists every record written in the log. Attributes that PLANTA has deliberately set differently in the Web Client, or that have already been customized there, are not overwritten but reported as conflicts. The package can be run multiple times.

The packages do not run automatically with the update; they are started in the migration module: Report, back up the DB, transfer, restart the worker, report for verification. Requirement: The update was run with ICOU (DT406_REF, DT410_REF, DT411_REF exist), and the reference tables belong to the current DB version. There is no automatic rollback. For systems on DB 27.0/27.1, the packages are available as a separate delivery.

2948

Triggers: Batch Writing

Triggers have the new field Batch writing allowed (BATCH_WRITING_ALLOWED, default value 0). If several records in a table are changed together, the server loads them with a single query, provided that all update and on-change triggers of this table allow it. Otherwise, it writes them individually as before.

Triggers supplied as standard are already set accordingly. Custom triggers have the value 0 after the update and therefore retain their previous behavior. Only set the value to 1 if the trigger does not read or write any other records in its own table. This requires the current server.

3536

Automatic cleanup of outdated user-defined submodule configurations

User-defined submodule configurations (settings specifying which submodules a user wants to load automatically) could deviate from the module customizing over time, e.g., if a submodule was removed. For each of these outdated configurations, an error was written to the log file every time the user logged in, without the data ever being cleaned up.

Outdated configurations for which no submodule exists anymore are now automatically deleted at login. Instead of one error per configuration, only one warning listing the cleaned-up modules is now written to the log file per user.

3653

The delivery database is now leaner: As a result, new installations run faster and the database uses less storage space.

3661

The customizing image no longer contains Python packaging tools (pip, setuptools, wheel) and therefore none of the previously reported vulnerabilities in these packages. Custom images that are based on the customizing image and require pip install it with python -m ensurepip.

3723

MSSQL: The license foreign key of the DT401 (Model Parameters) and DT439 tables were deactivated or marked as untrustworthy after reinstallation and update. The update activates it again and in doing so, checks the existing data. If a table contains records with a license that is missing in DT345, the foreign key is activated without this check. New records with an invalid license are rejected.

3820

Change Person ID: Configuration of individual tables

The columns containing a resource ID are predefined for the standard tables. The columns Created by and Changed by are are changed automatically in all tables. In the DF Configuration (RESS_CHANGE) of the Change person ID button, only custom tables and data items are now added, one line per table: Table number, then the data items. The configuration check reports a data item that cannot hold a resource ID before the change.

3368

LDAP Import: Locking of additionally assigned AD fields

For persons from the Active Directory PLANTA locks the fields that the LDAP import fills in the standard assignment, now including Surname, Name, and the e-mail addresses. Anyone who maps additional AD attributes to PLANTA fields in the assignment of the LDAP interface must lock these fields themselves, e.g., with a checkInput that queries ppms.user_creation.person_is_ldap_locked().

3575

The migration packages for transferring roles to user groups now report errors correctly: If an error occurs, they fail instead of being marked as successful, and they are executed again during the next update. Roles without modules, e. g., menu item roles, no longer cause errors. Memberships in user groups that are maintained via the LDAP import are not carried over by the migration; these are set by the next LDAP import.

3437

The avatar is now stored on the person instead of the resource. The update carries over existing avatars from resources with an assigned person. Custom customizing that reads the avatar from the resource (DT467, column AVATAR) must be switched to the person (DT516), since the column is removed during the update.

3600

When updating a database at DB 39.5.22 or older, individual migration packages (e. g., UnloadAndReplan) were executed twice, which could prolong the update. When updating from DB 39.5.22 or older to 27.2.0 or newer, this problem no longer occurs.

3762

When updating to DB 27.x, customer-specific charts are migrated to the new chart definitions (column width, display of empty data points, axis, legend, and marker parameters that are no longer supported), and the chart fields are regenerated. This applies to updates from DB 26.x and to systems that have already been updated to DB 27.0 or 27.1. An axis interval in hours, minutes, or seconds is set to Automatic. These intervals are no longer offered in the chart customizer, since the charts already determine them automatically. Columns of the CHARTDATASERIES table that are no longer used are removed.

3764

The minimum angle for displaying labels (MIN_ANGLE_TO_SHOW_LABEL) is now also stored with decimal places after an update and is no longer rounded to whole degrees. Under MSSQL, this eliminates the “Database Schema does not match” warning at server startup.

3763

When updating to DB 27.x under MSSQL, missing self-referencing foreign keys that a new installation has (e.g., for parent projects, interface mappings, or chart parameters), indexes, and delete triggers are created, and orphaned records are cleaned up.

3776

Security fix: For web interfaces with a token in the path (/api/<token>/…), the trigger log (Event.log) no longer logs the token in plain text but masks it, like the access log.

3787

Generated migration packets for new data fields no longer fail during updates when the column already exists in the database.

3788

Warnings already recorded in the warning log (e. g., notices about outdated customizing functions) are no longer written to the server log as WARNING at every login or module call, but only the first time they occur. Repeated occurrences appear at log level DEBUG. The warning log module continues to display all warnings unchanged.

Warnings from sessions without a logged-in user (e.g., interface and background sessions) are now recorded in the warning log immediately. As a result, a warning appears in the server log as WARNING only the first time it occurs, and no longer in each of these sessions until a user logs in.

3824

ICOU: Conflicts whose change was removed during an update (e.g., after the resolution “Always apply PLANTA value”) are now deleted as well.

1863

2746

2299

The new PowerPoint export is adjustable per customizing. For further information, please see here.

1767

In the chart customizer, the new attribute Show Label from Angle (Python ID min_angle_to_show_label) is available for pie charts. Labels are only displayed from the specified segment angle onward.

2746

The Module Reader now reads chart data fields as images and outputs them Base64-encoded in the JSON, with contentMediaType and contentEncoding. This is required, for example, for the PowerPoint export.

2822

The DI for Auto Pos. field (DI001985) can be set again in the Data Dictionary.

2387

The ActivateNewDesign migration package sets the value of the Skin user parameter to “PLANTA Standard Skin (New)”, thereby switching the system to the new design, new navigation, and new permission concept for all users.

• 1298

• 1571

• 1299

• 1318

New navigation elements in the application are customizable:

• Badges,

• Action bar in the panel title bar

• Overflow menu including the “+” creation menu in the user menu

Web 4.0.0

747

Buttons in modules can be configured for the Web Client with new design options (type, size, label, icon, and danger flag configurable).

1619

An OLE pro module can be stored on DT405 now. This is required for display in the new user menu. The required OLE file is stored in the Icon parameter in the Further Module Parameters module.

2262

1761

New Configuration matrices implemented: Module visibility and authorizations can now be consistently configured.

S 39.2.0

1747

The Deeplink configuration (DF configuration) now supports JSON; enables combined Deeplink and button styling in a field.

1961

New options in the Chart customizer: Show/hide axis labels (ShowLabels), configure the donut center label (DonutCenterLabel, DonutCenterTotalText), hide grid lines and axis lines by setting their width to 0.

Web 4.0.0

2083

Agile authorizations are customizable: Custom authorization rules (e.g., who is allowed to create activities/views) can be defined for the agile views.

2409

The font can no longer be changed in symbol customizing, since the setting no longer had any effect on the client side anyway.

1481

1644

The SVG data fields (Standard OLE SVG, Mouseover OLE SVG) are now available in the standard modules OLEs and OLEs by Category and can be maintained there.

1595

Four new columns for token-based gRPC authentication (refresh tokens) on DT443 are now created automatically via a migration package.

S 39.2.0

2372

The ICOU note for a changed reference value now contains the old and new values and a clear call to action for manual review.

1849

Fixed the error message “@G96 does not exist” when storing files in DI009421.

1872

PortConditional: Fixed the error “No such file or directory: config/globals.conf”.

WorkDirConditional is outdated in Docker environments. The working directory in Docker is always /planta. Customers migrating from a pre-container version who use WorkDirConditional must adjust their configuration.

1905

Internal (Pulse) and external (Jira webhook, Teams) URL generation via planta_link_hostname can now be configured independently. There is no longer a conflict between the internal container host name and external webhook URLs.

2242

The ICOU action “Change to Individual Value” failed after certain updates. The behavior is now consistent with the alternative action “Change to Individual Value (Don’t Ask Again)”.