Use status: Awaiting External

Select Awaiting External; its code-backed default progress is 75%. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

What you’ll accomplish

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

Follow these steps

1. Go to Admin Area → Projects & Work → Service Journeys → Application → Status Control.
2. Find the record, endpoint, field or action used to use status: awaiting external.
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 and options to review

Rules the system enforces

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

How to confirm it worked

• The use status: awaiting external 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.

Continue with related guidance