Understand event: Overdue reminder

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

The notification/audit layer recognises the Overdue reminder event.

What this guide helps you do

The notification/audit layer recognises the Overdue reminder event. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

1. Go to Admin Area → Projects & Work → Service Journeys → Application or CRM cron.
2. Find the record, endpoint, field or action used to understand event: overdue reminder.
3. Complete the displayed values exactly as described in this guide.
4. Select the available save, submit, send, upload, create, update or confirm action.
5. Return to the related register, portal, activity log or API response and verify the expected result.

Fields and options

Rules and limits

• Recipient and visibility rules depend on event direction and record flags.

Check it worked

• The understand event: overdue reminder workflow completes without a validation, permission, ownership or availability error.
• The related record, portal view, activity entry, notification log or API response shows the expected state.
• Client-visible, public and API data remains limited to the code-backed ownership and visibility rules.

Security, privacy and operational checks

• Use controlled test records and non-production credentials before wider rollout.
• Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs.

Related guides