Scribd
Upload
72 views2 pages

Case Study: Cao & M: Application UI Topic: Actions and Validations General Instructions For These Exercises

The document outlines 3 case studies for developing application UIs with client-side validations: 1) A business customer registration form that validates required fields are filled and data types/lengths. 2) An upload product form that validates required fields and data types. 3) A helpdesk ticket form that validates required fields, data types, and conditional logic for status and employee assignment. All forms should include a reset button.

Uploaded by

gurpreet2501
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
72 views2 pages

Case Study: Cao & M: Application UI Topic: Actions and Validations General Instructions For These Exercises

The document outlines 3 case studies for developing application UIs with client-side validations: 1) A business customer registration form that validates required fields are filled and data types/lengths. 2) An upload product form that validates required fields and data types. 3) A helpdesk ticket form that validates required fields, data types, and conditional logic for status and employee assignment. All forms should include a reset button.

Uploaded by

gurpreet2501
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Case Study : CAO & M Module : Application UI Topic : Actions and Validations General Instructions for these exercises:

The below exercises may be solved using HTML and Javascript (for some exercises, you might also require to use Paint) Data displayed on a screen will be hardcoded (not fetched from any database) Submitted data will not be stored in any database 1) Business Customer Registration: Use the screen designed earlier for customer registration and incorporate the following: On submitting the page / screen, ensure all mandatory fields have been filled in. Perform other client side validations for fields (customer name cannot be greater than 120 characters, address should have minimum 200 characters, contact number should have exactly 10 digits, Date should be a valid date,email Id should be of valid emailId format) Provide a Reset button to clear all the fields 2) Upload / Add new Product Use the screen designed earlier to upload/add new product and incorporate the following: On submitting the page / screen, ensure all mandatory fields have been filled in. Perform other client side validations for fields (productId should be a number, Product Name cannot be greater than 20 characters, Date should be a valid date, Status (e.g. Active, Inactive) Provide a Reset button to clear all the fields 3) Create Helpdesk Ticket Use the screen designed earlier for creating helpdesk ticket and incorporate the following: On submitting the page / screen, ensure all mandatory fields have been filled in. Perform other client side validations for fields (HelpdeskTicket Summary, Description of the ticket, Customer Id of the customer who raised the ticket can be alphanumeric, Customer name of the customer who raised the ticket cannot be more than 20 characters and no special characters allowed, Date on which the ticket is raised should be a valid date, Priority of the Ticket(High, Medium or Low), Status of the ticket(The status can contain the following

values : OPEN, ASSIGNED, RESOLVED) , Employee Id of the helpdesk employee who is assigned the ticket can be only number) If the status of the ticket is OPEN, then the system should not allow the user to select the employeeId. If the status of the ticket is ASSIGNED, then the UI should allow the user to select the Employee Id of the employee to whom the ticket is assigned. Provide a Reset button to clear all the fields

You might also like