Angular issues : Improve document refresh
SUMMARY
It has been identified a lack in performance on UI side caused by unnecessary repeat calls to refresh the document from server side. The goal is to analyze all the flow, optimize the process and address issues with the document refresh.
TO BE TESTED FOR EC AND CN IN ALL DOCUMENTS
- Edit element and close without saving => check that is possible to edit another element
- Edit element make some changes, and click outside of the editor => Check that is saved and that is possible to edit another element
- Edit element, make some changes, save first, and then close => Check that is saved and that is possible to edit another element
- Check that versions' pane and table of content are updated after saving
- Revert to previous version => check that TOC is updated
TO BE TESTED FOR CN
- Split feature => Editor should be opened on new element (after 4 secs, to be improved by CRI guys)
- Merge feature => elements are merged but editor is not opened
- Test edition on explanatory document
TO BE TESTED FOR EC
- In the financial statement, test checkboxes and the date picker
- Check accept and reject changes inside and outside editor
Edited by Pascal NYSTEN