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 2 Current »

JIRA reference: FT-587

Meeting notes: https://www.hawaii.edu/bwiki/display/FT/2021-02-04+Bi+Weekly+Meeting

High Level Requirements

Who: DPC Chair

What

  • Manoa applicants that can make edits to their dossier will follow a different workflow branch that rejoins the main workflow.
  • If Manoa and Applicant allowed to make edits flag = "Y" then follow this workflow
    • Submitted → DPC Feedback (123) → Awaiting Applicant (119) → Applicant Reviewing (120) → DPC Review (103)
  • Otherwise follow this workflow
    • Submitted →  DPC Review (103)

State table changes:

  • Add new state
    • id = 123
    • name = DPCFeedback
    • official_name = Under Review
    • simple_name = DPC Feedback
    • official_code = REVIEW
  • Remove state 121 DPCReviewSecondTime

Buttons:

  • label: "DPC Feedback Complete"
  • display for DPC Chair in the sub-banner 
  • popup:
    • By clicking Complete, the application will be sent to the applicant to make edits to their dossier based on the DPC feedback communicated to the applicant external to the system. No record of this feedback is captured in this system.

Application Tabs:

  • hide the Recommendations tab at this state 

Notifications:

  • functionals need to word smith based on feedback from DPC committees

Questions

  • Delete State 121 post implementation
    • Do we migrate recorded 121 states to a different state? Otherwise we need to keep the state in the database if it's being referenced.
  • (minus) what email gets sent from 102 → 123
  • No labels