Customer work, connected.

Help & supportMyAccount
Create and edit licence cases

Complete the Priority field

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to choose the operational priority. The code stores the selected text; it does not automatically reorder or escalate cases.

Audience: CRM staffPermission: Create or Edit Licence ApplicationsModule v1.0.0
Jump to steps
Where to goAdmin Area → Licence Applications → New/Edit Application → Priority
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

Choose the operational priority. The code stores the selected text; it does not automatically reorder or escalate cases. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

  1. Go to the new or edit case form.
  2. Find Priority.
  3. Enter or select the value described in this guide.
  4. Save the case.
  5. Reopen the case and verify the stored value.

Fields and options

FieldPriority
Payload keypriority
Supported valuenormal, urgent, high or low
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-create-edit/

Rules and limits

  • Choose the operational priority. The code stores the selected text; it does not automatically reorder or escalate cases.
  • Case editing writes this field to the application record unless a dedicated workflow rule is stated.

Check it worked

  • Complete the Priority 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page