Delete a client buy request
Use the portal delete action only when the request state permits it.
Exact navigationClient Portal → Real Estate → Buy Application → Delete
Before you begin
- Use an account with Authenticated owning client contact and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What this guide covers
Use the portal delete action only when the request state permits it. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Client Portal → Real Estate → Buy Application → Delete.
- Open the exact record and review linked documents, payments, approvals, files and portal visibility.
- Choose the supported Delete, Remove, Void or Cancel action.
- Confirm the action only after checking the consequence described below.
- Return to the list and verify whether the record was removed, retained with a status, or blocked by a code-backed restriction.
Fields, choices and supported possibilities
Exact actionDelete a client buy request
Exact navigationClient Portal → Real Estate → Buy Application → Delete
Module version1.0.0
Access ruleAuthenticated owning client contact
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Request recordCode, client, property/item, request type, currency, property price, term and inspection choice.
Notes and billingClient note, admin note and billing/shipping data where the form exposes them.
ConversionReview status and linked customer/property before converting to a contract or invoice.
Code-backed validations and workflow rules
- The client controller validates ownership and current status.
- Buy and rent requests use separate real_buy_request and real_rent_request capability groups.
- Status changes and conversion actions validate the current request and linked record IDs.
Expected result and verification
- The supported delete a client buy request flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.