Version C 39.5.13

• The Balloon Notification for dialog messages has been activated. It is displayed if a dialog message is displayed in the background of a PLANTA session. In addition, the respective session flashes in the task bar.
• The client now also supports Windows Server 2012 and Windows Server 2012 R2.
• A dynamic display of the horizontal or vertical grid lines have been implemented.
  • The distance between the vertical grid lines is influenced by the width of the scale, the distance between the horizontal grid lines by the values to be displayed.
• New variables have been added, by means of which the current print time can be included in the print footer or header.

Bug fixes

• The problem, that a wrong cursor was displayed when moving/copying via Drag&Drop has been resolved.
• The sporadically occurring System.NullReferenceException: Object reference not set to an instance of an object. client error message that, occurred when e.g. opening the Task module, has been resolved.
• A client crash in connection with incorrect chart customizing has been fixed.
• The visualization of several bars in the print preview has been improved.
• Problems for individually customized export to Excel using the IronPython functions CreateExcelExportDocument and GenerateExcelFile have been resolved.
• The MemoryError: Exception of type 'System.OutOfMemoryException' was thrown. client error message when trying to create a PDF of a module with many charts, has been resolved.

Version C 39.5.12

Features

• For the Page break parameter, the value 4 has been added.
  • Each line/each record of the area is displayed on a new page with its child records, if they do not all fit on the current page.
  • In order to use this value, the value range of DI001583 Page break are extended by value 4.
• Windows path variables like %HOMEDRIVE% or %HOMEPATH% can be used for PDF export.
• Better error messages for problems with the Kerberos authentification. For an explanation of the different error codes, click here.
• Improvements in the evaluation of the client configuration and validation of parameters
• For vertical or horizontal layout, the data field or column width is displayed when moving the column separator in the status line.

Bug fixes

• Messages that are displayed in inactive or background panels, are now displayed in the foreground, i.e. on top of all opened panels.
• The problem, that when using the Zoom to page width menu item, the page width was not made use of due to buttons invisible in the print, has been resolved.
• the problem, that in the Print Preview charts were not loaded, but the charging symbol was displayed instead, has been resolved.
• The problem, that navigating to further results of the Search in module function via the arrow buttons was not possible after having clicked in an input field, has been resolved.
• The client crash when clicking on the scroll bar when using PLANTA project on Windows 7 with the text zoom size being changed, has been resolved.
• The problem, that certain modules cannot be exported to Excel, has been resolved.
• Redundant connections via the proxy configured in the operation system have been fixed.
• An OutOfMemoryException exception when trying to export to Excel (several times) in a complex module with plenty of data, has been fixed.

Version C 39.5.11

• Please note that in this client version the version specification in the title bar is C 39.5.10 by mistake. You can find out whether you are using C 39.5.11 or C 39.5.10, by taking a look at the changeset number (see table).
  • The version specification is displayed in the title bar until the login dialog is displayed. From this moment on, the system title is displayed.

Features

• Dialog messages stored in the client, that are displayed when establishing a connection, when exporting to Excel, when changing the password, etc. have been translated into Portuguese.
• When focussing a todo item in the Project Core Data from the Process Status module, the Process Status module is closed.
• When right-clicking on headings, the available but hidden data fields for the respective module area are now sorted alphabetically in the context menu.
• For the CreateExcelExportDocument method, the closeModule parameter has been added, with which you can define whether the module to be exported is closed after export to Excel, or not. Further information on this can be found in the IronPython API.
• Via an IronPython function, the protocol version of the server can be read. Further information on this can be found in the IronPython API.
• The print behavior for data areas with Positioning = 1 or 2 can be controlled via the Print setting parameter.

Bug fixes

• Problems with Exporting an empty module to Excel have been resolved.
• The problem, that bars were drawn beyond the scale, has been resolved.
• The problem, that the width of heading fields did not comply with that of the corresponding data fields, has been resolved.
• Problems with creating module variants has been resolved.
• The crash after the General error in GDI+ error message in particular customizing constellations, has been resolved.
• Problems with the visualization of fields in particular module constructions with Next to parent area = @Y and a high negative indent, have been resolved.
• Problems that occurred when working with two monitors, have been resolved.
• The (sporadically occurring) problem that the client crashed after a reconnect, has been resolved..
• The problem, that a recently closed dialog module was displayed via CTRL + Tab as a "corrupt" submodule without content, has been resolved.
• The NameError: global name 'env' is not defined error message when clicking in a info pop-up when using database version 39.4.4.0 with server version 39.4.4.0 and client version 39.5.x has been resolved.
• The problem, that after entering a wrong user name or password the Reconnect dialog message was displayed instead of the login dialog message, has been resolved.
• The problem, that when closing the server connection (e.g. due to a server crash or by canceling the service) the client did not establish the connection (Reconnect), but crashed instead, has been resolved.
• The following error message has been fixed: System.NullReferenceException: Object reference not set to an instance of an object.

