| Neue Möglichkeiten |
|---|
| 1. | The new property, ParameterAlignment, has been added to the report.V2024.2.1 |
| 2. | New functions were added: IsAllDataRowNullOrEmpty, IsDataEmpty, IsNumeric, IsNullOrEmpty and IsNullOrWhiteSpace.V2024.2.1RBlazorRAngular |
| 3. | Disable hot keys in the Web report designer using the "EnableShortCutKeys" option.V2024.2.1RBlazor |
| 4. | Support for the .NET 8.0 framework in NuGet packages for all our products has been added.V2024.2.1RBlazorRAngular |
| 5. | The new static option StiOptions.Engine.NullDataSortMode. By default it is set to StiNullDataSortMode.NullFirst.V2024.2.5 |
| 6. | A new MergeDocument method has been added to the report for combining rendered reports.V2024.2.5 |
| 7. | New events OnDesignerBeforeRender and OnViewerBeforeRender have been introduced to load fonts and set necessary options before rendering a component on an HTML page.V2024.2.5RBlazor |
| Verbesserungen |
|---|
| 1. | The loading indicator behavior for the designer in Blazor Server and Blazor Wasm has been improved.V2024.2.5RBlazor |
| 2. | Collections of colors for HeatMaps with grouping in predefined dashboard styles.V2024.2.6 |
| 3. | The export format value "Excel2007" has been replaced by the universal Excel value. So now, you need to use the following line of code to export a report to Microsoft Excel format: report.ExportDocument(StiExportFormat.Excel, file);. If you need to obtain the old binary format of Excel, you should use the new value - ExcelBiff.V2024.2.1 |
| 4. | The export format value "Word2007" has been replaced by the "Word" value. So now, you need to use the following line of code to export a report to Microsoft Word format: report.ExportDocument(StiExportFormat.Word, file);.V2024.2.1 |
| 5. | Removed support for the outdated .NET 5.0 framework for BLAZOR products.V2024.2.1RBlazor |
| 6. | The .NET Standard 2.1 specification used has been replaced with the minimum .NET Core 3.1 framework required to compile our products.V2024.2.1 |
| 7. | The loading speed of the Designer and Viewer for Blazor WebAssembly has been significantly optimized.V2024.2.4RBlazor |
| 8. | Editors and menus in the Web designer have been optimized for small screen resolutions.V2024.2.3 |
| 9. | The export format value "Ppt2007" has been replaced by the "PowerPoint" value. So now, you need to use the following line of code to export a report to the Microsoft PowerPoint format: report.ExportDocument(StiExportFormat.PowerPoint, file);.V2024.2.1RAngular |
| Behobene Fehler |
|---|
| 1. | Export to Word. The transparent background of icons (Image.Icon) was exported incorrectly.V2024.2.5RAngular |
| 2. | The availability behavior of the "Editor" command when viewing reports has been adjusted when the "Request Parameters" property is set to "True".V2024.2.3 |
| 3. | Positioning controls in Web designer editors for the Safar webi browser.V2024.2.3RBlazor |
| 4. | Reset the display of components on the Insert tab in the cookies (for every new build version).V2024.2.3RBlazor |
| 5. | Positioning of the selection cursor in the report designer.V2024.2.3 |
| 6. | Exporting a report to Image from the Firefox web browser, if the "Compress To Archive" option is enabled.V2024.2.3 |
| 7. | Displaying a notification about an incorrect password on the "Account" tab in the report designer.V2024.2.4 |
| 8. | Using the Content-Type" = "application/x-www-form-urlencoded" header in the OData data source to get the Bearer.V2024.2.4 |
| 9. | Work of the DateTimeStep property for axes in report charts.V2024.2.4 |
| 10. | The problem with null values for variables in the viewer has been fixed.V2024.2.5 |
| 11. | Export to PDF. An exception occurred if the graphics library could not load the image from binary data (unsupported format or incorrect data).V2024.2.5 |
| 12. | Vertical scrolling of the list of elements in the constant line editor.V2024.2.3 |
| 13. | Export to HTML. There was a problem with displaying some images in Outlook.V2024.2.5 |
| 14. | HTML tags. Incorrect alignment of the text by width if the list element contains several lines of text.V2024.2.5 |
| 15. | A bug related to the "Prompt User Name and Password" property in the PostgreConnection.V2024.2.5 |
| 16. | Compatibility of the Web viewer component with IE mode (es5).V2024.2.6 |
| 17. | Handle negative values for the "Area -> X Axis -> Labels -> Step" chart property.V2024.2.6 |
| 18. | Formatting time in the DateTime variable editor.V2024.2.2 |
| 19. | Timeout of StringCache session.V2024.2.1 |
| 20. | Displaying selected components when overlapping them.V2024.2.1 |
| 21. | The error occured when drilling down into the data in the dashboard and applying parameters to filter it.V2024.2.1 |
| 22. | Calculate auto width for columns in the "Table" component.V2024.2.1 |
| 23. | Style of the pinned panels "Data Dictionary", "Properties Panel", "Report Tree" in the report designer.V2024.2.1 |
| 24. | Processing names of data columns that contain spaces when creating a dashboard with this data column.V2024.2.2 |
| 25. | Applying the StiOptions.Engine.defaultValueOfAllowApplyStyleProperty parameter to all chart properties.V2024.2.3 |
| 26. | The error with long resource URL.V2024.2.2 |
| 27. | Displaying zero and null values in charts when saving the generated report to *.mdc.V2024.2.2 |
| 28. | Loading a line style for a "3D Line" type chart when opening a generated report from *.mdc with JSON markup.V2024.2.2 |
| 29. | The RequestVerificationToken value for the GetScriptsResult() action in the NetCoreViewer and NetCoreDesigner components was not considered.V2024.2.3RAngular |
| 30. | List of properties for a barcode of the QR code type.V2024.2.3 |
| 31. | Calculation of field sizes in the electronic signature editor with a large value.V2024.2.3 |
