List of fixed issues
1. All machines
- Tests with the solid conductors in slots - Current in parallel paths
                        is wrongWhile computing a working point with elementary wires modeled with solid conductors, the computed electrical current in the branches in parallel is wrong, if the following conditions are met (ref.: FXM-14728):- There are parallel paths,
- The “Accurate mode” of computation is selected
- The “AC losses analysis” in “One” or “All phases” are selected
- The resulting finite element model doesn’t represent the full geometry
 This issue has been corrected. 
- Inner slots with 2 layers winding and a liner can be
                        infeasibleSometimes, while adding a liner in an inner slot inside of which there are 2 layers can fail (ref.: FXM-14100). This issue has been corrected. 
- Issue with report generationSometimes, the report generation freezes This is mainly due to the management of memory. An increase in the allocated memory for Motor Factory can solve the problem (ref.: FXM-13585). This issue has been corrected. 
- Save motor doesn’t workSometimes, saving a motor doesn’t work. This is mainly due to the management of memory. Increasing the allocated memory for Motor Factory can solve the problem (ref.: FXM-13584). This issue has been corrected. 
- Building and export of a report failedWhile adding multiple new tests, and simultaneously executing the previously saved tests (12) along with assigning material in the report and saved test (12), the building and the export of the resulting report can fail (ref.: FXM-11574) + (ref.: FXM-14117). These issues have been corrected. 
2. Synchronous machines – Motor Factory – Test environment
- Duty cycle with many working points failsRunning a computation of a duty cycle with many working points via scripting crashes (ref.: FXM-14435). This issue has been corrected. 
- FMU LUT data Export: Flux_D and Flux_Q are
                        incorrectThe flux linkage related to the end winding inductances on FMU side is not considered, as it is done on the test map side (ref.: FXM-14041). This issue has been corrected.