Understand the generated portal application summary
This guide explains that how intake details are combined into application_summary. 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 → Submit
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
Know how intake details are combined into application_summary. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Complete the main summary and relevant intake fields.
- Submit.
- Go to the case and verify the combined professional summary.
Fields and options to review
Stored outputMain summary plus non-empty professional intake details
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-client-application/
Rules the system enforces
- The portal controller limits records to the current client ID.
How to confirm it worked
- Understand the generated portal application summary 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.