...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Table of Contents |
---|
Posts - Field Validation
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
- Drop down
- Default to NONE
...
Enabled NPN manual edit
- Type: Drop down
- Dependencies: "Enable/d NPN manually editing" = "Yes"
- Mandatory: Yes
- Editable: Yes
- Default value: 'NONE'
Auto-generation NPN
- Dependencies: "Enable/d NPN manually editing" = "No"
- Editable: No
...
Enabled NPN manual edit
- Type: Drop down
- Dependencies: "Enable/d NPN manually editing" = "Yes"
- Mandatory: Yes
- Editable: Yes
- Default value: 'NONE'
Auto-generation NPN
- Dependencies: "Enable/d NPN manually editing" = "No"
- Editable: No
Warning: Suffix cannot be amended for autogenerated NPN
This field is required
...
- Drop down
- Default to Yes
...
- Type: Drop down
- Mandatory: Yes
- Editable: Yes
- Default value: Yes
...
- Type: Drop down
- Mandatory: Yes
- Editable: Yes
- Default value: Yes
...
'Enable/d NPN manually editing' No
- Auto-created number based on the managing local office code, grade code, speciality code and postfix
- Not editable
- Not visible until post is created
'Enable/d NPN manually editing' Yes
- Free text
...
Sort
- ascending order
Enabled NPN manual edit
- Type: Manual entry
- Character type: Alphanumeric
- Special characters allowed: /
- Character length: Min characters 1, Max characters none
- Dependencies: "Enable/d NPN manually editing" = "Yes"
- Mandatory: Yes
- Editable: If NPN manual edit is enabled
- Default value: N/A
Autogeneration
- Type: Auto-generated
- Derived from owner code, grade code, specialty code, suffix
- Dependencies: "Enable/d NPN manually editing" = "No"
- Mandatory: No
- Editable: No
- Default value: N/A
- Display in real time i.e. as the user enters fields
Enabled NPN manual edit
- Type: Manual entry
- Character type: Alphanumeric
- Special characters allowed: /
- Character length: Min characters 1, Max characters none
- Dependencies: "Enable/d NPN manually editing" = "Yes"
- Mandatory: Yes
- Editable: If NPN manual edit is enabled
- Default value: N/A
Autogeneration
- Type: Auto-generated
- Derived from owner code, grade code, specialty code, suffix
- Dependencies: "Enable/d NPN manually editing" = "No"
- Mandatory: No
- Editable: No
- Default value: N/A
- Display in real time i.e. as the user enters fields
This field is required
Only special characters allowed are /
...
Page content
Table of Contents |
---|
Posts - Field Validation
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 |
|
|
Posts - Bulk create column headers - validations
This was reviewed with data leads and there's no no dissenters on the columns and validations to include.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
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:
|
|
- Drop down
- Default to CURRENT
- Type: Drop down
- Mandatory: Yes
- Editable: Yes
- Default value: CURRENT
- Type: Drop down
- Mandatory: Yes
- Editable: Yes
- Default value:CURRENT
- Drop down
- Smart search
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Drop down
- Smart search
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Limit to already created Posts
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Limit to already created Posts
- Free text
- Type: Drop down
- Mandatory: No
- Editable: Yes
- Limit to ref table
- Type: Drop down
- Mandatory: No
- Editable: Yes
- Limit to ref table
- Free text
- Type: Manual entry
- Characters: Text
- Special characters allowed: /
- Character length: Min characters 0, Max characters none
- Mandatory: No
- Editable: Yes
- Type: Manual entry
- Characters: Text
- Special characters allowed: /
- Character length: Min characters 0, Max characters none
- Mandatory: No
- Editable: Yes
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
- Drop down
- Smart search
- MANDATORY
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Display SiteKnownAs+SiteNumber
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Display SiteKnownAs+SiteNumber
- Drop down
- Smart search
- + or - button
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Display SiteKnownAs+SiteNumber
- Add multiple/all
- Remove one/all
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Display SiteKnownAs+SiteNumber
- Add multiple/all
- Remove one/all
- Drop down
- Smart search
- MANDATORY
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Add one Main specialty only
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Add one Main specialty only
This field is required
- Drop down
- Smart search
- + or -
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Add multiple/all
- Remove one/all
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Add multiple/all
- Remove one/all
- Drop down
- Smart search
- + or -
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Add multiple/all
- Remove one/all
- Limit to sub-specialties of the Main specialty
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Add multiple/all
- Remove one/all
- Limit to sub-specialties of the Main specialty
- Drop down
- Smart search
- MANDATORY
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Limit to Post Grades
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Limit to Post Grades
This field is required
Warning: only Post grades can be selected
- Drop down
- Smart search
- + or -
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Add multiple/all
- Remove one/all
- Limit to Post Grades
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Add multiple/all
- Remove one/all
- Limit to Post Grades
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
- Drop down
- Smart search
- MANDATORY
- Type: Drop down, current only
- Mandatory: Yes
- Editable: Yes
- Type: Drop down, current only
- Mandatory: Yes
- Editable: Yes
- Drop down
- Smart search
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Drop down
- Smart search
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Drop down
- Smart search
- + or -
- Type: Drop down - current only
Mandatory: Yes - Editable: Yes
- Add multiple/all
- Remove one/all
- Dependencies: "Rotation name" only editable after "Programme name" is selected
- Type: Drop down - current only
Mandatory: Yes - Editable: Yes
- Add multiple/all
- Remove one/all
- Dependencies: "Rotation name" only editable after "Programme name" is selected
- Free text
- Type: Manual entry
- Characters: Text
- Special characters allowed:
forward slash ( / ), apostrophes ( ' ), hypens ( - ), full stops ( . ) and spaces ( )
- Character length: Min characters 0, Max characters none
- Mandatory: No
- Editable: Yes
- Type: Manual entry
- Characters: Text
- Special characters allowed:
forward slash ( / ), apostrophes ( ' ), hypens ( - ), full stops ( . ) and spaces ( )
- Character length: Min characters 0, Max characters none
- Mandatory: No
- Editable: Yes
15 | Owner* | Add | Y | Accepted values should match to one of Local Office reference table and are CURRENT. | ||
16 | Funding type* | Add | Y |
| ||
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 |
Questions and Assumptions
# | Question | Comments |
---|---|---|
1 | Should you be able to add Post fundings as part of the Post upload or should this be separate? | Yes! |
2 | Will the post funding information be available at the time of creating the posts? | Yes |
3 | What are the MVP fields for a Post Import template? | Update template is MVP. |
4 | 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? | Amend. |
Posts - Bulk Update column headers - validations
Note: Through the use of the bulk update function the NPN will not change.
AR: The Update template will be used to update existing TIS Posts details and also to add Rotations and Funding episodes to them.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
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_Programme_ID | Update (replace all existing values) | N |
| |
14 | Owner | Update | N |
| |
15 | Rotation | Update (replace all existing values) | N |
| |
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 |
17 | Old Post | Update | N |
|
Post Fundings - Bulk Update Columns Headers - Validations
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Ashley Ransoo and Alistair Pringle (Unlicensed) to run through with Data leads / stakeholders.- Done on 19/08 - Data leads happy with the below.
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 |
Post Funding FE Fields Validation New
Field name | Reference Table | Initial value in dropdown | Proposed value in dropdown | Current value in dropdown | Initial FE Validation & Rules | Proposed FE Validation Rules | Current FE Validation & Rules | Error Messages | List Page?(Y/N) | List Page Rules (Sort/Filter) | Comment |
---|---|---|---|---|---|---|---|---|---|---|---|
Funding type |
|
|
|
|
|
In addition to the Initial FE Validation Rules;
|
- Free text, if 'Funding type' 'OTHER is selected
If Funding type is "Other"
- Type: Manual entry
- Characters: Text
- Special characters allowed:
forward slash ( / ), apostrophes ( ' ), hypens ( - ), full stops ( . ) and spaces ( )
- Character length: Min characters 0, Max characters none
- Mandatory: No
- Dependencies:Only active when "Funding type" is "Other" otherwise greyed out
- Editable: Yes
If Funding type is not "Other"
- Editable: No
If Funding type is "Other"
- Type: Manual entry
- Characters: Text
- Special characters allowed:
forward slash ( / ), apostrophes ( ' ), hypens ( - ), full stops ( . ) and spaces ( )
- Character length: Min characters 0, Max characters none
- Mandatory: No
- Dependencies:Only active when "Funding type" is "Other" otherwise greyed out
- Editable: Yes
If Funding type is not "Other"
- Editable: No
- Drop down
- Smart search
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Add multiple
- Type: Smart search
- Mandatory: Yes
- Editable: Yes
- Add multiple
- Free text or calendar pick
- Date format DD/MM/YYYY
If Funding type is "No value provided"
- Editable: No
If Funding type is not "No value provided"
|
|
| Y | Filter |
https://hee-tis.atlassian.net/browse/TIS21-4801
|
Funding Details | N/A | N/A | N/A |
Then the ‘Funding Details’ field is greyed out; don’t accept text. If Funding type is "Other"
Then the ‘Funding Details’ field is NOT greyed out; accept text.
|
|
If Funding type is not " |
- Type: Free text or calendar pick
- Date format DD/MM/YYYY
- Character type: Numerical
- Special characters allowed: /
- Mandatory: Yes
- Dependencies: Only active when "Funding type" is not "No value provided" otherwise greyed out
- Editable: Yes
- Type otherwise greyed out
- Editable: Yes
This field is required
Only special characters allowed /
- Free text or calendar pick
- Date format DD/MM/YYYY
If Funding type is "No value provided"
Editable: no
If Funding type is not "No value provided"
- Type: Free text or calendar pick
- Date format DD/MM/YYYY
- Character type: Numerical
- Special characters allowed: /
- Mandatory: Yes
- Dependencies:Only active when "Funding type" is not "No value provided" otherwise greyed out
- Editable: Yes
- Type otherwise greyed out
- Editable: Yes
If Funding type is "No value provided"
- Editable: No
If Funding type is not "No value provided"
Other"
|
In addition to the Initial FE Validation Rules;
Then the ‘Funding Details’ field is greyed out; don’t accept text.
Then the ‘Funding Details’ field is NOT greyed out; accept text. |
Then the ‘Funding Details’ field is greyed out; don’t accept text. If Funding type is "Other"
Then the ‘Funding Details’ field is NOT greyed out; accept text.
|
|
|
If Funding type is not "Other"
|
| Only special characters allowed |
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
- Drop down
- Smart search
- Type: Smart search
- Mandatory: No
- Editable: Yes
- Add multiple/all
- Remove one/all
- Dependencies: Only active when Programme selected, otherwise greyed out. History only populates if Rotation is selected.
- Limit to Rotations already created
- Current values only
- Limited to Rotations in same Programme
: forward slash ( / ), apostrophes ( ' ), hypens ( - ), full stops ( . ) and spaces ( ) | N |
| |||
Funding body | No value display, it is smart search |
|
|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
- Read only
Y (Current Trainee)
Sort
Max 1 current trainee displayed in list page
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Read only
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Read only
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Read only
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Read only
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Read only
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Read only
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Read only
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
- Type: Derived from Placements
- Dependencies: Populates if Rotation is selected
- Editable: No
Posts - Bulk create column headers - validations - (DRAFT)
STILL TO BE REVIEWED - DO NOT SHARE
...
- the column should be mandatory on the template
- It would be an Add type
- The import will only be successful for the row if the NPN does not already exist, if already exist then throw an error in the downloadable template 'Cannot add post with this NPN as there are other posts with the same NPN'
- The 'Manually edit NPN / Auto-generate NPN' will be automatically set to 'Manually edit'
...
- Comma separated to add multiple
- Accepted values should match to one of the Grade reference table and are CURRENT
...
- Comma separated to add multiple
- Accepted values should match to one of the Specialty reference table and are CURRENT
...
- Comma separated to add multiple
- Accepted values should match to one of the Specialty reference table and are CURRENT
...
Should this be constrained to specialty type SUB_SPECIALTY?
Yes, but only when the PAG has reviewed and validated the current sub_spec list.
...
- Comma separated to add multiple
- Accepted values should match to one of the SiteKnownAs from Site reference table 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)
...
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)
...
Questions and Assumptions
...
Posts - Bulk Update column headers - validations - (DRAFT)
Note: Through the use of the bulk update function the NPN will not change.
AR: The Update template will be used to update existing TIS Posts details and also to add Rotations and Funding episodes to them.
- Should match to one of TIS_PostID's
- Accepted values should match to one of the Grade reference table and are CURRENT
- Validation throughout matches the validation on the TIS Post front end
- Comma separated to add multiple
- Accepted values should match to one of the Grade names in the reference table and are CURRENT (NOTE: abbreviations will not be accepted to match the FE validation)
Will a value in this column add to the existing values in this field in the Post or will it replace?
AR: If replacing, does it mean wiping existing rotations against the post and start fresh with the ones from the template?
- Accepted values should match to one of the Specialty reference table and are CURRENT
- Comma separated to add multiple
- Accepted values should match to one of the Specialty reference table and are CURRENT
Will a value in this column add to the existing values in this field in the Post or will it replace?
AR: If replacing, does it mean wiping existing 'Other specialties' against the post and start fresh with the ones from the template?
- Comma separated to add multiple
- Accepted values should match to one of the Specialty reference table and are CURRENT
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
AR:Will a value in this column add to the existing values in this field in the Post or will it replace?
If replacing, does it mean wiping existing 'sub specialties' against the post and start fresh with the ones from the template?
- Accepted values should match to one of the SiteKnownAs from Site reference table and are CURRENT
- Comma separated to add multiple
- Accepted values should match to one of the SiteKnownAs from Site reference table and are CURRENT
Will a value in this column add to the existing values in this field in the Post or will it replace?
AR: If replacing, does it mean wiping existing 'other sites' against the post and start fresh with the ones from the template?
- Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT
- Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT
- If populated on template, Programme Name and Number should both match to one of the existing programmes on TIS and are CURRENT.
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.
Intrepid/TIS views for data audit will show posts with no programme attached
- If populated on template, Programme Name and Number should both match to one of the existing programmes on TIS and are CURRENT.
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.
Intrepid/TIS views for data audit will show posts with no programme attached
- Accepted values should match to one of Local Office reference table and are CURRENT.
- Comma separated to add multiple
- Accepted values should match to one of the CURRENT Rotations from the Rotation list.
- AR: The rotations list is populated with only those that match Programme name and Number in the UI - Accepted values should therefore only be only one of those from that match the Programme Name and Number against the existing TIS_PostID.
Will a value in this column add to the existing values in this field in the Post or will it replace?
AR: If replacing, does it mean wiping existing rotations against the post and start fresh with the ones from the template?
Then the ‘Funding body’ field is NOT greyed out; accept text | Mandatory: No In addition to the Initial FE Validation Rules;
Then the ‘Funding body’ field is NOT greyed out; accept text |
Then the ‘Funding body’ field is NOT greyed out; accept text | This field is required | N |
| ||||||
Start date |
Then the ‘Start date’ field is greyed out; don’t accept text.
Then the ‘Start date’ field is NOT greyed out; accept text.
|
In addition to the Initial FE Validation Rules:
Then the ‘Start date’ field is NOT greyed out; accept text. |
Then the ‘Start date’ field is greyed out; don’t accept text.
Then the ‘Start date’ field is NOT greyed out; accept text.
|
| N |
| |||||
End date |
Then the ‘End date ’ field is greyed out; don’t accept text.
Then the ‘End date ’ field is NOT greyed out; accept text.
| Apart form the list in the Initial FE Validation & Rules, the following should be added
Inputting Placement: Validation message for a posts with status ‘Inactive’/funding end date expires OR inadequate funding end date when inputting placement against an ‘inactive’ post ( using UI/PPT or Placement bulk upload) In addition to the Initial FE Validation Rules;
Then the ‘End date ’ field is NOT greyed out; accept text. |
Then the ‘End date’ field is greyed out; don’t accept text.
Then the ‘End date’ field is NOT greyed out; accept text.
|
| N |
https://hee-tis.atlassian.net/browse/TIS21-4801
| |||||
This is new field to be created; Sub-category | To be created | None because it is a new filed to be created. |
| None because it is a new filed to be created. |
| To be updated after implementation | Funding Type Sub-category | ||||
This is new field to be created; Funding Reason | To be created | None because it is a new filed to be created. |
| None because it is a new filed to be created. |
| To be updated after implementation | Funding Type- Funding reason; |
Post Funding Bulk Upload (Post Funding Creation) Fields Validation:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Column Heading | Add/Update/Matching Criteria | Mandatory | Rules | Questions/Notes for discussions |
---|---|---|---|---|
TIS_Post_ID* | Matching Criteria | Y |
| |
Funding type | Add | Y |
| |
Funding Details | Add | N |
| |
Funding Body | Add | N |
| |
Funding subtype | Add | N |
| |
Date From | Add | Y |
| |
Date to | Add | N | Date format DD/MM/YYYY |
Post Funding Bulk Upload (Post Funding Update) Fields Validation
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 |
|
Free text
AR: If Funding type is not "Other", no value should be present in this column for the row on the template.
IF Funding type is 'Other', this should be mandatory to populate on template.
|
- Accepted values should match to one of existing NPN's held on TIS.
- Accepted values should match to one of Funding Type reference table and are CURRENT.
- AR: Cannot be left blank on the template, if one of 20-23 is populated on template.
- Can only add one Funding episode from one row of data from the template, for multiple episodes multiple rows for the same TIS_PostID is required.
Funding Details | Update | N |
| |
Funding Body | Update | N |
| |
Funding subtype | Update | N |
|
|
| |
Date From |
Update | N |
|
AR: BE/FE validations for Post and Post Funding ticket are yet to be done.
Ideally this should be mandatory if Funding type has been populated.
| |||
Date to | Update | N |
|
AR: BE/FE validations for Post and Post Funding ticket are yet to be done.
Ideally this should be mandatory if Funding type has been populated.