Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 12 Next »

Goals

  • Develop of the eligibility portion of the application

Requirements

#TitleUser StoryImportanceNotes
 Eligibility ScreenCoordinator will input this information for the ApplicantMust Have
 Form Fields

Campus

  • static field
  • value comes from campus on the APPLICATION table

Subject Area (info)

  • represents the faculty's discipline
  • this field is equivalent to Manoa's department field as detailed below
  • PeopleSoft value: eac_section_desc from edadba.psempl

Primary Department (info) (grey lightbulb)

  • PeopleSoft value: eac_branch_desc from edadba.psempl
  • Pull from record number 01

Primary College (info) (grey lightbulb)

  • PeopleSoft value: eac_division_desc from edadba.psempl
  • Pull from record number 01

Secondary Department (info) (grey lightbulb)

  • PeopleSoft value: eac_branch_desc from edadba.psempl
  • Pull from record number 02

Secondary College (info) (grey lightbulb)

  • PeopleSoft value: eac_division_desc from edadba.psempl
  • Pull from record number 02

Initial Appointment (can this information be pulled from PeopleSoft's historical tables?)

  • Classification (info)
    • use data from lookup data table
    • drop down options format: "code - description"
      • example: "C - Community Colleges"
    • PeopleSoft value: ?
  • Rank (info)
    • use data from lookup data table
    • drop down options format: "code - description"
      • example: "2 - Instructor"
  • Appointment Date (info)
    • date picker
    • PeopleSoft value: univ_appt_date from edadba.psempl
  • Appointment Type (info)
    • use data from lookup data table
    • drop down options format: "description"
      • example: "9 Month"

Current Appointment (Pull information from PeopleSoft)

  • Classification (info)
    • use data from lookup data table
    • drop down options format: "code - description"
      • example: "C - Community Colleges"
    • PeopleSoft value: 1st character of grade from edadba.psempl
  • Rank (info)
    • use data from lookup data table
    • drop down options format: "code - description"
      • example: "2 - Instructor"
    • PeopleSoft value: 2nd character of grade from edadba.psempl
  • Appointment Date (info)
    • date picker
    • PeopleSoft value: ?
  • Appointment Type (info)
    • use data from lookup data table
    • drop down options format: "description"
      • example: "9 Month"
    • PeopleSoft value: 4th and 5th characters of grade from edadba.psempl

Tenure Consideration

  • use data from lookup data table
  • drop down options format: "description"
    • example: "Appropriate"
  • Validation:
    • A file must be uploaded via the Memo field if "Appropriate" was NOT selected

Memo

  • If "Before Designated Year" is selected, the coordinator will upload the chancellor's approval for shortening the probationary period
  • If "After Designated Year" is selected, the coordinator upload the chancellor's approval for extending the probationary period
  • memo is completed prior to the T&P process
  • store file on server NOT google drive

Date of Tenure (info)

  • PeopleSoft value: tenure_effective_date from edadba.psempl
  • Pull from record number 01

Date of Last Promotion

Waiver of Minimum Requirements (grey lightbulb)

  • Upload file to Educational Requirement
  • Upload file to Service Requirement
  • waivers are obtained prior to the T&P process
  • store file on server NOT google drive
Must Have

(info) - prefill information from PeopleSoft via the HR Datamart when the application is created

(grey lightbulb) - hide for community colleges

User interaction and design

 

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome
Is the Tenure Consideration field required?yes
Does the Coordinator need to upload a document of Chancellor's approval?yes



  • No labels