Page copy can lead to an accidental deletion of AWM

In order to start a new App Within Minutes, a user may think that copying an existing AWM could help (for example, there could be a couple of fields that the user wants to re-use in its new AWM).

Currently, we don't support copying AWMs (XWIKI-19234) : copying the home page of an AWM with its children will not do anything particular compared to the standard page copy behavior. Thus, when a user copies an AWM, the new AWM, even though it comes with a code space, with a class, a sheet, etc, … the AWM itself is not configured to use the aforementioned components.

If the user finds out that its new AWM is not behaving as expected (for example, if the user sees that new entries in the AWM are shown on the home page of the two AWMs), it may want to delete the freshly copied AWM, by using the "Delete application" button on the home page. This action will delete :

• The code space of the copied AWM
• The home of the copied AWM
• The code space of the first AWM
• Any page created with the class defined by the first AWM

These two last elements can confuse the user even more.

Preventing such issue can be difficult, and we may need to implement XWIKI-19234 to consider this fixed.