Understand the generated portal application summary
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that how intake details are combined into application_summary.
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 this guide helps you do
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
Stored outputMain summary plus non-empty professional intake details
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-client-application/
Rules and limits
- The portal controller limits records to the current client ID.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.