All of this is tested in the development environment, with Security Established.
Although the directory of the old name (application that has been renamed) disappears, and that of the new one appears (application with the new name), in _app_data the file of the application that has been renamed is preserved and that of the application with the new name.
So that the application with the New Name can be used by the user, it must be synchronized in security and then it will be incorporated into the sec_apps and sec_groups_apps tables, thus being able to grant privileges to the user over this app, but in both sec_apps and sec_groups_apps, also The old app appears (application that has been renamed), with the privileges it had.???
Absurd!, the app no longer exists in the apps directory, it can never be used with that old name.
We continue, when we rename, we mark the option to change it in the menu (at least the menu already has the new name), which menu we will not be able to use until we have synchronized and granted privileges to the user to be able to use it.
Test carried out with the security project, incorporating the grid_customers app into the menu and renaming it to grid_customers_new, using options to change name in the menu and generate apps.
Danilo, thank you for addressing user concerns,
Greetings