Page content
| Table of Contents |
|---|
...
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 |
| 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 |
| Y (Primary Site) | Filter |
|
| This field is required | |||||||||||||||||||||||||||
5 | Other sites (optional) |
| N |
|
| Users should be able to add multiple fields individually, or add all fields from the drop down | ||||||||||||||||||||||||||||
6 | Main specialty |
| Y (Primary Specialty | Filter |
|
| This field is required | |||||||||||||||||||||||||||
7 | Other specialities |
| N |
|
| Users should be able to add multiple fields individually, or add all fields from the drop down | ||||||||||||||||||||||||||||
8 | Sub specialities |
| N |
|
| Warning: only sub-specialties o the Main specialty can be selected | Investigate whether multiple sub-specialties is required (Data Leads) | |||||||||||||||||||||||||||
9 | Approved grade |
| Y | Filter |
|
| This field is required Warning: only Post grades can be selected | |||||||||||||||||||||||||||
10 | Other grades |
| N |
|
| Warning: only Post grades can be selected | ||||||||||||||||||||||||||||
Ownership
| ||||||||||||||||||||||||||||||||||
11 | Owner |
| Y | Filter |
|
| This field is required | |||||||||||||||||||||||||||
12 | Employing body |
| N |
|
| This field is required | ||||||||||||||||||||||||||||
13 | Training body |
| N |
|
| This field is required | ||||||||||||||||||||||||||||
14 | Programme name* |
| Y | Filter |
|
| This field is required | |||||||||||||||||||||||||||
15 | Training description |
| N |
|
| Only special characters allowed: forward slash ( / ), apostrophes ( ' ), hypens ( - ), full stops ( . ) and spaces ( ) | ||||||||||||||||||||||||||||
18 | Status |
| 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 |
| 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 |
| 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 |
|
| |||||||||||||||||||||||||||||
...
Row no. | 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. Should not appear more than once on the same template being uploaded. | 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. 26/11/2019: JamesH - No to auto generation and yes to the below.
| |||||||||
2 | Approved grade* | Add | Y | Accepted values should match to one of the Grade reference table and are CURRENT | Validation in here to match that on the FE | |||||||||
3 | Other grades | Add | N |
| Make clear that it is the grade name not abbreviation | |||||||||
4 | Specialty* | Add | Y | 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? Yes, but only when the PAG has reviewed and validated the current sub_spec list. | |||||||||
7 | Training description | Add | Freetext | |||||||||||
8 | Main site (Known as)* | Add | Y | Accepted values should match to one of the SiteKnownAs from Site reference table and are CURRENT | Check that all 'SiteKnownAs' names have the site code afterwards - JW run report to check | |||||||||
9 | Other sites (Known as) | Add | N |
| ||||||||||
10 | Training body* | Add | Y | Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT | Not currently mandatory on TIS, but need to be made mandatory across the board (BE, FE, Bulk Upload) - Ticket? | |||||||||
11 | Employing body* | Add | Y | Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT | Not currently mandatory on TIS, but need to be made mandatory across the board (BE, FE, Bulk Upload) - Ticket? | |||||||||
12 | Programme name* (Use TIS_Programme_ID* in favour of this) | Add | N | If populated on template, 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 as not all posts will be training posts so therefore not attached to a training programme. However, when using the template, users should be conscious that this does need to be populated for the Placement Planning Tool to return the Post from the Programme view. | Can be made mandatory - what about existing posts? Alice and James (Intrepid/TIS views for data audit will show posts with no programme attached) Not currently mandatory, but need to be made mandatory across the board (BE, FE, Bulk Upload) - Ticket? | ||||||||
13 | Programme number* (Use TIS_Programme_ID* in favour of this) | Add | N | If populated on template, 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 as not all posts will be training posts so therefore not attached to a training progamme. However, when using the template, users should be conscious that this does need to be populated for the Placement Planning Tool to return the Post from the Programme view. | Can be made mandatory - what about existing posts? Alice and James (Intrepid/TIS views for data audit will show posts with no programme attached) Not currently mandatory, but need to be made mandatory across the board (BE, FE, Bulk Upload) - Ticket? | ||||||||
14 | TIS_Programme_ID* | Add | Y |
| Instead of Story to make this field mandatory from all journeys:
| |||||||||
15 | Owner* | Add | Y | Accepted values should match to one of Local Office reference table and are CURRENT. | ||||||||||
16Old post | Funding type* | Add | NY |
| ||||||||||
17 | Funding subtype | Add | N | Accepted values should match to one of Funding Subtype reference values under the verified funding type and are CURRENT. | ||||||||||
18 | Funding type - If 'Other' please specify | Add | N | Free text
| ||||||||||
19 | Funding Body | Add | N |
| ||||||||||
20 | Funding Start Date* | Add | Y | Date format DD/MM/YYYY
| ||||||||||
21 | Funding End Date | Add | N | Date format DD/MM/YYYY | ||||||||||
22 | Old post | Add | N | Accepted values should match to one of existing NPN's held on TIS. | Is this required in a bulk create scenario? Yes |
...
Row no. | Column heading | Add/Update/Matching Criteria | Mandatory | Rules | Questions/Notes for discussions | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | TIS_PostID* | Matching Criteria | Y |
| ||||||||||||||
2 | Approved grade | Update | N |
| ||||||||||||||
3 | Other grades | Update (replace all existing values) | N |
| ||||||||||||||
4 | Specialty | Update | N |
| ||||||||||||||
5 | Other specialties | Update (replace all existing values) | N |
| ||||||||||||||
6 | Sub specialties | Update (replace all existing values) | N |
| Should this be constrained to specialty type SUB_SPECIALTY? Eventually, but only when the PAG has reviewed and validated the current sub_spec list. For MVP accepted values will match to one of the Specialty reference table and are CURRENT | |||||||||||||
7 | Training description | Update | N | Freetext | ||||||||||||||
8 | Main site | Update | N |
| Check that all 'SiteKnownAs' names have the site code afterwards (follow a standard convention) - JW run report to check | |||||||||||||
9 | Other sites | Update (replace all existing values) | N |
| ||||||||||||||
10 | Training body | Update | N |
| ||||||||||||||
11 | Employing body | Update | N |
|
| |||||||||||||
|
|
|
|
|
| |||||||||||||
| ||||||||||||||||||
|
|
|
|
|
| |||||||||||||
12 | TIS_ |
| N |
| 14 | Owner | Update | N |
| 15 | Rotation | Update (replace all existing values) | N | Comma separated to add multiple
|
| 17 | Old Post |
|
16 | Status | Update | N |
| QUESTION: Is it a requirement to bulk update the status of a post e.g. from Current to Inactive? JW - Yes, this is a requirement | |||||||||||||
|
| |||||||||||||||||
12 | TIS_Programme_ID | Update (replace all existing values) | N |
| ||||||||||||||
14 | Owner | Update | N |
| 18 | Funding type | Add | N |
| |||||||||
15 | Rotation | Update (replace all existing values) | N | 20 | Funding Body | Add
| 19 | Funding type - If 'Other' please specify | Add | N |
| |||||||
16 | Status | Update | N |
| 21 | Date From | Add | N | 22 | Date to | Add | N | Date format DD/MM/YYYY
| QUESTION: Is it a requirement to bulk update the status of a post e.g. from Current to Inactive? JW - Yes, this is a requirement | ||||
17 | Old Post | Update | N |
|
Post Fundings - Bulk Update Columns Headers - Validations
...
Row no. | Column heading | Add/Update/Matching Criteria | Mandatory | Rules | Questions/Notes for discussions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | TIS_PostFunding_ID* | Matching Criteria | Y |
| |||||||||
2 | TIS_Post_ID* | Matching Criteria | Y |
|
| ||||||||
3 | Funding type | Update | N |
| |||||||||
4 | Funding type - If 'Other' please specify | Update | N | Free text
| |||||||||
5 | Funding Body | Update | N |
| |||||||||
6 | Date From | Update | N | Date format DD/MM/YYYY
| |||||||||
7 | Date to | Update | N | Date format DD/MM/YYYY |
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Note: If non-mandatory fields are blank, retain existing value
Column Heading | Add/Update/Matching Criteria | Mandatory | Rules | Questions/Notes for discussions |
|---|---|---|---|---|
TIS_Post_ID* | Matching Criteria | Y |
| |
TIS_PostFunding_ID* | Matching Criteria | Y |
| |
Funding type | Update | N |
| |
Funding Details | Update | N |
| |
Funding Body | Update | N |
| |
Funding subtype | Update | N |
| |
Date From | Update | N |
| |
Date to | Update | N |
|