As an App Adm, I want to delete a custom object, so that I can remove obsolete customized objects and keep my Apps database clean
Objects are the main entity of the App Builder. In this first version of the product, we are proposing a feature that allow user to create CRUD applications. That being said, each object will represent a new App that will be able to insert new entries, see the listing, delete and view existing entries.
The purpose of custom objects is to allow the user to represent his business needs that aren't supported by Liferay's native objects. This way, if some kind of entity is needed, but not already in Liferay (e.g. Product Orders, Quotes, Vacation Request, etc.), he can create a custom object, gather and centralize the information in his app using different forms and tables.
In this Story, we aim to allow the user to delete existing custom objects.
- Given an existing custom object has no entries, active publishings or being used as a Lookup, when a user try to delete the object, then the custom object should be removed from the Liferay instance;
- Given an existing custom object, when a user try to delete the object, then the system should ask the user for a confirmation before proceeding with the deletion.
All Acceptance Criteria were passed;
Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
Verify if the test labels were added;
Code with peer review completed;
Validated by QA, Product Designer and/or PM;
No critical bug related to Story scope (ex.: similar of FP4, FP5);
Make sure that all system documentation were updated (if necessary)