Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

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   

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4748
 / 
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4747

1

Suffix

See: TIS UI Fields - Dropdowns

  • Drop down 

  • Default to NONE

N


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 

Can Suffix be amended (changed, added, or removed) in an autogenerated NPN after it's been created?


2

Enable/d NPN manually editing


  • Drop down 

  • Default to Yes

N


  • Type: Drop down 

  • Mandatory: Yes

  • Editable: Yes

  • Default value: Yes

  • Type: Drop down 

  • Mandatory: Yes

  • Editable: Yes

  • Default value: Yes

Warning: If "No" selected, the NPN cannot be edited



3

National post number


'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

Y

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: / (note, no spaces)

  • 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 /










The error message should only be displayed where "Enable/d NPN manually editing" = Yes


Allocation 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4749
 / 
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4750

4

Main site 

See: TIS UI Fields - Dropdowns

  • Drop down

  • Smart search 

  • MANDATORY

Y (Primary Site)

Filter 

  • Type: Smart search 

  • Mandatory: Yes

  • Editable: Yes

  • Display SiteKnownAs+SiteNumber

  • Type: Smart search 

  • Mandatory: Yes

  • Editable: Yes

  • Display SiteKnownAs+SiteNumber

This field is required 



5

Other sites (optional)

See: TIS UI Fields - Dropdowns

  • Drop down

  • Smart search 

  • + or - button 

N


  • 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


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

  • Drop down

  • Smart search 

  • MANDATORY 

