Category: Apex Property Operations
-
In this example from the Apex Property Operations developer org, Salesforce enforces required permissions when changing Case ownership. When a Field Operative user does not have the necessary read access on the Case and related records (Account/Contact), Salesforce prevents the transfer. This behavior underscores an important admin principle: object-level permissions must be aligned with record…
-
1️⃣ Project Overview Goal:Design a secure, role-based service workflow for a property operations company using Salesforce, ensuring users only see and act on records relevant to their role. Initial Scope: Outcome:A more robust solution involving custom objects, permission sets, custom permissions, and role-specific Lightning apps. While Cases were appropriate for tracking customer issues, assigning operational…
-
Why this mattered: During the Apex Property Operations project, I needed different user roles (Admin, Operations Manager, Field Operative, Finance User) to: Profiles alone couldn’t solve this — and page layouts definitely couldn’t. This is where Custom Permissions + Dynamic Visibility became the right tool. Constraint 1: Same profile, different access All non-admin users were…
-
What a “blank app” actually means in Salesforce When you log in as a Platform User and see: “Well, this is awkward. This app doesn’t have any navigation items, or you can’t access them.” Salesforce is saying: “I looked at the app’s nav items, checked your object + tab permissions, and you’re not allowed to…
-
1. Context: The Temptation of a Validation Rule During the Apex Property Operations project, I needed to ensure that every Work Order always referenced the correct Property. At first glance, this looked like a textbook use case for a validation rule: Technically, this would have enforced correctness. But as the solution evolved, it became clear…
-
Project Overview What this project was about In the Apex Property Operations system, Work Orders are created from Maintenance Requests.Each Maintenance Request already has a related Property, but Salesforce still allows users to manually select a Property when creating a Work Order. This led to a recurring problem: The goal of this project was to…
-
1. The Requirement That Looked Simple In the Apex Property Operations project, the original requirement sounded straightforward: Ensure Work Orders always reference the correct Property. On paper, this felt like something a single Flow could handle. In practice, the moment I started building, it became clear that trying to force everything into one Flow would…