CHAPTER 1: The Salesforce Lightning Platform Governance Method
The content of this Chapter introduces the reader to the concepts of governance and how they need to construct their teams and processes to facilitate governance within their organisation. Additionally, the structure of our governance method is described, which sets the structure for the remainder of the book. The book is essentially split into two sections. The first section is the governance method, whilst the second section is the resources needed to perform the governance.
Resource Base
Key Points
Basic Structure
Adapting the SLPGM
Architecture Governance
Process Management
Scoping the Application Governance Cycle Platform Team
CHAPTER 2: Application Architecture (Phase A)
Describes the method by which the application architecture is governed on the Salesforce platform. Areas covered are general architecture, localisation and global deployments, workflow and process, formulas and files and social.
Objectives
Approach
Inputs
Steps
Outputs
CHAPTER 3: Data Architecture (Phase B)
Describes the method by which the data architecture is governed. Areas covered are design and data optimization, performance, predictive and actual data volumes and data movement. Objectives
Approach
Inputs
Steps
Outputs
CHAPTER 4: Identity & Access Management (Phase C)
This Chapter will focus on the governance of the identity and access management aspects of the application and Salesforce platform. These will form part of the technical standards and policies, but it is possible for an application to seek changes to these. For example, A Connected App (external to Salesforce) may be required that can only support a specific authentication solution, which is not part of the technical standards.
Objectives
Approach
Inputs
Steps
Outputs
CHAPTER 5: Sharing & Visibility (Phase D)
The Salesforce platform is very flexible and as such allows a "developer" to create applications with very little development experience. Obviously the more experience the developer, the more comprehensive the application can be. Salesforce has specifically focused on the ability to create applications and change configuration through "clicks", negating in the majority of cases the need to actually write "code". Creating applications and changing configuration via "clicks" is known as Declarative and the Salesforce platform has provided a significant amount of functionality and tailoring capability just through the declarative route. Declarative changes are stored in the metadata of the Org, and as such can be extracted (there are some limitations) and therefore analysed and governed. The approach to this phase is to describe how to take those declarative changes and assess them against the technical standards and policies. Objectives
Approach
Inputs
Steps
Outputs
CHAPTER 6: Integration (Phase E)
Salesforce provides numerous solutions to integration and the right solution will very much depend upon what the requirements are that underpin the integration. However, fundamentally this phase is looking to compare the integration techniques that are part of the technical standards and policies with those that have been used. Then, determine those that have been used, have they been used correctly. Objectives
Approach
Inputs
Steps
Outputs
CHAPTER 7: Apex, Visualforce & Lightning (Phase F)
On a shared platform, it is important that every developer takes ma
