Proposal versions, delivery and verified signatures

Process a declined proposal

Record the declined version/document, timeline event, landlord action and professional notifications.

Audience: Compliance administrators, consultants, landlords and authorised client contactsPermission: EditModule v1.0.0
Exact navigationAdmin Area → Full Compliance Applications → Case → Proposal
Before you begin
  • Confirm the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What this guide covers

Record the declined version/document, timeline event, landlord action and professional notifications. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Admin Area → Full Compliance Applications → Case → Proposal.
  2. Locate the record, setting or action used to process a declined proposal.
  3. Complete the displayed fields or controls exactly as described in this guide.
  4. Select the available save, submit, update, call, sign, upload or confirm action.
  5. Return to the related register, portal, dashboard or call panel and verify the recorded result.

Fields, choices and supported possibilities

Proposal workflowRecord the declined version/document, timeline event, landlord action and professional notifications.

Code-backed validations and workflow rules

  • The proposal belongs to the case and selected client contact.
  • Accepted and superseded evidence remains version-specific.

Expected result and verification

  • The process a declined proposal workflow completes without a validation, permission or availability error.
  • The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
  • Any client-visible or public result appears only where the code explicitly allows it.

Security, privacy and operational checks

  • Use a controlled test case, contact, extension or website origin before production rollout.
  • Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.