Y (Primary Specialty

Filter 

  • 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 




7

Other specialities

See: TIS UI Fields - Dropdowns

  • Drop down

  • Smart search 

  • + or -

N


  • 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


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

  • Drop down 

  • Smart search 

  • + or -

N


  • 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

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

  • Drop down 

  • Smart search 

  • MANDATORY

Y

Filter 

  • 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



10

Other grades 

See: TIS UI Fields - Dropdowns

  • Drop down

  • Smart search 

  • + or -

N


  • 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

Warning: only Post grades can be selected



Ownership 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4752
 / 
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4751

11

 , 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-3651

11

Owner

See: TIS UI Fields - Dropdowns

  • Drop down

  • Smart search 

  • MANDATORY 

Y

Filter 

  • Type: Drop down, current only

  • Mandatory: Yes

  • Editable: Yes

  • Type: Drop down, current only

  • Mandatory: Yes

  • Editable: Yes

This field is required 



12

Employing body

See: TIS UI Fields - Dropdowns

  • Drop down

  • Smart search 

N


  • Type: Smart search 

  • Mandatory: Yes

  • Editable: Yes

  • Type: Smart search 

  • Mandatory: Yes

  • Editable: Yes

This field is required 



13

Training body

See: TIS UI Fields - Dropdowns

  • Drop down

  • Smart search 

N


  • Type: Smart search 

  • Mandatory: Yes

  • Editable: Yes

  • Type: Smart search 

  • Mandatory: Yes

  • Editable: Yes

This field is required 



14

Programme

name 

name* 

See: TIS UI Fields - Dropdowns

  • Drop down

  • Smart search 

  • + or - 

Y

Filter

  • Type: Drop down -  current only
    Mandatory:

Yes 
  • Yes - 

    Jira Legacy
    serverSystem JIRA
    serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
    keyTISNEW-3651
     

  • 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 

This field is required 



15

Training description


  • Free text 

N


  • 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

Only special characters allowed: forward slash ( / ), apostrophes ( ' ), hypens  ( - ), full stops ( . ) and spaces (   )



18

Status 

See: TIS UI Fields - Dropdowns

  • Drop down

  • Default to CURRENT

Y

Filter 

  • Type: Drop down 

  • Mandatory: Yes

  • Editable: Yes

  • Default value: CURRENT 

  • Type: Drop down 

  • Mandatory: Yes

  • Editable: Yes

  • Default value:CURRENT 

This field is required 



19 

Old post 


  • Drop down 

  • Smart search 

N


  • Type: Smart search 

  • Mandatory: No

  • Editable: Yes

  • Type: Smart search 

  • Mandatory: No 

  • Editable: Yes




20

New post 


  • Drop down 

  • Smart search 

N


  • Type: Smart search 

  • Mandatory: No

  • Editable: Yes

  • Limit to already created Posts

  • Type: Smart search 

  • Mandatory: No

  • Editable: Yes

  • Limit to already created Posts




21

Post family 


  • Free text

N


  • Type: Drop down

  • Mandatory: No

  • Editable: Yes 

  • Limit to ref table

  • Type: Drop down

  • Mandatory: No

  • Editable: Yes 

  • Limit to ref table


JW to discuss with SMEs


22

Local post number


  • Free text 

N


  • 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




Funding (Needs to be discussed with SMEs - particularly EM & LASE) 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4753
 / 
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4754

23

Funding type 

See: TIS UI Fields - Dropdowns

  • Drop down

  • Default to 'No value provided'

Y

Filter 

  • Type: Drop down

  • Mandatory: Yes

  • Dependencies:"If 'Other', please specify," "Start date," "End date"

  • Editable: Yes 

  • Default value: "No value provided"

  • Type: Drop down

  • Mandatory: Yes

  • Dependencies:"If 'Other', please specify," "Start date," "End date"

  • Editable: Yes 

  • Default value: "No value provided"

This field is required 



24

If 'Other', please specify 


  • Free text, if 'Funding type' 'OTHER is selected 

N


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

Only special characters allowed: forward slash ( / ), apostrophes ( ' ), hypens  ( - ), full stops ( . ) and spaces (   )



25

Funding body / organisation

See: TIS UI Fields - Dropdowns

  • Drop down

  • Smart search

N


  • Type: Smart search 

  • Mandatory: Yes

  • Editable: Yes

  • Add multiple

  • Type: Smart search 

  • Mandatory: Yes

  • Editable: Yes

  • Add multiple

This field is required 

Should be pulling from "Funding Organisation table"


26

Start date


  • Free text or calendar pick

  • Date format DD/MM/YYYY

N


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"

    • 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 /



27

End date 


  • Free text or calendar pick

  • Date format DD/MM/YYYY

N


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"

  • 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 /



Rotation 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4755
 / 
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4756

29

Rotation name 


  • Drop down

  • Smart search 

N


  • 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

  • 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

Warning: Only rotations from within the same programme as the post can be selected



History (Table) 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4757
 / 
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-4758

30

Trainee full name


  • 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




31

Start date


  • Read only

N


  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No

  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No




32

End date


  • Read only

N


  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No

  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No




33

Main site 


  • Read only

N


  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No

  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No




 34

Main specialty


  • Read only

N


  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No

  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No




35

Placement grade


  • Read only

N


  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No

  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No




36

Placement type


  • Read only

N


  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No

  • Type: Derived from Placements

  • Dependencies: Populates if Rotation is selected 

  • Editable: No




37

Status 


  • Read only

N


  • 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

...

STILL TO BE REVIEWED - DO NOT SHARE

...

This was reviewed with data leads and there's no no dissenters on the columns and validations to include. 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-3650

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-3651


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. 

If not, then:

  • 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'


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

Comma separated to
  • Semicolon ( ; ) separated to add multiple

  • Accepted values should match to one of the Grade reference table and are CURRENT

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

Comma separated
  • Semicolon ( ; ) to add multiple

  • Accepted values should match to one of the Specialty reference table and are CURRENT



6

Sub specialties

Add

N

Comma separated to
  • Semicolon ( ; ) 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. 


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

Comma separated to
  • Semicolon ( ; ) to add multiple

  • Accepted values should match to one of the SiteKnownAs from Site reference table and are CURRENT



10

Training body*

Add

N

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

body*

Add

N

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

AddNOwner

*

(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)

14

Not currently mandatory, but need to be made mandatory across the board (BE, FE, Bulk Upload) - Ticket?

14

TIS_Programme_ID*

Add

Y

  • Semicolon ( ; ) separated to add multiple

  • Accepted values should match to

one of Local Office reference table and are CURRENT. 15Old postAddN
  • CURRENT TIS Programme IDs.

Instead of Progamme Name and Programme Number as separate columns on the template, we could do TIS_Programme_ID. We have used TIS_Programme_ID on bulk post update, so to keep consistent with and hopefully easier to match on.

Story to make this field mandatory from all journeys:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-3651


15

Owner*

Add

Y

Accepted values should match to one of

existing NPN's held on TIS.Is this required in a bulk create scenario? Yes New postIs this required in a bulk create scenario? NoLocal post numberIs this required in a bulk create scenario? NoPost familyIs this required in a bulk create scenario? No

Questions and Assumptions

...

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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-2628

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-2672

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-2673

Row no.Column headingAdd/Update/Matching CriteriaMandatoryRulesQuestions/Notes for discussions1TIS_PostID*Matching CriteriaY
  • Should match to one of TIS_PostID's
2Approved gradeUpdateN
  • 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
3Other gradesUpdate (replace all existing values)N
  • 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)
4SpecialtyUpdateN
  • Accepted values should match to one of the Specialty reference table and are CURRENT
5Other specialtiesUpdate (replace all existing values)N
  • Comma separated to add multiple
  • Accepted values should match to one of the Specialty reference table and are CURRENT
6Sub specialtiesUpdate (replace all existing values)NComma separated to add multiple

Local Office reference table and are CURRENT. 



16

Funding type*

Add

Y

  • Accepted values should match to one of Funding Type reference table and are CURRENT. 

  • Cannot be left blank on the template, if one of 20-22 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.

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

  • Only use when Funding Type = Other

19

Funding Body

Add

N

  • Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT

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
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-2628

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-2672

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-2673


Row no.

Column heading

Add/Update/Matching Criteria

Mandatory

Rules

Questions/Notes for discussions

1

TIS_PostID*

Matching Criteria

Y

  • Should match to one of TIS_PostID's


2

Approved grade

Update

N

  • Accepted values should match to one of the

Specialty 7Training descriptionUpdateNFreetext8Main siteUpdateN
  • Grade 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

  • Validation throughout matches the validation on the TIS Post front end


3

Other grades

Update (replace all existing values)

N

  • Semicolon 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)


4

Specialty

Update

N

  • Accepted values should match to one of the

SiteKnownAs from Site
  • Specialty reference table and are CURRENT

Check that all 'SiteKnownAs' names have the site code afterwards (follow a standard convention) - JW run report to check9Other sites


5

Other specialties

Update (replace all existing values)

N

  • Semicolon separated to add multiple

  • Accepted values should match to one of the Specialty reference table and are CURRENT


6

Sub specialties

Update (replace all existing values)

N

Comma separated
  • Semicolon separated to add multiple

  • Accepted values should match to one of the

SiteKnownAs from Site Accepted values should
  • Specialty reference table and are CURRENT

10Training bodyUpdateN

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

TrustKnownAs from Trust Employing body

Specialty reference table and are CURRENT

11


7

Training description

Update

N

Freetext


8

Main site

Update

N

  • Accepted values should match to one of the

TrustKnownAs
  • SiteKnownAs from

Trust
  • Site reference table and are CURRENT

12Programme name

Update

AR 22/03: This is being dscussed in DQ channel.

N
  • If populated on template, Programme Name and Number should both match to one of the existing programmes on TIS and are CURRENT.

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

  • Semicolon separated to add multiple

  • Accepted values should match to one of the SiteKnownAs from Site reference table and are CURRENT


10

Training body

Update

N

  • Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT


11

Employing body

Update

N

  • Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT


12

Programme name

Update

AR 22/03: This is being dscussed in DQ channel.

N

  • 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

13

Programme number

Update

AR 22/03: This is being dscussed in DQ channel.

N

  • 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

12

TIS_Programme_ID

Update (replace all existing values)

N

  • Comma separated to add multiple

  • Accepted values should match to CURRENT TIS Programme IDs.


14

Owner

Update

N

  • Accepted values should match to one of Local Office reference table and are CURRENT. 


15

Rotation

Update (replace all existing values)

N

  • Comma separated to add multiple

  • Accepted values should match to one of the CURRENT Rotations from the Rotation list.

  • The rotations list is populated with only those that match Programme name and Number in the UI - Accepted values should therefore be one of those that match the Programme Name and Number linked to the TIS_PostID. 



16

Status

Update

N

  • Accepted values should match to one of the allowed Status' and are CURRENT. 

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

17Old PostUpdateN
  • Accepted values should match to one of existing NPN's held on TIS.
18Funding type

the status of a post e.g. from Current to Inactive?

JW - Yes, this is a requirement

17

Old Post

Update

N

  • Accepted values should match to one of existing NPN's held on TIS.



Post Fundings - Bulk Update Columns Headers - Validations 

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISNEW-3248

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

  • Should match to one of TIS_PostFundingID's


2

TIS_Post_ID*

Matching Criteria

Y

  • Should validate if the post funding is under this post ID

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-3949

3

Funding type

Update

N

  • Accepted values should match to one of Funding Type reference table and are CURRENT. 

  • Can only update one Funding episode from one row of data from the template, for multiple episodes of the same post, multiple rows for each TIS_PostFunding_ID is required.


4

Funding type - If 'Other' please specify

Update

N

Free text

  • Only use when Funding Type = Other



5

Funding Body

Update

N

  • Accepted values should match to one of the TrustKnownAs from Trust reference table and are CURRENT


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 

See: TIS UI Fields - Dropdowns

  • No value provided

  • Academic- HEE

  • Academic - NIHR

  • Academic - Trust

  • HEE Funded - Non-Tariff

  • HEE Funded - Tariff

  • Long Term Plan

  • Military

  • Other

  • Supernumerary

  • Trust Funded

  • No value provided

  • Academic- HEE

  • Academic - NIHR

  • Academic - Trust

  • HEE Funded - Non-Tariff

  • HEE Funded - Tariff

  • Long Term Plan

  • Military

  • Other

  • Supernumerary

  • Trust Funded

  • Academic - University

  • 100% Tariff Funded

  • No value provided

  • Academic- HEE

  • Academic - NIHR

  • Academic - Trust

  • HEE Funded - Non-Tariff

  • HEE Funded - Tariff

  • Long Term Plan

  • Military

  • Other

  • Supernumerary

  • Trust Funded

  • Academic - University

  • 100% Tariff Funded

  • Drop down

  • Default to 'No value provided'

  • If you select ‘Academic - NIHR’ from the ‘Funding type’ dropdown list, then the ‘Funding body’ field is populated with ‘National Institute for Health Research’

  • Type: Drop down

  • Mandatory: Yes

  • Dependencies:"If 'Other', please specify," "Start date," "End date"

  • Editable: Yes 

  • Default value: "No value provided"

In addition to the Initial FE Validation Rules;

  • Mandatory: Yes ( using TIS UI or Post bulk upload)

  • Admin cannot create a new post without completing this field (a new post MUST have at least a post funding)

  • Admin cannot update a post without completing this field (a post MUST have at least a post funding)


  • Drop down

  • Default to 'No value provided'

  • If you select ‘Academic - NIHR’ from the ‘Funding type’ dropdown list, then the ‘Funding body’ field is populated with ‘National Institute for Health Research’

  • Type: Drop down

  • Mandatory: Yes ( using TIS UI or Post bulk upload

  • Dependencies:"If 'Other', please specify," "Start date," "End date"

  • Editable: Yes 

  • Default value: "No value provided"

  • Admin cannot create a new post without completing this field (a new post MUST have at least a post funding)

  • Admin cannot update a post without completing this field (a post MUST have at least a post funding)

  • This field is required 

  • Error report of listing the missing mandatory field as the reason when creating the post

Y

Filter 

  • Admin should not be able to create/update/save post on TIS if the mandatory field is not completed in UI or post bulk template

https://hee-tis.atlassian.net/browse/TIS21-4801

  • Question: Should other fields in post funding be greyed out or allow free text when the new funding types are added? James Response I think 'Academic - University' it should be editable and for '100% Tariff Funded' it should be greyed out
    https://hee-tis.atlassian.net/browse/TIS21-4875

  • Add ‘Academic - University’ and ‘100% Tariff Funded’ to list of funding type

https://hee-tis.atlassian.net/browse/TIS21-4802

Funding Details


N/A

N/A

N/A

  • If you select the following from the ‘Funding type’ dropdown;

  1. ‘No value provided’

  2. ‘Trust Funded’

  3. ‘Military’

  4. 'Long Term Plan'

  5. 'HEE Funded - Tariff'

  6. ‘HEE Funded - Non- Tariff’

Then the ‘Funding Details’ field is greyed out; don’t accept text.

If Funding type is "Other"

  • If you select the following from the ‘Funding type’ dropdown;

  1. ‘Academic - HEE’

  2. 'Academic - NIHR'

  3. 'Academic Trust'

  4. 'Other'

  5. 'Supernumerary'

Then the ‘Funding Details’ field is NOT greyed out; accept 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

  • Dependencies:Only active when "Funding type" is "Other" otherwise greyed out

  • Editable: Yes

If Funding type is not "Other"

  • Editable: No

  • Mandatory: No

In addition to the Initial FE Validation Rules;

  • If you select the following from the ‘Funding type’ dropdown;

  1. 100% Tariff Funded - Done

Then the ‘Funding Details’ field is greyed out; don’t accept text.

  • If you select the following from the ‘Funding type’ dropdown;

  1. Academic - University- Done

Then the ‘Funding Details’ field is NOT greyed out; accept text.

  • If you select the following from the ‘Funding type’ dropdown;

  1. ‘No value provided’

  2. ‘Trust Funded’

  3. ‘Military’

  4. 'Long Term Plan'

  5. 'HEE Funded - Tariff'

  6. ‘HEE Funded - Non- Tariff’

  7. 100% Tariff Funded - Done

Then the ‘Funding Details’ field is greyed out; don’t accept text.

If Funding type is "Other"

  • If you select the following from the ‘Funding type’ dropdown;

  1. ‘Academic - HEE’

  2. 'Academic - NIHR'

  3. 'Academic Trust'

  4. 'Other'

  5. 'Supernumerary'

  6. Academic - University- Done

Then the ‘Funding Details’ field is NOT greyed out; accept 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

  • Dependencies:Only active when "Funding type" is "Other" otherwise greyed out

  • Editable: Yes

If Funding type is not "Other"

  • Editable: No

Only special characters allowed: forward slash ( / ), apostrophes ( ' ), hypens  ( - ), full stops ( . ) and spaces (   )

N


  • Funding Details: This is field is not fillable unless certain funding types are selected, e.g. ‘Other’

https://hee-tis.atlassian.net/browse/TIS21-4801

Funding body

See: TIS UI Fields - Dropdowns

No value display, it is smart search



  • Drop down

  • Smart search

  • Type: Smart search 

  • Mandatory: No

  • Editable: Yes

  • Add multiple

  • If you select the following from the ‘Funding type’ dropdown;

  1. No value provided

  2. Trust Funded’

  3. ‘Military’

  4. 'Long Term Plan'

  5. 'HEE Funded - Tariff'

  6. ‘HEE Funded - Non- Tariff’

  7. ‘Academic - HEE’

  8. 'Academic - NIHR'

  9. 'Academic Trust'

  10. 'Other'

  11. 'Supernumerary'

Then the ‘Funding body’ field is NOT greyed out; accept text

Mandatory: No

In addition to the Initial FE Validation Rules;

  • If you select the following from the ‘Funding type’ dropdown;

  1. 100% Tariff Funded

  2. Academic - University

Then the ‘Funding body’ field is NOT greyed out; accept text

  • Drop down

  • Smart search

  • Type: Smart search 

  • Mandatory: No

  • Editable: Yes

  • Add multiple

  • If you select the following from the ‘Funding type’ dropdown;

  1. No value provided

  2. Trust Funded’

  3. ‘Military’

  4. 'Long Term Plan'

  5. 'HEE Funded - Tariff'

  6. ‘HEE Funded

  7. ‘Academic - HEE’

  8. 'Academic - NIHR'

  9. 'Academic Trust'

  10. 'Other'

  11. 'Supernumerary'

  12. 100% Tariff Funded

  13. Academic - University

Then the ‘Funding body’ field is NOT greyed out; accept text

This field is required 

N


  • Should be pulling from "Funding Organisation table"

  • Funding Body: There is outstanding work to be done on the Trust table which populates this dropdown. This field is not used by all Local Offices especially with Tariff posts as the Post Owner would be the same as the Funding Body

https://hee-tis.atlassian.net/browse/TIS21-4801

Start date





  • If you select the following from the ‘Funding type’ dropdown;

  1. ‘No value provided’

Then the ‘Start date’ field is greyed out; don’t accept text.

  • If you select the following from the ‘Funding type’ dropdown;

  1. Trust Funded’

  2. ‘Military’

  3. 'Long Term Plan'

  4. 'HEE Funded - Tariff'

  5. ‘HEE Funded - Non- Tariff’

  6. ‘Academic - HEE’

  7. 'Academic - NIHR'

  8. 'Academic Trust'

  9. 'Other'

  10. 'Supernumerary'

Then the ‘Start date’ field is NOT greyed out; accept text.

  • Free text or calendar pick

  • Date format DD/MM/YYYY

  • If Funding type is "No value provided", the Start date is greyed out; don’t accept text.

  • If Funding type is NOT "No value provided", the Start date is NOT greyed out; accept text.

  • 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 

  • Mandatory: Yes ( using TIS UI or Post bulk upload)

  • Admin cannot create a new post without completing this field (a new post MUST have at least a post funding)

  • Admin cannot update a post without completing this field (a post MUST have at least a post funding)

In addition to the Initial FE Validation Rules:

  • If you select the following from the ‘Funding type’ dropdown;

  1. 100% Tariff Funded

  2. Academic - University

Then the ‘Start date’ field is NOT greyed out; accept text.

  • Mandatory: Yes ( using TIS UI or Post bulk upload)

  • Admin cannot create a new post without completing this field (a new post MUST have at least a post funding)

  • Admin cannot update a post without completing this field (a post MUST have at least a post funding)

  • If you select the following from the ‘Funding type’ dropdown;

  1. ‘No value provided’

Then the ‘Start date’ field is greyed out; don’t accept text.

  • If you select the following from the ‘Funding type’ dropdown;

  1. Trust Funded’

  2. ‘Military’

  3. 'Long Term Plan'

  4. 'HEE Funded - Tariff'

  5. ‘HEE Funded - Non- Tariff’

  6. ‘Academic - HEE’

  7. 'Academic - NIHR'

  8. 'Academic Trust'

  9. 'Other'

  10. 'Supernumerary'

  11. 100% Tariff Funded

  12. Academic - University

Then the ‘Start date’ field is NOT greyed out; accept text.

  • Free text or calendar pick

  • Date format DD/MM/YYYY

  • If Funding type is "No value provided", the Start date is greyed out; don’t accept text.

  • If Funding type is NOT "No value provided", the Start date is NOT greyed out; accept text.

  • 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 

  • This field is required 

  • Only special characters allowed / 

  • Error report of listing the missing mandatory field as the reason when creating the post

N


  • Admin should not be able to create/update/ save post on TIS if the mandatory field is not completed in UI or post bulk template

https://hee-tis.atlassian.net/browse/TIS21-4801

End date 





  • If you select the following from the ‘Funding type’ dropdown;

  1. ‘No value provided’

Then the ‘End date ’ field is greyed out; don’t accept text.

  • If you select the following from the ‘Funding type’ dropdown;

  1. Trust Funded’

  2. ‘Military’

  3. 'Long Term Plan'

  4. 'HEE Funded - Tariff'

  5. ‘HEE Funded - Non- Tariff’

  6. ‘Academic - HEE’

  7. 'Academic - NIHR'

  8. 'Academic Trust'

  9. 'Other'

  10. 'Supernumerary'

Then the ‘End date ’ field is NOT greyed out; accept text.

  • Free text or calendar pick

  • Date format DD/MM/YYYY

  • If Funding type is "No value provided", the End date is greyed out; don’t accept text.

  • If Funding type is NOT "No value provided", the End date is NOT greyed out; accept text.

  • If Funding type is not "No value provided"

  1. Type: Free text  or calendar pick 

  2. Date format DD/MM/YYYY

  3. Character type: Numerical 

  4. Special characters allowed: /

  5. Mandatory: Yes 

  6. Dependencies:Only active when "Funding type" is not "No value provided" otherwise greyed out

  7. Editable: Yes

  8. Type otherwise greyed out

  9. Editable: Yes 


Apart form the list in the Initial FE Validation & Rules, the following should be added

  • Mandatory: No

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;

  • If you select the following from the ‘Funding type’ dropdown;

  1. 100% Tariff Funded

  2. Academic - University

Then the ‘End date ’ field is NOT greyed out; accept text.

  • Mandatory: No

  • 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)

  • If you select the following from the ‘Funding type’ dropdown;

  1. ‘No value provided’

Then the ‘End date’ field is greyed out; don’t accept text.

  • If you select the following from the ‘Funding type’ dropdown;

  1. Trust Funded’

  2. ‘Military’

  3. 'Long Term Plan'

  4. 'HEE Funded - Tariff'

  5. ‘HEE Funded - Non- Tariff’

  6. ‘Academic - HEE’

  7. 'Academic - NIHR'

  8. 'Academic Trust'

  9. 'Other'

  10. 'Supernumerary'

  11. 100% Tariff Funded

  12. Academic - University

Then the ‘End date’ field is NOT greyed out; accept text.

  • Free text or calendar pick

  • Date format DD/MM/YYYY

  • If Funding type is "No value provided", the End date is greyed out; don’t accept text.

  • If Funding type is NOT "No value provided", the End date is NOT greyed out; accept text.

  • 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 

  • This field is required 

  • Only special characters allowed /

  • Example of possible messages:

    • ”This placement would be in an inactive post. You cannot continue”

    • ”This placement would be in a post where the funding dates do not cover the placement’s entire duration. You cannot continue”

N


  • Funding End Date: This is expected to be left NULL for all posts who have long-term, established funding, i.e. there is no known or expected ending to the funding of this post. If a post needs to be discontinued in terms of funding, this field is then filled in with the relevant date

https://hee-tis.atlassian.net/browse/TIS21-4801

  • A post’s funding dates should cover the entire duration of a placement. A warning message to prompt users to double check this should improve data quality. Where there is no funding end date the post should be considered to be actively funded indefinitely.

https://hee-tis.atlassian.net/browse/TIS21-2687

This is new field to be created;

Sub-category

To be created

None because it is a new filed to be created.

  • HEE Funded - Non-Tariff:

  1. Salary recharges

  2. Dental – 50%

  3. Dental - 100%

  4. FY2GP

  5. Public Health

  6. Hospice or Charity

  7. Occupational Medicine

  8. Community setting

  9. Foundation academic

  10. Other post funding

  • Supernumerary:

  1. Exceptional training

  2. SRTT

  3. Salary recharges


None because it is a new filed to be created.

  • Sub category appears ONLY If you select ‘HEE Funded- Non-Tariff’ OR ‘Supernumerary’ from the ‘Funding type’ dropdown list.

  • Type: Drop down

  • Mandatory: ? ( using TIS UI or Post bulk upload) Please check with stakeholder if this new field should be mandatory

  • Default to: NULL

  • Editable: NO

To be updated after implementation




Funding Type Sub-category

https://hee-tis.atlassian.net/browse/TIS21-4803

This is new field to be created;

Funding Reason

To be created

None because it is a new filed to be created.

  • Long Term Plan

  • Redistribution

  • Expansion Posts

  • Cancer and Diagnostics


None because it is a new filed to be created.

  • Funding Reason appears ONLY If you select any item from the ‘Funding type’ dropdown list

  • Type: Drop down

  • Mandatory: No ( using TIS UI or Post bulk upload)

  • Default to: NULL

  • Editable: No

To be updated after implementation




Funding Type- Funding reason;

https://hee-tis.atlassian.net/browse/TIS21-4804

Post Funding Bulk Upload (Post Funding Creation) Fields Validation:


Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4803

Column Heading

Add/Update/Matching Criteria

Mandatory

Rules

Questions/Notes for discussions

TIS_Post_ID*

Matching Criteria

Y

  • Should validate if the post funding is under this post ID

Funding type

Add

Y

  • Accepted values should match to one of Funding Type reference table and are CURRENT. 

Funding Details

Add

N

Funding Body

Add

N

  • Accepted values should match to one of

Funding Type
  • the 'TrustKnownAs' from ‘Trust’ reference table and are

CURRENT. 
  • Cannot be left blank on the template, if one of 20-22 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.
  • 19Funding type - If 'Other' please specifyAddN

    Free text

    • Only use when Funding Type = Other
    20Funding Body
    • CURRENT

    Funding subtype

    Add

    N

    • Accepted values should match to one of

    the TrustKnownAs from Trust
    • Funding subtype reference table and are CURRENT

    21
    • Only allow funding subtype which is allowed by the funding type.

    • Error message should read ‘Funding subtype "xxxx" does not match funding type "yyyyyy".’

    Date From

    Add

    N22

    Y

    • Date format DD/MM/YYYY

     

    • Date to should not be the same or before the Date from If date to is not NULL

    Date to

    Add

    N

    Date format DD/MM/YYYY

    Post

    ...

    Funding Bulk Upload (Post Funding Update) Fields Validation

    Jira Legacy
    serverSystem JIRA
    serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
    keyTISNEW-3248

    Ashley Ransoo and Alistair Pringle (Unlicensed) to run through with Data leads / stakehoders.

    ...

    -66091fcfe3c7
    keyTIS21-4803

    Note: If non-mandatory fields are blank, retain existing value

    Column Heading

    Add/Update/Matching Criteria

    Mandatory

    Rules

    Questions/Notes for discussions

    1

    TIS_

    PostFunding

    Post_ID*

    Matching Criteria

    Y

    • Should

    match to one of TIS_PostFundingID's2
    • validate if the post funding is under this post ID

    TIS_PostFunding_ID*

    Matching Criteria

    Y

    • Should validate if the post funding is under this post ID

    Funding type

    Update

    N

    • Accepted values should match to

    one of Funding Type reference table and are CURRENT. 
  • Cannot be left blank on the template, if one of 20-22 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.
  • 3Funding type - If 'Other' please specifyUpdateN

    Free text

    • Only use when Funding Type = Other
    4Funding Body
    • one of Funding Type reference table and are CURRENT. 

    Funding Details

    Update

    N

    Funding Body

    Update

    N

    • Accepted values should match to one of the 'TrustKnownAs' from ‘Trust’ reference table and are CURRENT

    Funding subtype

    Update

    N

    • Accepted values should match to one of

    the TrustKnownAs from Trust
    • Funding subtype reference table and are CURRENT

    5
    • Only allow funding subtype which is allowed by the funding type.

    • Error message should read ‘Funding subtype "xxxx" does not match funding type "yyyyyy".’

    Date From

    Update

    N

    • Date format DD/MM/YYYY

     

    6
    • Date to should not be the same or before the Date from If date to is not NULL

    Date to

    Update

    N

    • Date format DD/MM/YYYY