Version C 39.5.10

• The Content pattern, Content thickness and Content density symbol parameters do work now.
  • This may cause layout changes of bars.
• For the shading of the (non) working days, the calendar stored in the System calendar parameter in the License, System Parameters and DB Instances module is used.
• The print behavior for data areas with Positioning = 1 or 2 has changed. Fixed data areas are displayed fixed at the top once when Position = 1 on the first page, when = 2 once on the last page.

Bug fixes

• Dialog modules
  • Visualization problems when scrolling in a dialog modul with opened listbox has been resolved.
  • The problem, that the dimmer function has not worked, has been resolved. It cannot be opened via the activate_dimming() und get_dimmming() functions. The description of this function can be found in the IronPython API.
  • in connection with freerdp
    • Problems with opening listboxes have been resolved.
    • The problem, that a main project was able to assign itself as a subproject, has been fixed.
• Problems when changing listbox sizes, e.g. Flickering and white spaces, have been resolved.
• Further occurrence of the DataFieldEnumerator errors: ... error has been fixed.

Version C 39.5.9

• In modules that contain a scale DI with a sub-DI with the SR function, non-working days are highlighted in the scale with the color stored in the sub-DI.
• From now on, the today line is a firm component of every scale and does not have to be customized explicitly. Exceptions: If a deviating layout for the today line is required, e.g., a different color or even invisible, the today line must be customized. For further information on this, see e.g. Time Scale in the Scales topic.
• The creation or changing of module variants can be switched off user or module related. For further information, click here.
  • This function required Server version S 39.5.7.
• If no data area is selected when exporting to excel, the Please select at least one data area! message is now displayed.
• For dialog modules, the indicator is also displayed for unsaved changes now * (asterisk).

Bug fixes

• The problems that occurred when using the 39.5.8 PLANTA Client with Windows XP and Windows 2003 have been resolved. The new Client 39.5.9 is operational for the mentioned operation systems.
  • The System.OutOfMemoryException: Out of memory exception error message as well as the display problems of the Icons in the user menu when starting PLANTA under Windows 2003, have been resolved.
  • The out of memory message when using the C 39.5.8 client under Windows XP, has been resolved.
• The overlapping of fields in the print review in connection with data fields with activated multi line parameter have been resolved.
• Problems when exporting formats on projected data fields to Excel, have been resolved.
• A Client crash when moving fields in the Customizing mode, have been resolved.
• The problem, that incorrect data is displayed in module titles with & sign, has been resolved.
• The problem, that the heading in particular, rare customizing constellations has been displayed displaced, has been resolved.
• A sporadically occurring problem in connection with the part string search in listboxes, has been resolved.
• The DataFieldEnumerator error message, that occurred in the Projects module when displaying columns via the context menu, has been resolved.
• The problem, that a wrong cursor was displayed when moving/copying via Drag&Drop, has been resolved.
• The problem, that heading fields for data areas with activated Next to parent area had the wrong size, has been resolved.
• The problem, that the IronPython library in the ClickOnce client was not contained completely, has been resolved.
• The DataFieldEnumerator error error message that occurred in the status line when switching module variants upon use of rare and special customizing constructions has been fixed.
• The use of storage has further been improved.

Version C 39.5.8

• The Client 39.5.8 cannot be used with the Windows XP and Windows 2003 operation systems.

Features

• Manual changing of the listbox size
  • This function is now available for each listbox.
  • The symbol for enlarging or downsizing a listbox is blue.
  • If a listbox above the field is opened, the symbol for changing the size is located in the upper right corner of the listbox.
• The minimum zoom size of checkboxes has been changed to 6x6 px.
• The documentation of the bulkExport parameter has been IronPythonAPI completed.
• The use of storage has been improved.

Bug fixes

• Problems when calculating data field lengths for parent data areas with structure, has been resolved.
• In the course of the improvement of the manual change the of listbox size, several problems have been resolved, e.g. The opening of a listbox via the task bar.
• The problem, that after moving a dialog module listboxes remained at the same position instead of closing, has been resolved.

Version C 39.5.7

