Start a conversation

Corporater BMP - - Release Notes

New and Changed Functionality

Reporter: New Report generation queue has been introduced in order to improve performance and prevent requesting too many reports simultaneously from exhausting system resources. Reports will be queued and are given priority depending on from where they are started. Please contact Corporater Support for more information.

Workflow: New functionality

Action group has an optional property for selecting period type, independent of the period context selected on the web.

It is now possible to add a log folder to an Action group. An Action button running a Workflow action group works as expected and no longer gives warning/error.

Running event rules no longer automatically creates a log folder when none is present, so now it is possible to disable logging by removing the log folder from event rules and any action groups.

Error Corrections and Improvements

Several performance improvements, primarily related to generation of reports.

Statuses in maps now display the name of the selected element in the map comfiguration as expected, instead of showing system names. Please note that when a status entry of any type refers to an object in the Template model and the local version of it has an overridden name, the correct name may not be displayed.

Inserting dynamic context tags in a query in a Query table works as expected and no longer causes a Java error.

Filtered lists with comments display the text correctly as “Wrapped ” when that option is selected, and not always as “Full text”. Switching ‘Comment text’ to “Full text” or “Truncated” works as expected. ‘Display in tables’ can now be used on comments to change the appearance of comment text in filtered list.

Chart previews are displayed as expected when twin axis is enabled , and no longer show "No data to show". Charts are also correct in reports.

Reporter: Formatting in Aspose charts is now displayed as expected when previewing. The formatting used in the report template is displayed as expected the report preview.

Reporter: When reporting to Excel, the report uses the column and row sizes as they are defined in the template, and does not automatically resize.

Reports generated using ControlCmd are now working as expected and contain data. The context was previously not set correctly when ControlCmd was used.

Transformer: Dividing by a low, whole number (integer) by 100 or another higher number now gives the correct decimals, instead of only 0.

Transformer: Excel (xlsx) files are now rendering properly when previewed in Transformer.

Transformer: Auditing activated in Control Center no longer prevents some Transformer jobs from running properly. In some cases, when auditing was turned on in Control Center and "Overwrite the previously inserted import (if any)" was NOT checked, the Transformer job never finished and an error could occur.

Transformer: When running a Transformer job, from Web or Configuration Studio, using an incorrect file or sheet, an invalid sheet error is now correctly logged and a failed import message is displayed, instead of a Java error.

Known issues

When upgrading to version 4.3.x, the change that makes Comments normal business objects may affect how Comments are displayed in Filtered Comments and Filtered Lists, and will need a manual configuration change. A configuration that displays Comments from a selected object from Element list may need to be reconfigured, either by selecting the relevant Comment list in the Element list or by marking the Include subelements box.

When upgrading from 4.1.1.x to 4.3.x, some properties may be ordered differently. Considerably more properties are now displayed in Configuration Studio, as a result of Context being available there. Because of this change some properties may be displayed in different order after upgrading to version 4.3.x.

When upgrading from to 4.2.x or 4.3.x, in some cases Property names in ‘Property settings’ need to be changed manually. The names, descriptions and categories of the system properties that were converted to custom properties in version are sometimes not upgraded using the correct language. If this occurs, the property names should be changed manually in ‘Property settings’.

Table views that are linked to a dataset table with many columns on the x-axis may damage a two-column page setup in the web page and cause the page to become very wide. This will be addressed at a later time.


  1. 449 KB
  2. View
  3. Download
Choose files or drag and drop files
Was this article helpful?
  1. Hans Erik Hovland

  2. Posted
  3. Updated