PLANTA customizer 39.5.23

27503

Logging and Performance in ICOU have been improved.

27511

New maintenance module 009DV7 Python Warn Log, in which warnings from the system regarding Python customizing are collected and listed grouped by category, as well as the new Clean up Python warning log event, which deletes warnings that are at least 30 days old, have been implemented.

• Once you have resolved the reason for a warning, you can delete the record in the module manually or wait until the event has cleared up the warnings.

26406

The option to read out the data of a PLANTA project module via the web has been implemented. The data for a module are provided as JSON by default. Alternatively you can receive a JSON schema file for a module instead of the module data. For further information, see here.

27739

New DF behavior "hm", which turns the e-mail fields into hyperlinks, has been implemented. Please refer to our client release notes, as the function must be supported by the corresponding client.

27277

The place of use in the Object Use module is filled with a default value when the module is opened.

27441

The new Session startup events event type with the eponymous module has been implemented. For further information, see Programmable Events.

27389

DI066000 and DI066001 have been converted to real in order to facilitate aggregation/summarization of employees' vacation and absence data into their higher-level departmental resources.

27698

27742

Performance improvements in the update process have been achieved.

27900

Since IronPython customizing is no longer supported, the DI062333 HTML template for value range no longer has any function and has been removed.

27825

The customizing.events.module.run_module and customizing.events.module.run_module_persistent_session event functions now have a 3rd parameter for specifying a timeout (in seconds) for the maximum time to wait until the module has been executed. Find further information under Time-Controlled Events and Startup Events

27626

The new Open context in PyCharm menu item has been added to the Tools → Python menu. If the menu item is clicked on while a field belonging to a Python object is focused, the corresponding file is opened in PyCharm. In order to use the menu item, a few requirements must be met. For further information, see here.

27697

Migration packages that only have to run up to a certain version due to their dependency are now no longer marked as “not relevant” in the subsequent versions, but are set to “completed” and thus removed from subsequent migrations.

27521

The ICOU now automatically recognizes if the stored reference data does not match the current update. In this case, the (cross-release) migration package ApplyInCaseOfUpdate reports an error. If the correct reference has been imported via DB Update / ICOU -> Preparation -> Import reference, the packet can be run again in order to find the adjustements automatically and apply the ICOU.

27508

The new icou_deployment.par parameter file for deploying ICOU changes from the development system to the productive system, has been implemented.

27814

New folders have been implemented in which customer-specific Python files can be saved and added to the Python path:

• /py/customer/

• /jython/kunde/

The directories already contain template files for user-defined PLANTA link mapping functions, web interfaces and transformers.

Restrictions: It is not permitted to have a /py/customer/api/ directory (this prevents login)

27363

A framework has been implemented that enables the reuse of the same clientless session across multiple calls.

There is a new PersistentClientlessSession class that builds up on ClientlessSession and can also be used as context manager. Unlike the ClientlessSession context manager, where the session is exited when the context is exited, with PersistentClientlessSession the session remains open when the context is exited. For further information, see here.

22

Risk charts can now be created in any desired size.

Web 3.1.0

Key

Description

27674

Time-controlled events that were not executed at their configured time (e.g. due to a server restart or delayed execution due to several simultaneously scheduled timed events) are based on the last execution time, which causes the next execution time to shift further and further away from the configured execution time.
This issue has been fixed and the runtime has been improved when scheduling long-lasting events with short intervals.