Requirements - To build a candidate registration process for Acquisita LLP
- Integrate process into www.acquisita.com
What we did We used neatComponents development platform to build the process and focused on 5 key areas to build the feature. They are summarised below: 1. Security Permissions Model
2. Database Structure (Form)
3. Automated email - Event trigger
4. Candidate and team view
5. Search Mechanism (Query By Example - QBE) 1. Security Permissions Model Within the site there is a security model used to control different roles as shown in the table below: | Role | Description | | Site Administrator | Controls site and all administration | | Candidate View | Candidates can login or edit their own Profiles | | Team View | The Acquisita Team can log into the site and review candidate information | 2. Database Structure (Form) Using the 'Forms' feature we added the following database structure: | Field | Type | Candidate View | Internal View | System | | UserID | #Counter | | | x | | RecordID | #Counter | | | x | | Created | Date | | x | x | | Updated | Date | | x | x | | Mobile Tel | Text | x | | | | Photo | Image | x | | | | Rate | Link to reference table | x | | | | Region | Link to reference table | x | | | | Sector | Link to reference table | x | | | | Describe Key Skills | Large Text | x | | | | CV | File | x | | | | Available From | Date | x | | | | Available To | Date | x | | | | Available | Yes/No | x | | | | Prof Indemnity Ref No | Text | x | | | | Prof Indemnity Certificate | File | x | | | | Status | List | x | | | | Partner | List | | x | | | Initial Contact Date | Date | | x | | | Partner Comments | Large Text | | x | | | Action Date | Date | | | | | Action Notes | Large Text | | | | | Action Date | Date | | | | 3. Automated email (Event trigger) When a Candidate enters information into the system an automatic trigger is produced and sends an email to the Acquisita team highlighting when the candidate has registered their details. 4. Candidate and team view When a team member logs into the system, features normally hidden to most users become available: There is a menu tab called 'Team' and the candidates search can be selected. From here the user is able to enter various search criteria to find the candidate. 
5. Search mechanism (Query) The search is constructed through a query. The example shown below is an extract from a query that will show a list of candidates - it is the combination of account information and the candidate's informations entered on-line. 
This query is used as a basis for the search. Within neatComponents there is an option to create a customised Search By Example (SBE) query. The screen shown below is a customised view, highlighting all the customised fields, and what is actually shown in the text editor. 
Tags: | 
