How You Analyze a Requirement

You can break down your requirement under logical information chunks of what, where, when, and the rule criteria to understand your objective. This table helps you to break down your requirement using some common examples of autocomplete rules.

Rule	What	Where	When	Criteria
Add a functional description of the use case	Default or validate fields. For validation, either show an error message or warning message	Specify actions and the section where you want to trigger the rule	When must the rule be triggered - when the user enters a section or page (default), clicks the Continue or Submit buttons (validate), or tabs out of a field (validate or default)	List all the criteria (area and field) to default or validate fields
Working hours must not be less than 40 hours when the employee is a full time employee	Validation - error message	Add Contingent Worker - Employment Add Nonworker - Employment Add Pending Worker - Employment Change Assignment - Employment Hire an Employee - Employment	Continue or Submit button	Employment - Assignment Category= Full time or Part time Employment - Working Hours
During termination, warn a user that selecting some action reasons prevents employees from being rehired	Validation - warning message	Termination - When and Why	Tab out of the Action Reason field	Action Reason Termination Reason
Default Salary Basis based on the job FLSA status	Default	Add Contingent Worker - Salary Add Nonworker - Salary Add Pending Worker - Salary Change Salary - Salary Hire an Employee - Salary	Enter section or page	Compensation - Salary Basis Employment - Job FLSA Status
Default these field values when the user selects job BAA in the Add Contingent Worker flow Assignment Category - Full time, temporary Working Hours - 80 Frequency - Biweekly Hourly Paid or Salaried -Hourly	Default	Add Contingent Worker - Assignment	Tab out of the Job field	Employment - Job Employment - Assignment Category Employment - Working Hours Employment - Frequency Employment - Hourly Paid or Salaried