Case control, ownership, status and progress

Use status: In Progress

Select In Progress; its code-backed default progress is 60%.

Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicantsPermission: EditModule v1.0.0
Exact navigationAdmin Area → Projects & Work → Service Journeys → Application → Status Control
Before you begin
  • Confirm the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What this guide covers

Select In Progress; its code-backed default progress is 60%. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Admin Area → Projects & Work → Service Journeys → Application → Status Control.
  2. Locate the record, endpoint, field or action used to use status: in progress.
  3. Complete the displayed values exactly as described in this guide.
  4. Select the available save, submit, send, upload, create, update or confirm action.
  5. Return to the related register, portal, activity log or API response and verify the expected result.

Fields, choices and supported possibilities

StatusIn Progress
Default progress60%
Progress override0–100 input is accepted by the status form.

Code-backed validations and workflow rules

  • Use Completed Successfully only when work is complete because it clears the outstanding badge count.

Expected result and verification

  • The use status: in progress workflow completes without a validation, permission, ownership or availability error.
  • The related record, portal view, activity entry, notification log or API response shows the expected state.
  • Client-visible, public and API data remains limited to the code-backed ownership and visibility rules.

Security, privacy and operational checks

  • Use controlled test records and non-production credentials before wider rollout.
  • Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs.