Complete the client Outcome required field
Describe the intended licence outcome. 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.
Where to goClient Portal → Licence Applications → New Application → Outcome required
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What you’ll accomplish
Describe the intended licence outcome. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Sign in and open New Application.
- Find Outcome required.
- Enter or select the required value.
- Complete the remaining required fields.
- Submit and verify the created case.
Fields and options to review
FieldOutcome required
Payload keyoutcome_required
Supported valueRequired
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-client-application/
Rules the system enforces
- Describe the intended licence outcome.
- The portal controller uses this field when constructing the stored application or application summary.
How to confirm it worked
- Complete the client Outcome required field completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Use the least-privilege account that has the stated permission.
- Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.