Change History for fusion_place 12.2.x
12.2.0-S130
2024-01-22
The following are the changes in this release (12.1.0 → 12.2.0).
New Features and Improvements
Adding Loop Rows with a Single Action
(@sugimoto-kei, @KimuraMayumi, #552)
You can now add loop rows in the form screen with a mouse click.
Member Property “Data Type/#DATA_TYPE”
(@sugimoto-kei, @chaip-taka, @miwako-takemoto, #575, #596)
The member property Data Type/#DATA_TYPE has been introduced for general dimensions. The selectable data type values are as follows:
-
Dependent on Accounts or Note Item /ACCOUNT
-
None /NONE
With Data Type/#DATA_TYPE, it is now possible to create members within each dimension solely for grouping purposes.
By setting the data type of a given member to “None,” it becomes permissible to have duplicate members between member trees when multiple member trees are registered under that member.
Replacing reload4j with SLF4J and logback
(@77web, @iteman, @chaip-taka, @miwako-takemoto, #537)
Log output using reload4j (a vulnerability-patched package of log4j 1.2.17) has been replaced by SLF4J and logback.
With this replacement, the log configuration files on both the server and client sides have changed from log4j.properties to logback.xml.
Additionally, the output destination for H2 database logs has changed from fusionplace.trace.db in the same directory as the previous database to fusionplace-stdout.YYYY-MM-DD.log in the Tomcat log directory.
Along with this, the file name for server log files from previous days has changed from fusionplace.log.YYYY-MM-DD to fusionplace.YYYY-MM-DD.log.
For details, please refer to Viewing Log Files.
|
In relation to the above, there are also changes to the connection URLs in the Tomcat configuration file |
Other Improvements
In addition to the above, the following new features and improvements are included:
-
Security enhancements via HTTP headers (@77web, #566)
-
Improved “Update Method” content for ledger update history in scripting and Web-API import processing (@sugimoto-kei)
-
Expanded support for Ledger Edition objects (@sugimoto-kei, @chaip-taka, #636)
Defect Fixes
The following defects have been fixed:
-
[Manager] Cannot specify fiscal year as a filtering criterion for ledger update history. (@sugimoto-kei, @chaip-taka, #584)
-
[Browser] [Contributor] When entering values exceeding the maximum in forms, they are converted to strange numbers and can be saved as-is. (@sugimoto-kei, @KimuraMayumi, #491)
-
Parameters in script execution error messages are not replaced. (@iteman, #642)
-
[Contributor] When saving package input data, parameter values from the source form are not used. (@iteman, @takayuki-ohashi, #637)
-
After referencing a large amount of ledger edition update history, subsequent processing times out. (@sugimoto-kei, @chaip-taka, #625)
Client Component Update Information
The following table shows the versions of client software components included in this release and whether they need to be updated due to the fusion_place server update (12.1.0 → 12.2.0).
Component |
Version |
Update Required? (YES/no) |
Remarks |
1.1.1 |
no |
||
12.1.0 |
no |
||
12.2.0 |
no |
