We need to do a lot more on each table - 1. All tables are sorted by default by the Request ID and are in Open state. 2. All columns can be used to sort the data 3. All columns that show enumerations have to show those options and another “All” option so that user can set any option he wants. 4. We will have another column “Status” that shows the status of the request. By default this is set to “Open” and each table shows only Open status requests only. 5. When a request is in Open state, the Closed Date field will have an empty value.
We need search feature on each table too. When user enters any string, we should search all columns for that string, specifically, sorting the rows based on the best matches in the Subject column of the table.
Need to have pagination for our tables. Maximum 10 rows are shown at a time. We should also show the total number of rows as well. E.g. Showing 10-20 rows of 300 rows at the bottom of the table. User can move up or down using Left and Right side arrow indicators.
We need to do a lot more on each table - 1. All tables are sorted by default by the Request ID and are in Open state. 2. All columns can be used to sort the data 3. All columns that show enumerations have to show those options and another “All” option so that user can set any option he wants. 4. We will have another column “Status” that shows the status of the request. By default this is set to “Open” and each table shows only Open status requests only. 5. When a request is in Open state, the Closed Date field will have an empty value.
We need search feature on each table too. When user enters any string, we should search all columns for that string, specifically, sorting the rows based on the best matches in the Subject column of the table.
Need to have pagination for our tables. Maximum 10 rows are shown at a time. We should also show the total number of rows as well. E.g. Showing 10-20 rows of 300 rows at the bottom of the table. User can move up or down using Left and Right side arrow indicators.