Complete the client Outcome required field
Describe the intended licence outcome.
Exact navigationClient Portal → Licence Applications → New Application → Outcome required
Before you begin
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Confirm 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 this guide covers
Describe the intended licence outcome. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Sign in and open New Application.
- Locate Outcome required.
- Enter or select the required value.
- Complete the remaining required fields.
- Submit and verify the created case.
Fields, choices and supported possibilities
FieldOutcome required
Payload keyoutcome_required
Supported valueRequired
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-client-application/
Code-backed validations and workflow rules
- Describe the intended licence outcome.
- The portal controller uses this field when constructing the stored application or application summary.
Expected result and verification
- 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.