Understand immutable proposal hashing
This guide explains that each uploaded PDF receives a SHA-256 hash for version evidence. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Full Compliance Applications → Case → Proposal
Before you start
- Verify 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 you’ll accomplish
Recognise that each uploaded PDF receives a SHA-256 hash for version evidence. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to Admin Area → Full Compliance Applications → Case → Proposal.
- Find the relevant record, setting or action on the page. Use the record name, reference, current status and surrounding details to make sure you are working on the intended item.
- Complete each field or control that applies to this task. Keep verified existing values intact, supply required information, and resolve any validation message before moving on.
- Use the primary action shown by the workflow—such as Save, Submit, Update, Call, Sign, Upload or Confirm. Submit once, then allow the request to finish before taking another action.
- Reopen the related register, portal, dashboard or call panel. Verify the status, visible values and any audit, activity, document, call or notification evidence created by the action.
Fields and options to review
Proposal workflowRecognise that each uploaded PDF receives a SHA-256 hash for version evidence.
Rules the system enforces
- The proposal belongs to the case and selected client contact.
- Accepted and superseded evidence remains version-specific.
How to confirm it worked
- The understand immutable proposal hashing 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
- Validate the change with a controlled test case, contact, extension or approved website origin before relying on it in production.
- Grant only the permissions needed for the task, and keep private documents, call metadata, signing evidence, API credentials and infrastructure paths restricted to authorised users.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.