Property & Compliance Management

Resend the latest notification for a record

Use the record-level action to resend only the latest applicable notification.

Reviewed 27 October 2026Merged module 2.1.3
Where to goCompliance → Core Compliance → Notification / Intimation Engine

Before you start

Compliance View opens the workspace; Create is used for new intake, Edit for review/approval and Delete for deletion. Each action also validates its record.

Follow these steps

  1. Go to the compliance record.
  2. Check the latest notification reference and stage.
  3. Verify it is the message that should be repeated.
  4. Run the latest-notification resend action.
  5. Check the new or updated log state in the notification engine.

Fields, rules and limits

  • Review the recipient delivery ledger before repeating a run. A record or PDF may already exist even when one recipient failed. Retry the failed delivery rather than creating a duplicate compliance record.

Check it worked

The linked entity, saved state, dates and evidence match the intended task.

If something does not look right

If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.

Questions and answers

Does a parsed document count as approved?

No. Parsing supplies suggested values. A reviewer must verify the linked entity, evidence and required fields, then use the separate approval action.

Is the generated PDF the original certificate?

No. The system PDF reflects the saved compliance record or notification. Open the original source evidence separately when checking the document supplied.