-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement logic for Application Event Code in IER12 #2289
Comments
Qn 1:
|
Qn 2:
|
Application event codes, RECA, COEM, DISP is not considered for the ticket/not in the scope, that's why it is marked as grey. |
For, |
For, |
Removed below AC -
|
Questions on application status codes and IER
(Answers below are based on discussion with @JasonCTang and @HRAGANBC )
COER vs DISR status: When a disbursement has a coe which is waiting for approval from institution and assume that the coe has not been approved until disbursement_date and the student has restriction. With this situation should we return COER or DISR ? - Answer: COER as per @HRAGANBC
Consider a disbursement which has been sent to finastra and this disburesment had some funds withheld due to restriction at the time of e-cert generation(DISW). After the disbursement is sent to finastra we got disbursement feedback errors(DISE). should we return DISW or DISE ? - Answer: DISE
Should DISW and DISE override DISS ? - Answer: Yes
Describe the task
Implementation of Application event code and Application event date for IER 12. For reference Please use the spreadsheet from General > Files >Analysis > Institution File Specs > IER12_Analysis_Output_and_Mapping_Part_1_V2.xlsx
Private Zenhub Image
Additional context
List of validations which needs to be in place to derive application status code
Validation: Check if an application has more than one submission.
Logic:
select count(id) from sims.applications a where a.application_number = '$APPLICATION_NUMBER'
Validation: Check if the disbursement has any feedback error
Logic: Check the
sims.disbursement_feedback_errors
feedback table for one or more errors which belongs to given list of FT Error codes.FT Error codes: Ecert Error Codes and Descriptions External.xlsx (this is only FT codes)
Validation: Check if disbursement is not sent due to restriction
Logic: Check if the student has any active restriction of action type 'Stop full time disbursment' and disbursement date is after cutoff date (current date + 5)
Validation: Check if any disbursement award was withheld due to restriction
Logic: Check if the restriction_amount_subracted > 0
Logic to derive the application event code from application and assessment data.
Note: BPMN diagram is used only explain the logic, it is not considered as solution for implementation.
Private Zenhub Image
Source BPMN file(for making updates) : application-event-code.bpmn.txt
Logic to derive application event date (As per discussion with @JasonCTang )
Note: BPMN diagram is used only explain the logic, it is not considered as solution for implementation.
Private Zenhub Image
Source BPMN: application-event-date.bpmn.txt
Acceptance Criteria
Application event code
[Application event codes, RECA, COEM, DISP is not considered for the ticket/not in the scope, that's why it is marked as grey.]Application event date
The text was updated successfully, but these errors were encountered: