We've moved the documentation for Apliqo UX & Apliqo FPM to a new, improved space.
To access the updated documentation, please click on the links below:
Splicer should be able to parse properly rule files that contain accented or special characters (all non-ASCII).
Potential Issue
Splicer will fail to parse a rule that contains invalid UTF-8 character sequences and will initiate rollback of changes.
Precautions
Please make sure the rules always contain proper characters supported by UTF-8 format.
#531 - Add test to package pre process verify if SubsetElementExists works properly
Symptoms
Functions HierarchySubsetElementExists and SubsetElementExists do not work properly in certain versions of Planning Analytics and return 0 in all cases despite the element does exist in the subset. This issue renders such Planning Analytics versions not compatible with Apliqo FPM.
Incompatible version found: 2.0.9.5 (11.8.00400.7)
Solution
Functional test was added to package pre process to make sure both functions work properly.
Please note: The package pre process will fail further update processing in case the functions don't work as expected. In this case, please update your Planning Analytics.
#508 - Check performance of }APQ.C3.CoAMap.Import.Cube process
Symptom
The execution time of }APQ.C3.CoAMap.Import.Cube is significantly higher by observation from testing of issue #419. The cause needs to be identified.
Solution
Attribute mirroring for alias Code and Description is causing performance degradation which may increase processing time by 200%.
Below table shows example of run time comparison when rules in }ElementAttributes_FIN CoA Map and }LocalizedElementAttributes_FIN CoA Map are enabled and Code and Description is alias, second row shows runtime with both disabled, Code and Description still being alias, third case when alias is changed to string with rules in place.
Pre package script makes sure Code and Description type is String and not Alias.
0 Comments
Add your comment