New Features and Other Improvements
Clausion ESEF Reporting Tool: Possibility to define report package folder and iXBRL report file name
Feature ID: FD-79
The default report package zip file name pattern for a final official report is now "%LEI CODE%‑%EXTENSION DATE%_%LANG CODE%" which could end up in a report package zip file name "743700YEFL7CIOGVEV73‑2021‑12‑31_fi.zip". Earlier the default pattern was "%EXTENSION PREFIX%‑%EXTENSION DATE%". The pattern can be reset with the new literal /**FinalReportFolderName.
The default pattern for a viewer report is now "viewer_%EXTENSION PREFIX%‑%EXTENSION DATE%_%LANG CODE%". The report package zip file could then be named "viewer_dg_2021‑12‑31_fi.zip". It is thus clearly distinguishable from the official report. The pattern can be reset with the /**ViewerReportFolderName literal. Both literals have certain variables which can be used in them. These variables are: %EXTENSION DATE%, %EXTENSION PREFIX%, %LANG CODE%, %LEI CODE%, and %PUBLISHER PATHSAFE%.
Clausion FPM Web Client: Enabling iframe in other application tasks
Feature ID: FD-54
Iframe has been enabled in Clausion FPM Web Client. Now the user can see the content of the URL within FPM Web Client in the right-side pane while the FPM navigation remains on the left.
An external application task opens within FPM Web Client, when admin changes the task settings by giving value "Parent" to the parameter "targetscreen". In FPM Desktop Client this value has no meaning, i.e. the external application always opens outside FPM, in the browser or other application associated with the linked file type.
Clausion ESEF Reporting Tool support for Transformation Registry 4
Feature ID: FD-33
Clausion ESEF Reporting Tool now uses the latest transformation registry version 4 when it creates the XHTML report files. This means that it is now possible to report a zero for numeric facts with any non‑numeric text such as "‑". All tagged values for a numeric fact which do not contain digits are considered to be zero.
There is also more flexibility in choosing a presentation format for tagged dates (ItemType: Date) such as for element "Date of end of reporting period". A date fact can be presented in a localized date format on an entry sheet, such as "30. kesäk. 2020", "30 juni 2020" or even "30 юни 2020". Dates have 84 different formats which can be found from the transformation registry 4, but the easiest way to report a date is to write it in the desired format on an entry sheet, tag it normally leaving the UnitRef column empty, and running the Report Package. The application will then suggest all the possible transformations for the fact. The most specific must always be chosen. Furthermore, the possibility to choose the used transformation registry has now been taken off so the literal /**TransformationRegistryNS is deprecated.