Salesforce daily archive
730 days of practical thinking.
One retrospective note for every day from 2 September 2024 to 1 September 2026.
Archive dates organise the subject history. They do not claim the notes were originally published on those dates.
Showing 244 archive entries
Page 6 of 11
Protecting the data contract: Data virtualisation
External data can sometimes remain in its source while Salesforce presents it at the point of work. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Transaction boundaries
Cross-system work cannot rely on one database transaction to guarantee an all-or-nothing outcome. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Idempotent integrations
A request may be delivered more than once; a dependable receiver must make repetition safe. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Error recovery
Failure handling is part of the business process, not a technical appendix added after the happy path. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: API boundaries
An API should expose a stable business capability rather than mirror a database or a single user interface. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Customer identity across systems
Identity resolution is the foundation of a coherent customer view across Salesforce and connected platforms. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Master data decisions
A connected estate needs a clear answer to which system is authoritative for each important business fact. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Event-driven Salesforce
Events allow systems to announce meaningful change without controlling every downstream reaction. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Synchronous or asynchronous
Timing is an architectural decision: a process should wait only when the immediate response genuinely changes the next action. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteProtecting the data contract: Integration ownership
Every integration needs an explicit owner for its business contract, data meaning and operational health. This retrospective daily note considers how meaning, validation and change control keep producers and consumers aligned.
Read daily noteObservability before production: Backup and recovery
Data protection requires tested recovery objectives, not only confidence that a backup exists. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Deployment observability
Delivery metrics should show whether change is becoming safer and faster, not merely count deployments. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Environment strategy
Each Salesforce environment should have a clear purpose, data posture and refresh rhythm. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Data-quality ownership
Data quality is an operating responsibility supported by technology, not a cleanup project owned only by administrators. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Flow governance
Flow makes automation accessible, which increases the need for shared design and lifecycle standards. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Permission-set strategy
A scalable access model grants capability through composable permission sets rather than profile sprawl. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Deprecation tracking
Retirements and end-of-support notices need the same visibility as new features. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Feature adoption decisions
New platform capability creates value only when it solves a prioritised business need and has an accountable owner. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Post-release validation
A successful deployment does not prove that every business journey works under production data and integrations. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Release communication
Users need to understand the few changes that affect their work, not receive a copy of the complete release notes. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Critical update review
Critical updates can change security or runtime behaviour and deserve ownership before enforcement dates arrive. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Seasonal regression testing
Regression testing should concentrate on high-impact journeys, custom automation and integration boundaries. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Sandbox preview planning
Preview sandboxes provide a controlled window to evaluate upcoming platform behaviour before production changes. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily noteObservability before production: Release readiness
Each seasonal Salesforce release is a change programme, even when most features are enabled automatically and safely. This retrospective daily note considers the signals and context required to support the capability once it is live.
Read daily note