Page content
...
| Field Sequence | Field name | Reference Table | Current FE Validation & Rules | List Page?(Y/N) | List Page Rules (Sort/Filter) | Proposed FE Validation Rules | Proposed BE Validation / Rules | Error Messages | Notes | Delete (Y/N) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
National Post Number
| ||||||||||||||||||||||||||
| 1 | Suffix | See: TIS UI Fields - Dropdowns |
| N | Enabled NPN manual edit
Auto-generation NPN
| Enabled NPN manual edit
Auto-generation NPN
| Warning: Suffix cannot be amended for autogenerated NPN This field is required | Can Suffix be amended (changed, added, or removed) in an autogenerated NPN after it's been created? | ||||||||||||||||||
| 2 | Enable/d NPN manually editing |
| N |
|
| Warning: If "No" selected, the NPN cannot be edited | ||||||||||||||||||||
| 3 | National post number | 'Enable/d NPN manually editing' No
'Enable/d NPN manually editing' Yes
| Y | Sort
| Enabled NPN manual edit
Autogeneration
| Enabled NPN manual edit
Autogeneration
| This field is required Only special characters allowed are / | The error message should only be displayed where "Enable/d NPN manually editing" = Yes | ||||||||||||||||||
Allocation
| ||||||||||||||||||||||||||
| 4 | Main site | See: TIS UI Fields - Dropdowns |
| Y (Primary Site) | Filter |
|
| This field is required | ||||||||||||||||||
| 5 | Other sites (optional) | See: TIS UI Fields - Dropdowns |
| N |
|
| Users should be able to add multiple fields individually, or add all fields from the drop down | |||||||||||||||||||
| 6 | Main specialty | See: TIS UI Fields - Dropdowns |
| Y (Primary Specialty | Filter |
|
| This field is required | ||||||||||||||||||
| 7 | Other specialities | See: TIS UI Fields - Dropdowns |
| N |
|
| Users should be able to add multiple fields individually, or add all fields from the drop down | |||||||||||||||||||
| 8 | Sub specialities | See: TIS UI Fields - Dropdowns |
| N |
|
| Warning: only sub-specialties o the Main specialty can be selected | Investigate whether multiple sub-specialties is required (Data Leads) | ||||||||||||||||||
| 9 | Approved grade | See: TIS UI Fields - Dropdowns |
| Y | Filter |
|
| This field is required Warning: only Post grades can be selected | ||||||||||||||||||
| 10 | Other grades | See: TIS UI Fields - Dropdowns |
| N |
|
| Warning: only Post grades can be selected | |||||||||||||||||||
Ownership
| ||||||||||||||||||||||||||
| 11 | Owner | See: TIS UI Fields - Dropdowns |
| Y | Filter |
|
| This field is required | ||||||||||||||||||
| 12 | Employing body | See: TIS UI Fields - Dropdowns |
| N |
|
| This field is required | |||||||||||||||||||
| 13 | Training body | See: TIS UI Fields - Dropdowns |
| N |
|
| This field is required | |||||||||||||||||||
| 14 | Programme name | See: TIS UI Fields - Dropdowns |
| Y | Filter |
|
| This field is required | ||||||||||||||||||
| 15 | Training description |
| N |
|
| Only special characters allowed: forward slash ( / ), apostrophes ( ' ), hypens ( - ), full stops ( . ) and spaces ( ) | ||||||||||||||||||||
| 18 | Status | See: TIS UI Fields - Dropdowns |
| Y | Filter |
|
| This field is required | ||||||||||||||||||
| 19 | Old post |
| N |
|
| |||||||||||||||||||||
| 20 | New post |
| N |
|
| |||||||||||||||||||||
| 21 | Post family |
| N |
|
| JW to discuss with SMEs | ||||||||||||||||||||
| 22 | Local post number |
| N |
|
| |||||||||||||||||||||
Funding (Needs to be discussed with SMEs - particularly EM & LASE)
| ||||||||||||||||||||||||||
| 23 | Funding type | See: TIS UI Fields - Dropdowns |
| Y | Filter |
|
| This field is required | ||||||||||||||||||
| 24 | If 'Other', please specify |
| N | If Funding type is "Other"
If Funding type is not "Other"
| If Funding type is "Other"
If Funding type is not "Other"
| Only special characters allowed: forward slash ( / ), apostrophes ( ' ), hypens ( - ), full stops ( . ) and spaces ( ) | ||||||||||||||||||||
| 25 | Funding body / organisation | See: TIS UI Fields - Dropdowns |
| N |
|
| This field is required | Should be pulling from "Funding Organisation table" | ||||||||||||||||||
| 26 | Start date |
| N | If Funding type is "No value provided"
If Funding type is not "No value provided"
|
| This field is required Only special characters allowed / | ||||||||||||||||||||
| 27 | End date |
| N | If Funding type is "No value provided"
If Funding type is not "No value provided"
| If Funding type is "No value provided"
If Funding type is not "No value provided"
| This field is required Only special characters allowed / | ||||||||||||||||||||
Rotation
| ||||||||||||||||||||||||||
| 29 | Rotation name |
| N |
|
| Warning: Only rotations from within the same programme as the post can be selected | ||||||||||||||||||||
History (Table)
| ||||||||||||||||||||||||||
| 30 | Trainee full name |
| Y (Current Trainee) | Sort Max 1 current trainee displayed in list page |
|
| ||||||||||||||||||||
| 31 | Start date |
| N |
|
| |||||||||||||||||||||
| 32 | End date |
| N |
|
| |||||||||||||||||||||
| 33 | Main site |
| N |
|
| |||||||||||||||||||||
| 34 | Main specialty |
| N |
|
| |||||||||||||||||||||
| 35 | Placement grade |
| N |
|
| |||||||||||||||||||||
| 36 | Placement type |
| N |
|
| |||||||||||||||||||||
| 37 | Status |
| N |
|
| |||||||||||||||||||||
...
| # | Column heading | Add/Update/Matching Criteria | Mandatory | Rules | Questions for discussions | MVP (Y/N) |
|---|---|---|---|---|---|---|
| 1 | National Post Number* | Add | Y | Should be a Post that does not already exist on TIS. | Do we need this to be auto generated as in the UI? If so, there are some fields that are mandatory and it will also need the addition of the Suffix as a column.
| |
| 2 | Approved grade* | Add | Y | Accepted values should match to one of the Grade reference table and are CURRENT | ||
| 3 | Other grades | Add | N |
| ||
| 4 | Specialty* | Add | Accepted values should match to one of the Specialty reference table and are CURRENT | |||
| 5 | Other specialties | Add | N |
| ||
| 6 | Sub specialties | Add | N |
| Should this be constrained to specialty type SUB_SPECIALTY? | |
| 7 | Training description | Add | Freetext | |||
| 8 | Main site* | Add | Y | Accepted values should match to one of the SiteKnownAs from Site reference table and are CURRENT | ||
| 9 | Other sites | Add | N |
| ||
| 10 | Training body | Add | N | Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT | ||
| 11 | Employing body | Add | N | Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT | ||
| 12 | Programme name* | Add | Y | Programme Name and Number should both match to one of the existing programmes on TIS and are CURRENT. | This is not currently mandatory on the UI. This may be because of the data inherited from Intrepid migration which would mean that if this was made mandatory then the whole post record would be made un-editable where there are empty Programme name and number on Posts records. However, this does need to be mandatory for the Placement Planning Tool to return the Post from the Programme view. This requires some work for the data leads to correct the posts with no programme name & number to avoid Programmes from being created as such going forward. | |
| 13 | Programme number* | Add | Y | Programme Name and Number should both match to one of the existing programmes on TIS and are CURRENT. | This is not currently mandatory on the UI. This may be because of the data inherited from Intrepid migration which would mean that if this was made mandatory then the whole post record would be made un-editable where there are empty Programme name and number on Posts records. However, this does need to be mandatory for the Placement Planning Tool to return the post from the Programme view. This requires some work for the data leads to correct the posts with no programme name & number to avoid Programmes from being created as such going forward. | |
| 14 | Owner* | Add | Y | Accepted values should match to one of Local Office reference table and are CURRENT. | ||
| Old post | Is this required in a bulk create scenario? | |||||
| New post | Is this required in a bulk create scenario? | |||||
| Local post number | Is this required in a bulk create scenario? | |||||
| Post family | Is this required in a bulk create scenario? | |||||
...
| # | Question | Comments |
|---|---|---|
| 1 | Should you be able to add Post fundings as part of the Post upload or should be separate? | |
| 2 | Will the post funding information be available at the time of creating the posts? | |
| 3 | What are the MVP fields for a Post Import template? | |
| 34 | Should the MVP be to use the template to only create new Posts and consider update as a post-MVP future increment or the other way round? | |