﻿*************************************************************************************
***********	                    VER 2017.01.31                           ************
*************************************************************************************

What’s new in this release?   

-------------
New features:
-------------
-	Enables migration from containers created in VER 2016.10.14 and in 
	VER 2016.04.29 (in case of the latter for these data points that are the same 
	in 2.0.1 and 2.1.0).
-	Update to February release of deactivated validations.

	IMPORTANT: 
-	Different error margins applied by the database-based validations (relative 
	error with tolerance of 0.000001) and XBRL assertions (interval arithmetic) 
	may result in inconsistent evaluations (compared to XBRL validators).
-	Due to the limit of User Objects in Windows (https://goo.gl/rFg5H5) the tool 
	may crash when large forms are rendered or forms are switched (and rendered) 
	too quickly (this may happen also when a user clicks on errors in order to 
	highlight affected cells, especially in larger tables with multiple z-axis 
	dropdowns).
	Technically, the garbage collector does not clean the objects memory fast 
	enough and they reach the limit of 10000 which is the Windows default. 
	To minimize the risk of this to happen the merged views (i.e. views of all 
	closed tables within a template variant) have been disabled. The users are 
	advised to save the data regularly and allow some time between switching 
	the tables or validation error results.
-	In XBRL 1% should be reported as 0.01 not 1. To detect cases where there is 
	probably an issue of this kind in the report, when importing/exporting to 
	XBRL the tool checks if such item is less than 1 and otherwise shows 
	a warning (just for information that such value may be undesired). 
	However some ratios/percent items may normally be > 1 (e.g. SCR ratio) 
	and this check may be confusing.
-	ETL error may occur when import large XRRL files due to RAM limitation. For
	importing large XBRL please ensure at least 16GB of RAM.
-	Ad hoc module includes technical (i.e. starting from TV) and content template
	validations which are not forced by the XBRL 2.1.0 Taxonomy. Please treat
	these errors as warnings only.
-	Data in Excel templates (basic and business) must be in the same local settings
	as the system running the application. For example when data is saved with comma 
	separating the units and decimals but is imported/exported with local/regional 
	setting expecing there a dot, the values may be incorrectly moved between the 
	tool and Excel inputs/outputs and errors may appear.
-	Version 2017.01.31 supports import or basic and business excel templates
	produced with version 2016.10.14 for all templates apart from S.01.02.07.03.
-	Validation rules involving conditional checks on open tables (i.e. BV135, 
	BV137, BV189, BV363, BV364, BV364, BV365, BV366, BV367, BV368, BV369, BV370,
	BV371, BV372, BV373, BV374, BV375, BV376, BV377, EV42, EV43, EV44) are 
	evaluated only when at least one row matching the filered condition is present
	in an open table that a rule concerns.

----------
Bug fixes:
----------
-	Fixes related to bugs identified in the List of known issues:
		- Validations checking patterns for codes are incorrectly implemented;
		- S.01.02.07.03 does not allow for data entry or edition due cell not being
		  displayed in the UI;
		- Value in "Difference" column displaying database validations was 
		  multiplied by 10 in local system settings using comma to separate units
		  and decimals;
		- Data was not possible to be saved in S.19 template;
-	Cells whose row or column code begins with "E" were not highlighed when
	presenting database validation errors.
-	Rules checking consistency of duplicated data points between various templates
	have been fixed when a data point appears in more than one template.

-----------
Known bugs:
-----------
-	Tool may signal violation of the EIOPA.S.2.18.c Filing Rule for metric mi1131 
	appearing in column C0050 of S.02.03.07.02 and C0080 of SPV.03.01.20.02 on XBRL
	instance import when value of @decimals attribute is set to less than '2'. 
	This is due to the fact that this metric is shared with tables for which higher 
	precision is requested. The error shall be ignored for Data Point Signatures:
	-	MET(s2md_met:mi1131)|s2c_dim:EN(s2c_CG:x29)|s2c_dim:UI(*),
	-	MET(s2md_met:mi1131)|s2c_dim:RS(*).
-	Tool does not handle dates later than 31/12/9998;
-	Arelle import/export may be signalling IO errors for files not included in the
	embedded taxonomy package i.e. xbrl.org (mind no www.) and w3c.org;
- 	Arelle running in background even when application was closed (instance document 
	is still being validated);
-	Users are not informed when a row in an open table contains data for key columns 
	only, which would not result in any XBRL facts on output.
-	The tool does not handle well empty strings as typed dimension values on XBRL
	import. The xsi:nil should be used in these cases as requested in the Guidelines
	section of the Filing Rules.


*************************************************************************************
***********	                    VER 2016.10.14                           ************
*************************************************************************************

What’s new in this release?   

-------------
New features:
-------------
-	Support for full Solvency II Reporting DPM and XBRL Taxonomy version 2.1.0.
-	Enables migration from containers created in VER 2016.04.29 (for these data
	points that are the same in 2.0.1 and 2.1.0).


----------
Bug fixes:
----------
-	Fix to export of the Business Excel Template which was repeating rows in open 
	tables when their number was over 1000.
-	Improvements to UI communicates wording and the user manual.
-	Fix to migration (from the previous version) of reports containing '/' in their 
	name or report names being long (and exceeding the Windows limitation of 260 
	characters in the full path).

