Logical Operators

Boolean isActive = true;
Boolean hasBalance = false;

Boolean canPurchase = isActive && hasBalance;   // false — both must be true
Boolean needsReview = isActive || hasBalance;    // true — at least one is true
Boolean isInactive = !isActive;                  // false — flips isActive

1. Boolean isActive = true; — one starting fact.
2. Boolean hasBalance = false; — another starting fact.
3. (blank line)
4. Boolean canPurchase = isActive && hasBalance; — && (AND) needs both sides true — since hasBalance is false, the whole expression is false.
5. Boolean needsReview = isActive || hasBalance; — || (OR) needs at least one side true — isActive alone makes this true.
6. Boolean isInactive = !isActive; — ! (NOT) flips a Boolean — !true is false.

Boolean policyIsActive = true;
Integer daysUntilExpiry = 15;

Boolean needsRenewalReminder = policyIsActive && daysUntilExpiry <= 30;
System.debug(needsRenewalReminder); // true

1. Boolean policyIsActive = true; — one fact about the policy.
2. Integer daysUntilExpiry = 15; — another fact.
3. (blank line)
4. Boolean needsRenewalReminder = policyIsActive && daysUntilExpiry <= 30; — combines a Boolean and a comparison with &&: both "is active" and "expiring within 30 days" must be true.
5. System.debug(needsRenewalReminder); — logs true, since both conditions hold.

Real business rules are almost always compound like this — "active AND expiring soon" — which is exactly what && expresses directly in code.

Apex evaluates && and || left to right, and stops early when the answer is already certain: if the left side of && is false, Apex never bothers checking the right side, since the whole expression is already guaranteed false. This isn't just an optimization detail — it's sometimes used deliberately, for example to safely check record != null && record.Amount > 100 without risking a null pointer error on the second condition.