Update portfolio-review status
Choose Pending, Completed or Not required after the consultation gate is satisfied.
Exact navigationAdmin Area → Full Compliance Applications → Case → Client journey → Portfolio-review status
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
Choose Pending, Completed or Not required after the consultation gate is satisfied. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Admin Area → Full Compliance Applications → Case → Client journey → Portfolio-review status.
- Locate the record, setting or action used to update portfolio-review status.
- Complete the displayed fields or controls exactly as described in this guide.
- Select the available save, submit, update, call, sign, upload or confirm action.
- Return to the related register, portal, dashboard or call panel and verify the recorded result.
Fields, choices and supported possibilities
Portfolio-review statusPending, Completed or Not required.
Client-visible portfolio-review noteMaximum 5,000 characters.
Code-backed validations and workflow rules
- Portfolio review cannot be completed or marked not required until consultation is Completed or Not required.
Expected result and verification
- The update portfolio-review status workflow completes without a validation, permission or availability error.
- The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
- Any client-visible or public result appears only where the code explicitly allows it.
Security, privacy and operational checks
- Use a controlled test case, contact, extension or website origin before production rollout.
- Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.