Workflow Orchestration for Enrollment Changes and Graduation Eligibility: Compare Documents and Locate Differences

Graduation Eligibility: review workflows for document checks. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This page focuses on material verification and discrepancy localization in student status changes and graduation eligibility review, covering three types of materials: leave/resumption of study applications, major transfer applications, and graduation review checklists. Leave/resumption of study applications are usually submitted in semester batches, with fields including student ID, name, change type, effective date, and signature field; major transfer applications are accepted centrally by academic year, with fields including original major, target major, assessment conclusion, and receipt number; graduation review checklists are generated by graduation batch, with fields including course name, credits, grade, graduation conclusion, and review signature. The material sources are paper scans submitted by each college and system-exported tables, with an update rhythm that rolls with batches. When entering workflow orchestration, leave/resumption of study applications serve as the source materials to be compared, major transfer applications serve as associated supporting materials, and graduation review checklists serve as the ledger baseline materials; after the three are aligned by student ID and batch number, they enter the discrepancy localization step.

Configuration and implementation checks

This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "discrepancy list" is then completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.

ObjectCheckVerification action
Leave/resumption of study applicationWhether the change type, effective date, and signature of the same student ID are consistent across the two materialsCheck the options and branch connections one by one in the node, compare the change fields of the leave/resumption of study application and the graduation review checklist, and use variables to record the selection result
Major transfer applicationWhether the same record matches on original major, target major, assessment conclusion, and receipt numberTrigger a user selection node once, view the node status in the run record, and check the field discrepancies between the major transfer application and the ledger
Graduation review checklistWhether the same course name, credits, grade, and graduation conclusion are consistent across the two materialsReference the selection result variable in a subsequent node and run a trial once to locate the fields where the graduation review checklist and the ledger are inconsistent
Workflow nodeWhether each option corresponds to one branch, and whether execution continues downward after the interaction is completedCheck the options and branch connections one by one in the node, use nodeId to locate the node, and check the branch direction and interaction status in the run record

Three common errors

  • Symptom: The name, quantity, and date of the same record do not match across the two materials. Cause: The material source batches differ, the field definitions are not unified, and normalized mapping was not performed before entering the comparison.
  • Symptom: The versions are not synchronized; the ledger has been updated while the application materials are still the old version. Cause: The update rhythms are inconsistent, and there is a lack of version identifiers and timestamp comparison steps.
  • Symptom: Signatures or receipts are missing, and the material chain is incomplete. Cause: Omissions occurred in the submission step, and the signature field and receipt number were not included as mandatory fields during verification.

How to verify the setup

Feature acceptance: Run a trial for each option, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and that the process continues downward after the interaction is completed, and use variables and nodeId to locate the selection result and the node.

Business test: Use one real record to find the fields inconsistent with the ledger, align the leave/resumption of study application, major transfer application, and graduation review checklist by student ID, and compare field by field.

  • Align the three types of materials by student ID and batch number, and check the name, quantity, date, and signature field field by field.
  • Check the options and branch connections one by one in the node, and after triggering a user selection node once, view the node status in the run record.