Fork and merge: Milestone explorer - handle document addition/deletion - Backend
SUMMARY
Follow-up for #1675
When working on a clone proposal, the users are free to modify all the cloned documents, and these changes are tracked in track changes, but they are also allowed to ADD/REMOVE documents such as Annexes of LFS. In this case, when the cloned is consolidated, there needs to be a way for the receiving end (Lead DG) to consult such document level changes and act upon them.
In Legacy Vaadin version of LEOS, this functionality was covered according to the following documentation : https://citnet.tech.ec.europa.eu/CITnet/confluence/pages/viewpage.action?pageId=1148028673
ACCEPTANCE CRITERIAS / GOALS
Implement support for all BACKEND layer support for the UI changes done in #1675:
- Add backend logic support for Accept document addition
- Add backend logic support for Reject document addition
NOTE: For both services, the functionality already existed in old Vaadin version. This will need to be exposed through a REST API and adapted to integrate with new Angular UI