hisapy / adventureworks2008r2.ror Goto Github PK

Create a login mechanism to Employees access the application, based on some of the information stored in HumanResources.Employee and Person.Password.

UI to manage the EmployeePayHistory Entity. As with the other features of this milestone, this feature must be included in the Employee CRUD UI.

This will be an UI to search Employees based on its basic information (all fields in Employee, Person, Email, etc).
The UI will be a form like search widget where the user should be able to add or remove fields as needed. For example, the user can search Employees based on their names, their email, their sex, etc.

Everything related to managing Department information.

Department search mechanism to search by name or by group name.

This feature must be integrated in the Employee CRUD UI. It should include all the tasks related to managing the relation between employees and department, even viewing a EmployeeDepartmentHistory and its corresponding Shifts

In this UI the user will be able to search Employees based on information other information related to them such as department, shift, sales related information (if Employee is a SalesPerson), and Pay history, etc.

This feature will also include operators such as > (greater than) or < (less than) for numeric or date fields. For example, if the user wants to find the SalesPerson with a SalesYTD higher than 250000.

The AdventureWorks2008R2 has some sort of built-in documentation through the use of Extended Properties. The extended property used to describe the fields, tables and other database object is the MS_Description.

This feature must implement some sort of mechanism to display the MS_Description possibly responding to a mouse over event or by switching on/off a "display inline help" button.

Ruby on Rails outputs all records of a given query by default. This feature will add a pagination mechanism that will be used in every list. By default the pagination should include no more than 10 records, but the user should be able to modify this value and this setting should be stored in a cookie in the user's web browser.

Make the lists sortable by clicking on one of its columns. For example, in a employees list, if the user clicks on the FirstName column, all records should be sorted by FirstName. This mechanism will be used in every list in the application.

Everything related to creating/updating/deleting an Employee (including a Sales.SalesPerson). Take into account that the HumanResources.Employee gets its basic information from Person schema tables.