Skip to main content

Clausion 25.09 Release Notes

Introduction

This document includes information about the new features, other improvements, and corrected known issues implemented in the Clausion 25.09.

New Features and Other Improvements

Web Client: Audit Trail Feature

Feature ID: FD-10664

The new Audit Trail functionality in Web Client allows you to view the complete history of changes made to specific data points in your financial reports.

You can access audit trail by right-clicking on any data cell in input sheets. The audit trail option is only enabled for data columns and is disabled for definition columns, customized sheets, report sheets, and card sheets. When you click on Audit Trail, a new tab opens showing the complete change history for that specific cell.

Audit trail view in web client

Note: You need to enable history for DATAMAIN tables to see previous transactions on the audit trail screen.

The audit trail screen includes Print, Save to File, and Add Columns buttons with tooltips. You can view data in a grid format with breadcrumb navigation showing the selected account, period, and year. Search functionality is available for filtering data within grid columns, with a Clear button to remove search criteria. The screen supports both horizontal and vertical scrollbars for easy navigation.

When you open the audit trail screen, the following columns are displayed by default: Account ID, DIM00, CODIM00, Input Type, Position, Unit Amount N, Group Amount N, Comment, Updated On, Updated By, Update Method, and Template Name.

You can print grid data through a popup window or automatically export data to Excel using the Save to File button. Column management is available through the Add Columns button, which shows a checkbox list for selecting visible columns. The default pagination shows 250 rows per page, which you can change to 500 or 1000 rows. Sorting is available on all audit trail columns, with default sorting applied to the "Updated On" column.

You can see the template name (document name) in the DATAMAIN table after saving data in input and report sheets from both desktop and Web Client. This works for both manual and calculated entries.

Note: Audit trail functionality is available for all Web Client users but is not available on desktop client or for sum accounts where data is aggregated rather than stored directly in DATAMAIN tables.

Audit Trail Management Screen

Feature ID: FD-17856

As an administrator, you can now take into use a dedicated Audit Trail Management screen by adding the AuditTrailMnt task ID in your user interface. This feature provides advanced filtering and reporting capabilities for audit trail data.

Two new components are available in the user interface: Users and Date Range Filter. You can use these components specifically for the Audit Trail Management screen. If these components are added to other task IDs, they will not appear on the Web Client.

To use the Date Range Filter, change the start date by double-clicking on the end date and then select your desired start date. For dimension components, selecting a parent unit automatically fetches data for all child units without requiring individual selection.

The Date Range Filter component remains visible and enabled even if set to false in the user interface, as date selection is essential for audit trail functionality. By default, the Date Range Filter shows one week's worth of dates with future dates disabled.

Audit trail selections view

The Audit Trail view includes Print, Save to File, Add Columns, and Selections buttons at the top, with a report grid below displaying data from the DATAMAIN history table. You can access components by clicking the Selections button, which opens a panel with Cancel and Apply options.

You can use multiple selection functionality for Periods, Users, Dimensions, Accounts, and Document Series components.

The selections panel appears as an overlay over the report grid to improve performance when handling large datasets. You can close the panel by clicking the Selections, Cancel, or Apply buttons. The panel retains your selections when you apply filters and resets to user interface defaults when you refresh the screen.

The screen supports pagination with a default of 250 rows per page, configurable to 500 or 1000 rows (maximum limit). You can apply sorting on audit trail columns by clicking column headers. If no data matches your selections, a "No results matching your search" message appears.

AI-Powered Dimension Extra Field Filtering

Feature ID: FD-23165

You can now filter report data using natural language prompts that target dimension extra fields. This AI-powered feature converts your plain language requests into machine-understandable filters, making data filtering more intuitive and accessible.

You can type prompts in your selected language to filter data based on dimension extra fields. For example, you can enter "Filter data by DIM00 extra field Region, value is equal to Europe" and the AI will automatically apply the appropriate filter when you click the Open button.

When you enter your prompt and click Open to open the report, the system automatically applies the filter to your report data, showing only the results that match your specified criteria. The filtered results display the same data you would see if you had applied the equivalent filter through the desktop client interface.

How It Works

The system utilizes AI to interpret your natural language input and convert it into the appropriate filter parameters. This eliminates the need to navigate complex filter menus while providing the same powerful filtering capabilities available in the desktop client.

Note: This feature is available exclusively for Clausion Platform users as it utilizes ISW AI APIs that require Platform configuration.

Corrected Known Issues

Issue ID

Issue

Resolution

FD-25593

Dynamic Reporting: If DRData formula has brackets and the minus sign, it does not work

You can now use DRData formula with brackets and minus

FD-24890

If the conversion table for counter unit uses only the parent level as its source, Internal Data Transfer (IDT) functions erroneously

You can now successfully transfer data when dimension and counter-dimension conversion rules are defined at parent levels without encountering false validation errors

Was this article helpful?

We're sorry to hear that.