credit-registration-admin

POST `/api/v0/main-frontend/credit-registration-admin/registrations/{credit_registration_id}/transition` - Moves one row by hand. The escape hatch out of `submission_uncertain`, which the pipeline never leaves on its own because re-importing could put a second attainment on a real transcript. Even here, a row is not resubmitted while Suotar may still hold its earlier submission as pending (`submission_uncertain_too_recent`, `submission_pending`). The row's `hand_actions` says in advance what this refuses.

Changed on
post/api/v0/main-frontend/credit-registration-admin/registrations/{credit_registration_id}/transition

Request

  • The document declares no server URL.
  • Auth: none declared

Path parameters

credit_registration_idstring uuid required

Credit registration id

Request body

reasonstring required

Response

What the transition did

needs_admin_attentionboolean required
outcome'applied' | 'refused' | 'no_change' required
refusal'superseded' | 'already_succeeded' | 'submission_uncertain' | 'submission_uncertain_too_recent' | 'not_failed_permanent' | 'still_in_pipeline' | 'submission_pending' | 'already_submitted' | 'awaiting_confirmation' | 'already_cancelled' | 'nothing_to_check'

Why [ResubmissionFacts] refuses a hand action on a row.

Rendered by the teacher and admin surfaces, which decide from it which buttons a row gets, so it travels to them as it is rather than being re-mapped per surface.

state'pending' | 'ready_to_submit' | 'resolving_enrolment' | 'checking_enrolment' | 'no_usable_enrolment' | 'submitting' | 'submission_uncertain' | 'awaiting_verification' | 'partially_registered' | 'registered' | 'duplicate' | 'not_improved' | 'misregistered' | 'failed_retryable' | 'failed_permanent' | 'blocked' | 'cancelled' required

What the pipeline does next with a ledger row.

Changes

    • ●

      added the new already_cancelled enum value to the //// response property for the response status

    • ●

      added the new awaiting_confirmation enum value to the //// response property for the response status

    • ●

      added the new nothing_to_check enum value to the //// response property for the response status

    • ●

      added the new still_in_pipeline enum value to the //// response property for the response status

    • ●

      added the new submission_uncertain_too_recent enum value to the //// response property for the response status

    • ●

      added the new partially_registered enum value to the response property for the response status