• Hyperlinks support arbitrary URLs (e.g. Lotus Notes).
• When exporting modules with charts, the Processing charts for export to Excel... message is displayed.
• If the dialog window is opened when exportig to Excel, not only the current session, but also all other sessions are blocked.
• If PLANTA is closed while exporting to Excel, the following message is displayed: The Excel export is still in process. Do you want the export to be canceled and the PLANTA Client to be closed anyway?

Bug fixes

• The problem, that data exported to Excel have been displayed reversed or as a text, has been resolved.
• Problems when automatically exporting to Excel have been resolved.
• The problem, that pressing the Enter button has not had any function when only one data field has been available in the data area, has been resolved.
• The problem, that for particular customizing settings both in the print preview as well as for printing, only half of the last record on a page was displayed and the other half was displayed on the next page, has been resolved.
• The following problem has been resolved: If a heading field with a sorting symbol has been downsized as much as possible, the sorting symbol was displayed on the heading field next to it.
• The problem, that when creating new records in the Data Items module by pressing F4, sometimes the data field content of the field on which the key was pressed was displayed at another position in the module, has been resolved.
• A rare problem, due to which the Client with activated compression could not establish a connection to the server, has been resolved.
• The problem, that when changing the column width in modules with fixed headings, display errors occurred in the heading, has been resolved.
• The function of the DI002947Default zoom to page width parameter has been improved.
• The problem, that charts have not always been included when exporting to PDF, has been resolved.
• The problem, that listboxes were downsized after a value has been entered, but were not enlarged again when clicking outside, has been resolved.

Version C 39.5.6

• Changed settings for the bar tracking are saved and not reset when changing to another module variant.

Bug fixes

• The problem, that in some modules the format was not copied for some records when exporting to Excel, has been resolved.
• The problem, that the window separator jumped when it was clicked, has been resolved.
• The problem, that when moving columns, the columns were moved to a wrong position after scrolling horizontally, has been resolved.
• The problem, that the colors of the data fields have changed in a module if a dialog module was opened, has been resolved.
• The problem, that the quarter names on the quarter scale disappeared in some modules, e.g. In the My Department module, has been resolved.
• The following improvements have been made to the IronPython API:
  • The tabs for C#, Visual Basic and Visual C++ have been removed since they are not required.
  • Write errors in the IronPython tab have been corrected.
  • The display of the examples has been improved.
• The exception error message, that occurred when closing modules (e.g. the Data Areas module) in which a listbox was open, has been resolved.
• The problem, that startup modules have not been loaded completely if the window was minimized immediately after login, has been resolved.
• The problem, that when selecting a target folder that already contained data during the client installation with the help of the automatic installer, the data was deleted, has been resolved.

Version C 39.5.5

• Due to the newly implemented message compression, the network load caused by the communication between Client and Server has been reduced. This may lead to performance improvements.
  • This feature can only be used in combination with the use of Server version S 39.5.2.
• The None of the DA Python-IDs in DACsCU_NamesToExport existiert message, which is displayed if only non-existing data area IDs (DA Python-ID) are used in the CreateExcelExportDocument() IronPython function in the DACsCU_NamesToExport parameter, has been renamed None of the DA Python-IDs stored in DAsCU_NamesToExport exists.
• If one or more non-existing data area IDs (DA-Python-ID) are used in the CreateExcelExportDocument() IronPython function in the DACsCU_NamesToExport parameter, now the One or more of the DA Python-IDs stored in DAsCU_NamesToExport, do not exist. The data area(s) the DA Python Ids of which exist are exported.
• When using the CreateExcelExportDocument() IronPython function with the useBulkExport = true parameter without specification of the data area to be exported, the data area is exported with most records. The same applies if several records are specified.

Bug fixes

• Problems with the display of the cursor on scroll bars in connection with data fields with activated Multi-line parameter, have been resolved.
• The problem, that when closing a project, the previously opened listbox was not closed, has been resolved.
• The problem, that if in the same moment, in which a listbox was opened, a letter was entered, this letter was "swallowed", has been resolved.
• The outlook API is only activated if it is actually used. This solves the problem with opening the MS Outlook installation after closing the client upon incorrect or incomplete Outlook installation.

Version C 39.5.4

• From Client 39.5.4, there is no longer a division into several clients depending on the server used (e.g. Client for Server 39.4.4.0 and Client for Server 39.5.0). The new standardized client is able to recognize the correct server and control it accordingly.
• The error treatment of the IronPython code has been improved.

