## Contact Form Submission – Website & Admin Requirements ### Website Implement the Contact Form submission functionality with the following requirements: 1. When a user submits the contact form, the submitted data should be saved to the corresponding database table. 2. After successful submission: * Display a confirmation/success message to the user. * Provide a **"Send Another Message"** button that resets the form and allows the user to submit a new message. ### Admin Panel Create a Contact Messages management section in the Admin Panel with the following functionality: #### Message Listing 1. Display all received messages in a grid/list view. 2. Show messages in **descending order of Received Date** by default (newest first). 3. Enable sorting on all columns. 4. Include a **Select All** checkbox to allow bulk selection of messages. #### Message Details 1. Provide an option to view the full message content. 2. The message details can be displayed in a popup/modal or a dedicated detail view page. #### Audit Fields 1. Since contact form submissions originate from the public website, the **Created By** and **Updated By** fields should not be set to "Super Admin". 2. Use a generic value such as **"Website User"**, **"Website Submission"**, or another appropriate identifier to clearly indicate that the record was created from the website rather than the admin portal. #### Delete Functionality 1. Add a **Delete** option in: * The message list view. * The message detail view. 2. Implement **soft delete** functionality in the database (records should not be permanently removed). 3. Support bulk deletion of selected messages using the **Select All** functionality. ### Default Behavior * Default sorting: **Received Date (Descending)**. * All columns should support ascending and descending sorting. * Deleted records should follow the application's existing soft-delete conventions.
Similar category and model suggestions.