• The problem with the double display of the listbox in the hyperlink dialog window, has been resolved.
• The problem, that in Windows 7 Theme in inactive continuous text fields that contained more text than visible in the window, no scroll bar was displayed, has been resolved.
• Various problems with listboxes in dialog modules (assertions, unhandled exceptions, abprupt closing of the listbox for different actions in listbox modules, e.g. enlargement of columns) have been resolved.
• The problem, that data field headings in structured modules have been moved if no tree structure was activated in one of the child data areas of a data area (if the child data area of a data area with structure had Tree = 0, the first data field of the child data area was not prolonged like that of the structured one), has been resolved.
• The client crash when changing the data field width in a listbox in a dialog module, has been resolved.
• The performance when working with data fields with activated Multi-line parameter have been resolved.
• The following problems with module variants have been resolved:
  • When automatically changing to a module variant upon module start, the wrong name was displayed in the listbox module variant.
  • Although changing a module variant was not permitted by the customizing, the module variant could be changed.

Version C 39.5.3

• If a non-existing path is specified in the CreateExcelExportDocument() IronPython function, an exception of the IOError type is displayed when trying to export to Excel.
• If non-existing data area IDs (DA Python-ID) are used in the CreateExcelExportDocument() IronPython function in the DACsCU_NamesToExport parameter (exclusively), the None of the DA Python-IDs in DACsCU_NamesToExport exists error message is displayed.

• The problem, that the part string entry did not work correctly for listboxes with grouped data areas, has been resolved
• The problem, that the window separator line was displaced when carrying out particular actions, has been resolved.
• The problem, that scale lines in utilization diagrams were displayed twice, has been resolved.
• The following error message when using the Windows Classic Theme, has been fixed. Errors in visual style related tasks since no visual style is active at the moment.
• A problem with the alternating shading which caused the Evaluation data area in the Project Core Data module to be displayed in gray (and hence all data fields were on output), has been resolved.
• The problem, that presetting the data areas in the Extended dialog message of the Excel exports with the CreateExcelExportDocument() function was not possible, has been resolved.
• The unhandled Python exception when trying to save an empty macro in an external editor, e.g. Notepad++, has been resolved.

Version C 39.5.2

• The Excel export can be addressed via the IronPython API of the client. This enables, a.o., the preset of all parameters that can be selected via the Excel dialog.
  • For this purpose, the following IronPython functions CreateExcelExportDocument(), GenerateExcelFile(), and ExportToExcelWithDialog() have been implemented.
• Export to Excel
  • The export to Excel can be canceled by clicking on the Cancel (new) button in the progress bar window.
  • When trying to export data amounts that are too big, the following message is displayed: The data amount to be exported is very big, therefore, the export may take some time. Please select either the bulk export or deactivate the "Export Layout" option. Do you want to proceed with the current settings?
• The connection attempt can be canceled by pressing the ESC key.
• The current size and position of the window is maintained upon crash of the server and subsequent reconnect.
• Changes to the zoom can be saved in the Base variant of the module in a module variant or via the save module customizing menu item.

Bug fixes

• Export to Excel
  • The problem with the incorrect export of line breaks in data fields with activated multi line parameter has been resolved for Excel 2010.
    • Due to an error in Excel 2003/2007, the problem in these versions remains.
  • The problem with charts that were deformed or the zoom of which was changed upon export, has been resolved.
  • The problem with the wrong format display of projected currency fields in Excel has been resolved.
  • The problem, that when exporting to Excel 2003 and 2007 the progress bar was also displayed after the export has finished (and could not be closed), has been resolved.
  • The problem with the white font
    • in fields and headings in Excel 2003,
    • in headings in Excel 2007,
    • in headings in Excel 2003, 2007, and 2010 when exporting only one data area,
      • which made it look as if no data had been exported, has been resolved.
• The sporadically occurring problem, that the changed zoom was reset to default after graphical creation of a link, has been resolved.
• The problem, that Disconnected was displayed after a successful reconnect in the title bar, has been resolved.
• The problem, that listboxes were not enlarged when displaying child records via the +/- sign of the tree structure, has been resolved.

Version C 39.5.1

• When exporting to Excel, all settings are saved in the export window as well as in the Extended dialog message until the respective module is closed.

Bug fixes

• Export to Excel
  • When exporting a particular record amount, the set formats (e.g. Currency format) no longer get lost.
  • The problem, that column headings were not exported correctly, has been resolved.
  • The performance when exporting overview modules, has been improved.
  • The sporadically occurring error of white headings in Excel has been resolved.
• The AttributeError: 'module' object has no attribute 'file' error message when clicking on the Open Python macro editing [ALT + E] in the Modules module, has been resolved.
• When graphically creating actual dates (under the scale) via the Editing Graphical editing Actual start/Actual end menu items, the bar is immediately visible, even if only one of the dates is set.

Version C 39.5.0

Features