Salesforce Platform Governance Method: A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Elektronisch E-Book |
| Sprache: | English |
| Veröffentlicht: |
Berkeley, CA
Apress L. P.
2022
|
| Schlagworte: | |
| Online-Zugang: | HWR01 |
| Beschreibung: | Description based on publisher supplied metadata and other sources |
| Beschreibung: | 1 Online-Ressource (399 Seiten) |
| ISBN: | 9781484274040 |
Internformat
MARC
| LEADER | 00000nmm a2200000zc 4500 | ||
|---|---|---|---|
| 001 | BV048920962 | ||
| 003 | DE-604 | ||
| 005 | 00000000000000.0 | ||
| 007 | cr|uuu---uuuuu | ||
| 008 | 230502s2022 |||| o||u| ||||||eng d | ||
| 020 | |a 9781484274040 |9 978-1-4842-7404-0 | ||
| 035 | |a (ZDB-30-PQE)EBC6897050 | ||
| 035 | |a (ZDB-30-PAD)EBC6897050 | ||
| 035 | |a (ZDB-89-EBL)EBL6897050 | ||
| 035 | |a (OCoLC)1301273680 | ||
| 035 | |a (DE-599)BVBBV048920962 | ||
| 040 | |a DE-604 |b ger |e rda | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-2070s | ||
| 082 | 0 | |a 658.812 | |
| 100 | 1 | |a Harding, Lee |e Verfasser |4 aut | |
| 245 | 1 | 0 | |a Salesforce Platform Governance Method |b A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform |
| 264 | 1 | |a Berkeley, CA |b Apress L. P. |c 2022 | |
| 264 | 4 | |c ©2022 | |
| 300 | |a 1 Online-Ressource (399 Seiten) | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b c |2 rdamedia | ||
| 338 | |b cr |2 rdacarrier | ||
| 500 | |a Description based on publisher supplied metadata and other sources | ||
| 505 | 8 | |a Intro -- Table of Contents -- About the Authors -- About the Technical Reviewer -- Acknowledgments -- Introduction -- Chapter 1: Salesforce Platform Governance Method -- Overview -- The Method -- The Resource Base -- Key Points -- Basic Structure -- Method Adaption -- Architecture Governance -- Process Management -- Scoping the Application Governance Cycle -- Summary -- Chapter 2: Application Architecture: Phase A -- Overview -- General Architecture -- Localization / Global Deployments -- Workflow & -- Processes -- Formulas -- Files & -- Social -- Method -- Approach -- Inputs -- Steps -- General Architecture -- Localization & -- Global Deployments -- Workflow & -- Processes -- Formulas -- Files & -- Social -- Outputs -- Scenario -- Summary -- Chapter 3: Data Architecture & -- Management: Phase B -- Overview -- Design & -- Optimization -- Data Movement -- Method -- Approach -- Inputs -- Steps -- Design and Optimization -- Data Movement -- Outputs -- Scenario -- Summary -- Chapter 4: Identity & -- Access Management: Phase C -- Overview -- Single Sign-On -- Identity Management -- Method -- Approach -- Inputs -- Steps -- Single Sign-On -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 5: Sharing & -- Visibility: Phase D -- Overview -- Declarative Sharing -- Govern the core declarative platform features that are used to meet record-level, object, and field-sharing requirements -- Organization-Wide Defaults (OWDs) -- Profile-level object settings -- Permission set-level object settings -- Record ownership -- Manual sharing -- Govern the use of team functionality to meet business requirements -- Role hierarchies -- Teams (accounts, case, and opportunity) -- Queues -- Manager groups -- Govern list view, report folder, and dashboard folder security -- List view security | |
| 505 | 8 | |a Report folder and dashboard folder security -- Legacy folder sharing -- Enhanced folder Sharing -- Govern implicit sharing within the platform -- Implicit sharing -- Master-detail relationship -- Account relationship data sharing -- Govern the appropriate sharing design for the various community user types -- Sharing sets -- Sharing groups -- Super user access -- External account hierarchy -- Govern the application of territory management -- Programmatic Sharing -- Govern the core programmatic platform security features that have been used to meet sharing requirements -- Enforcing sharing rules -- Enforcing object and field permissions -- Enforcing SOQL data filtering -- Class security -- Apex-managed sharing -- Govern the security risks in programmatic customizations relative to data visibility, focus on difference in capabilities between programmatic sharing for standard vs. custom objects -- Performance -- Govern whether the solution is scalable to and maintainable at enterprise levels -- Data Security -- Govern any specific secured data implementation on the Salesforce platform -- Govern the use of "classic" encryption fields in the Salesforce platform and the limitations that need to be taken into consideration -- Method -- Approach -- Inputs -- Steps -- Declarative Sharing -- Programmatic Sharing -- Performance -- Data Security -- Outputs -- Scenario -- Summary -- Chapter 6: Integration: Phase E -- Overview -- Technologies & -- Overall Integration Strategy -- Govern the enterprise integration landscape and overall integration strategy, with associated risks, trade-offs, and business and technical considerations -- Govern the data backup/archiving/data warehousing integration strategies -- Govern whether the appropriate integration strategy and standard integration patterns have been used | |
| 505 | 8 | |a Govern the integration components involved in a flow and consider transaction management and error and exception handling -- Integration Solution Tools -- Govern the use of the appropriate platform-specific integration technology for integration with external systems -- Remote Process Invocation - Request and Reply -- Remote Process Invocation - Fire and Forget -- Batch Data Synchronization -- Remote Call-in -- UI Update Based on Data Changes -- Data Virtualization -- Govern the usage of the Lightning platform integration APIs and features and determine whether they have been appropriately used -- Security -- Govern how security requirements are met at each of the integration layers -- Method -- Approach -- Inputs -- Steps -- Technologies and Overall Integration Strategy -- Integration Solution Tools -- Security -- Outputs -- Scenario -- Summary -- Chapter 7: Apex, Visualforce & -- Lightning: Phase F -- Overview -- Visualforce -- Apex -- Lightning Components -- Design and Functionality -- Govern the continuum of UI options actually used against those available on the platform (buttons, mashups, Canvas, Visualforce pages, and Lightning components) -- Govern the sharing and visibility model in code solution -- Govern the code against security best practices to ensure all Visualforce and Apex code is developed per OWASP standards -- Govern the object-oriented design principles and design patterns that were adhered to when developing the solution (Singleton, etc.) -- Govern the appropriate use of the Model-View-Controller pattern -- Govern any Apex controllers against the technical standards (extensions to standard controllers and custom controllers) -- Govern the usage of custom settings and synchronous vs. asynchronous patterns, and all the available execution contexts (e.g., batch, trigger, callout, etc.) | |
| 505 | 8 | |a Govern the usage of batch Apex and the flex queue -- Govern the Apex / Visualforce solution against the governor limits -- Govern the order of execution of transactions within the platform (specifically against pre-existing triggers) -- Govern the quality of test coverage (required for production deployment, call-out testing is a special case) -- Govern the approach to error/exception handling -- Performance and Scalability -- Govern that performance and scalability best practices have been considered within Visualforce pages and Apex code (performance profiling, use of static resources) -- Govern the Apex and Visualforce performance to include LDV scenarios (Pagination, JavaScript remoting) -- Govern the use of external web technologies and complementary UI technologies -- Maintainability and Reuse -- Govern multi-language support and determine the appropriate solution has been used to support globalization -- Govern the options and techniques used to make programmatic components maintainable and reusable on the platform (custom settings, skeleton templates, custom metadata types) -- Method -- Approach -- Inputs -- Steps -- Design and Functionality -- Performance and Scalability -- Maintainability and Reuse -- Outputs -- Scenario -- Summary -- Chapter 8: Communities: Phase G -- Overview -- Design -- Govern the license types associated with the sites and communities -- Govern the sharing usage for partner, customer, and employee community users -- The project team has planned its sharing model -- The project team has defined its sharing requirements -- The project team has determined the sharing options it should use -- The project team has updated its sharing requirements with the sharing option it will implement -- Govern the different UI / UX capabilities to style a community -- Govern the mobile considerations for communities | |
| 505 | 8 | |a Identity Management -- Govern how identity management is handled within communities: provisioning, syncing, and de-provisioning -- Govern the use of external identity (Facebook, Google, etc.) if appropriate -- Method -- Approach -- Inputs -- Steps -- Design -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 9: Mobile Solutions Architecture: Phase H -- Overview -- Mobile Strategy and Design -- Govern the mobile solution for use of the appropriate mobile platform: HTML5, Native (iOS / Android), hybrid solutions, or Salesforce mobile app -- Govern the authentication / authorization (including SSO), offline storage, and sync requirements -- Govern the use of Salesforce mobile app declarative design -- Mobile Security -- Govern how the project has secured the mobile application and its data, including offline data encryption -- Method -- Approach -- Inputs -- Steps -- Mobile Strategy and Design -- Mobile Security -- Outputs -- Scenario -- Summary -- Chapter 10: Development Lifecycle & -- Deployment: Phase I -- Overview -- Development Lifecycle -- Govern the development and release of applications on the Salesforce platform -- Govern the testing strategies and test plan -- Deployment Techniques and Considerations -- Govern the deployment strategy and the platform tools, use cases, limitations, and best practices for environment management and data migration strategy -- Govern the tools (source control and continuous integration for release management) -- Method -- Approach -- Inputs -- Steps -- Development Lifecycle -- Deployment Techniques and Considerations -- Outputs -- Scenario -- Summary -- Chapter 11: Resource Base Introduction -- How to Use the Resource Base -- The Resource Base Structure -- The GitHub Repository -- A Final Word -- Chapter 12: Application Architecture (Phase A) Resource Base -- Guidelines and Best Practices | |
| 505 | 8 | |a General Architecture | |
| 650 | 4 | |a Salesforce (Online service) | |
| 650 | 4 | |a Sales management | |
| 650 | 4 | |a Customer relations-Management | |
| 700 | 1 | |a Bayliss, Lee |e Sonstige |4 oth | |
| 776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe |a Harding, Lee |t Salesforce Platform Governance Method |d Berkeley, CA : Apress L. P.,c2022 |z 9781484274033 |
| 912 | |a ZDB-30-PQE | ||
| 999 | |a oai:aleph.bib-bvb.de:BVB01-034185053 | ||
| 966 | e | |u https://ebookcentral.proquest.com/lib/hwr/detail.action?docID=6897050 |l HWR01 |p ZDB-30-PQE |q HWR_PDA_PQE |x Aggregator |3 Volltext | |
Datensatz im Suchindex
| _version_ | 1804185102879555584 |
|---|---|
| adam_txt | |
| any_adam_object | |
| any_adam_object_boolean | |
| author | Harding, Lee |
| author_facet | Harding, Lee |
| author_role | aut |
| author_sort | Harding, Lee |
| author_variant | l h lh |
| building | Verbundindex |
| bvnumber | BV048920962 |
| collection | ZDB-30-PQE |
| contents | Intro -- Table of Contents -- About the Authors -- About the Technical Reviewer -- Acknowledgments -- Introduction -- Chapter 1: Salesforce Platform Governance Method -- Overview -- The Method -- The Resource Base -- Key Points -- Basic Structure -- Method Adaption -- Architecture Governance -- Process Management -- Scoping the Application Governance Cycle -- Summary -- Chapter 2: Application Architecture: Phase A -- Overview -- General Architecture -- Localization / Global Deployments -- Workflow & -- Processes -- Formulas -- Files & -- Social -- Method -- Approach -- Inputs -- Steps -- General Architecture -- Localization & -- Global Deployments -- Workflow & -- Processes -- Formulas -- Files & -- Social -- Outputs -- Scenario -- Summary -- Chapter 3: Data Architecture & -- Management: Phase B -- Overview -- Design & -- Optimization -- Data Movement -- Method -- Approach -- Inputs -- Steps -- Design and Optimization -- Data Movement -- Outputs -- Scenario -- Summary -- Chapter 4: Identity & -- Access Management: Phase C -- Overview -- Single Sign-On -- Identity Management -- Method -- Approach -- Inputs -- Steps -- Single Sign-On -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 5: Sharing & -- Visibility: Phase D -- Overview -- Declarative Sharing -- Govern the core declarative platform features that are used to meet record-level, object, and field-sharing requirements -- Organization-Wide Defaults (OWDs) -- Profile-level object settings -- Permission set-level object settings -- Record ownership -- Manual sharing -- Govern the use of team functionality to meet business requirements -- Role hierarchies -- Teams (accounts, case, and opportunity) -- Queues -- Manager groups -- Govern list view, report folder, and dashboard folder security -- List view security Report folder and dashboard folder security -- Legacy folder sharing -- Enhanced folder Sharing -- Govern implicit sharing within the platform -- Implicit sharing -- Master-detail relationship -- Account relationship data sharing -- Govern the appropriate sharing design for the various community user types -- Sharing sets -- Sharing groups -- Super user access -- External account hierarchy -- Govern the application of territory management -- Programmatic Sharing -- Govern the core programmatic platform security features that have been used to meet sharing requirements -- Enforcing sharing rules -- Enforcing object and field permissions -- Enforcing SOQL data filtering -- Class security -- Apex-managed sharing -- Govern the security risks in programmatic customizations relative to data visibility, focus on difference in capabilities between programmatic sharing for standard vs. custom objects -- Performance -- Govern whether the solution is scalable to and maintainable at enterprise levels -- Data Security -- Govern any specific secured data implementation on the Salesforce platform -- Govern the use of "classic" encryption fields in the Salesforce platform and the limitations that need to be taken into consideration -- Method -- Approach -- Inputs -- Steps -- Declarative Sharing -- Programmatic Sharing -- Performance -- Data Security -- Outputs -- Scenario -- Summary -- Chapter 6: Integration: Phase E -- Overview -- Technologies & -- Overall Integration Strategy -- Govern the enterprise integration landscape and overall integration strategy, with associated risks, trade-offs, and business and technical considerations -- Govern the data backup/archiving/data warehousing integration strategies -- Govern whether the appropriate integration strategy and standard integration patterns have been used Govern the integration components involved in a flow and consider transaction management and error and exception handling -- Integration Solution Tools -- Govern the use of the appropriate platform-specific integration technology for integration with external systems -- Remote Process Invocation - Request and Reply -- Remote Process Invocation - Fire and Forget -- Batch Data Synchronization -- Remote Call-in -- UI Update Based on Data Changes -- Data Virtualization -- Govern the usage of the Lightning platform integration APIs and features and determine whether they have been appropriately used -- Security -- Govern how security requirements are met at each of the integration layers -- Method -- Approach -- Inputs -- Steps -- Technologies and Overall Integration Strategy -- Integration Solution Tools -- Security -- Outputs -- Scenario -- Summary -- Chapter 7: Apex, Visualforce & -- Lightning: Phase F -- Overview -- Visualforce -- Apex -- Lightning Components -- Design and Functionality -- Govern the continuum of UI options actually used against those available on the platform (buttons, mashups, Canvas, Visualforce pages, and Lightning components) -- Govern the sharing and visibility model in code solution -- Govern the code against security best practices to ensure all Visualforce and Apex code is developed per OWASP standards -- Govern the object-oriented design principles and design patterns that were adhered to when developing the solution (Singleton, etc.) -- Govern the appropriate use of the Model-View-Controller pattern -- Govern any Apex controllers against the technical standards (extensions to standard controllers and custom controllers) -- Govern the usage of custom settings and synchronous vs. asynchronous patterns, and all the available execution contexts (e.g., batch, trigger, callout, etc.) Govern the usage of batch Apex and the flex queue -- Govern the Apex / Visualforce solution against the governor limits -- Govern the order of execution of transactions within the platform (specifically against pre-existing triggers) -- Govern the quality of test coverage (required for production deployment, call-out testing is a special case) -- Govern the approach to error/exception handling -- Performance and Scalability -- Govern that performance and scalability best practices have been considered within Visualforce pages and Apex code (performance profiling, use of static resources) -- Govern the Apex and Visualforce performance to include LDV scenarios (Pagination, JavaScript remoting) -- Govern the use of external web technologies and complementary UI technologies -- Maintainability and Reuse -- Govern multi-language support and determine the appropriate solution has been used to support globalization -- Govern the options and techniques used to make programmatic components maintainable and reusable on the platform (custom settings, skeleton templates, custom metadata types) -- Method -- Approach -- Inputs -- Steps -- Design and Functionality -- Performance and Scalability -- Maintainability and Reuse -- Outputs -- Scenario -- Summary -- Chapter 8: Communities: Phase G -- Overview -- Design -- Govern the license types associated with the sites and communities -- Govern the sharing usage for partner, customer, and employee community users -- The project team has planned its sharing model -- The project team has defined its sharing requirements -- The project team has determined the sharing options it should use -- The project team has updated its sharing requirements with the sharing option it will implement -- Govern the different UI / UX capabilities to style a community -- Govern the mobile considerations for communities Identity Management -- Govern how identity management is handled within communities: provisioning, syncing, and de-provisioning -- Govern the use of external identity (Facebook, Google, etc.) if appropriate -- Method -- Approach -- Inputs -- Steps -- Design -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 9: Mobile Solutions Architecture: Phase H -- Overview -- Mobile Strategy and Design -- Govern the mobile solution for use of the appropriate mobile platform: HTML5, Native (iOS / Android), hybrid solutions, or Salesforce mobile app -- Govern the authentication / authorization (including SSO), offline storage, and sync requirements -- Govern the use of Salesforce mobile app declarative design -- Mobile Security -- Govern how the project has secured the mobile application and its data, including offline data encryption -- Method -- Approach -- Inputs -- Steps -- Mobile Strategy and Design -- Mobile Security -- Outputs -- Scenario -- Summary -- Chapter 10: Development Lifecycle & -- Deployment: Phase I -- Overview -- Development Lifecycle -- Govern the development and release of applications on the Salesforce platform -- Govern the testing strategies and test plan -- Deployment Techniques and Considerations -- Govern the deployment strategy and the platform tools, use cases, limitations, and best practices for environment management and data migration strategy -- Govern the tools (source control and continuous integration for release management) -- Method -- Approach -- Inputs -- Steps -- Development Lifecycle -- Deployment Techniques and Considerations -- Outputs -- Scenario -- Summary -- Chapter 11: Resource Base Introduction -- How to Use the Resource Base -- The Resource Base Structure -- The GitHub Repository -- A Final Word -- Chapter 12: Application Architecture (Phase A) Resource Base -- Guidelines and Best Practices General Architecture |
| ctrlnum | (ZDB-30-PQE)EBC6897050 (ZDB-30-PAD)EBC6897050 (ZDB-89-EBL)EBL6897050 (OCoLC)1301273680 (DE-599)BVBBV048920962 |
| dewey-full | 658.812 |
| dewey-hundreds | 600 - Technology (Applied sciences) |
| dewey-ones | 658 - General management |
| dewey-raw | 658.812 |
| dewey-search | 658.812 |
| dewey-sort | 3658.812 |
| dewey-tens | 650 - Management and auxiliary services |
| discipline | Wirtschaftswissenschaften |
| discipline_str_mv | Wirtschaftswissenschaften |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>11091nmm a2200481zc 4500</leader><controlfield tag="001">BV048920962</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">00000000000000.0</controlfield><controlfield tag="007">cr|uuu---uuuuu</controlfield><controlfield tag="008">230502s2022 |||| o||u| ||||||eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781484274040</subfield><subfield code="9">978-1-4842-7404-0</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ZDB-30-PQE)EBC6897050</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ZDB-30-PAD)EBC6897050</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ZDB-89-EBL)EBL6897050</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)1301273680</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV048920962</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-2070s</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">658.812</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Harding, Lee</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Salesforce Platform Governance Method</subfield><subfield code="b">A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Berkeley, CA</subfield><subfield code="b">Apress L. P.</subfield><subfield code="c">2022</subfield></datafield><datafield tag="264" ind1=" " ind2="4"><subfield code="c">©2022</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource (399 Seiten)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Description based on publisher supplied metadata and other sources</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Intro -- Table of Contents -- About the Authors -- About the Technical Reviewer -- Acknowledgments -- Introduction -- Chapter 1: Salesforce Platform Governance Method -- Overview -- The Method -- The Resource Base -- Key Points -- Basic Structure -- Method Adaption -- Architecture Governance -- Process Management -- Scoping the Application Governance Cycle -- Summary -- Chapter 2: Application Architecture: Phase A -- Overview -- General Architecture -- Localization / Global Deployments -- Workflow &amp -- Processes -- Formulas -- Files &amp -- Social -- Method -- Approach -- Inputs -- Steps -- General Architecture -- Localization &amp -- Global Deployments -- Workflow &amp -- Processes -- Formulas -- Files &amp -- Social -- Outputs -- Scenario -- Summary -- Chapter 3: Data Architecture &amp -- Management: Phase B -- Overview -- Design &amp -- Optimization -- Data Movement -- Method -- Approach -- Inputs -- Steps -- Design and Optimization -- Data Movement -- Outputs -- Scenario -- Summary -- Chapter 4: Identity &amp -- Access Management: Phase C -- Overview -- Single Sign-On -- Identity Management -- Method -- Approach -- Inputs -- Steps -- Single Sign-On -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 5: Sharing &amp -- Visibility: Phase D -- Overview -- Declarative Sharing -- Govern the core declarative platform features that are used to meet record-level, object, and field-sharing requirements -- Organization-Wide Defaults (OWDs) -- Profile-level object settings -- Permission set-level object settings -- Record ownership -- Manual sharing -- Govern the use of team functionality to meet business requirements -- Role hierarchies -- Teams (accounts, case, and opportunity) -- Queues -- Manager groups -- Govern list view, report folder, and dashboard folder security -- List view security</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Report folder and dashboard folder security -- Legacy folder sharing -- Enhanced folder Sharing -- Govern implicit sharing within the platform -- Implicit sharing -- Master-detail relationship -- Account relationship data sharing -- Govern the appropriate sharing design for the various community user types -- Sharing sets -- Sharing groups -- Super user access -- External account hierarchy -- Govern the application of territory management -- Programmatic Sharing -- Govern the core programmatic platform security features that have been used to meet sharing requirements -- Enforcing sharing rules -- Enforcing object and field permissions -- Enforcing SOQL data filtering -- Class security -- Apex-managed sharing -- Govern the security risks in programmatic customizations relative to data visibility, focus on difference in capabilities between programmatic sharing for standard vs. custom objects -- Performance -- Govern whether the solution is scalable to and maintainable at enterprise levels -- Data Security -- Govern any specific secured data implementation on the Salesforce platform -- Govern the use of "classic" encryption fields in the Salesforce platform and the limitations that need to be taken into consideration -- Method -- Approach -- Inputs -- Steps -- Declarative Sharing -- Programmatic Sharing -- Performance -- Data Security -- Outputs -- Scenario -- Summary -- Chapter 6: Integration: Phase E -- Overview -- Technologies &amp -- Overall Integration Strategy -- Govern the enterprise integration landscape and overall integration strategy, with associated risks, trade-offs, and business and technical considerations -- Govern the data backup/archiving/data warehousing integration strategies -- Govern whether the appropriate integration strategy and standard integration patterns have been used</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Govern the integration components involved in a flow and consider transaction management and error and exception handling -- Integration Solution Tools -- Govern the use of the appropriate platform-specific integration technology for integration with external systems -- Remote Process Invocation - Request and Reply -- Remote Process Invocation - Fire and Forget -- Batch Data Synchronization -- Remote Call-in -- UI Update Based on Data Changes -- Data Virtualization -- Govern the usage of the Lightning platform integration APIs and features and determine whether they have been appropriately used -- Security -- Govern how security requirements are met at each of the integration layers -- Method -- Approach -- Inputs -- Steps -- Technologies and Overall Integration Strategy -- Integration Solution Tools -- Security -- Outputs -- Scenario -- Summary -- Chapter 7: Apex, Visualforce &amp -- Lightning: Phase F -- Overview -- Visualforce -- Apex -- Lightning Components -- Design and Functionality -- Govern the continuum of UI options actually used against those available on the platform (buttons, mashups, Canvas, Visualforce pages, and Lightning components) -- Govern the sharing and visibility model in code solution -- Govern the code against security best practices to ensure all Visualforce and Apex code is developed per OWASP standards -- Govern the object-oriented design principles and design patterns that were adhered to when developing the solution (Singleton, etc.) -- Govern the appropriate use of the Model-View-Controller pattern -- Govern any Apex controllers against the technical standards (extensions to standard controllers and custom controllers) -- Govern the usage of custom settings and synchronous vs. asynchronous patterns, and all the available execution contexts (e.g., batch, trigger, callout, etc.)</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Govern the usage of batch Apex and the flex queue -- Govern the Apex / Visualforce solution against the governor limits -- Govern the order of execution of transactions within the platform (specifically against pre-existing triggers) -- Govern the quality of test coverage (required for production deployment, call-out testing is a special case) -- Govern the approach to error/exception handling -- Performance and Scalability -- Govern that performance and scalability best practices have been considered within Visualforce pages and Apex code (performance profiling, use of static resources) -- Govern the Apex and Visualforce performance to include LDV scenarios (Pagination, JavaScript remoting) -- Govern the use of external web technologies and complementary UI technologies -- Maintainability and Reuse -- Govern multi-language support and determine the appropriate solution has been used to support globalization -- Govern the options and techniques used to make programmatic components maintainable and reusable on the platform (custom settings, skeleton templates, custom metadata types) -- Method -- Approach -- Inputs -- Steps -- Design and Functionality -- Performance and Scalability -- Maintainability and Reuse -- Outputs -- Scenario -- Summary -- Chapter 8: Communities: Phase G -- Overview -- Design -- Govern the license types associated with the sites and communities -- Govern the sharing usage for partner, customer, and employee community users -- The project team has planned its sharing model -- The project team has defined its sharing requirements -- The project team has determined the sharing options it should use -- The project team has updated its sharing requirements with the sharing option it will implement -- Govern the different UI / UX capabilities to style a community -- Govern the mobile considerations for communities</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">Identity Management -- Govern how identity management is handled within communities: provisioning, syncing, and de-provisioning -- Govern the use of external identity (Facebook, Google, etc.) if appropriate -- Method -- Approach -- Inputs -- Steps -- Design -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 9: Mobile Solutions Architecture: Phase H -- Overview -- Mobile Strategy and Design -- Govern the mobile solution for use of the appropriate mobile platform: HTML5, Native (iOS / Android), hybrid solutions, or Salesforce mobile app -- Govern the authentication / authorization (including SSO), offline storage, and sync requirements -- Govern the use of Salesforce mobile app declarative design -- Mobile Security -- Govern how the project has secured the mobile application and its data, including offline data encryption -- Method -- Approach -- Inputs -- Steps -- Mobile Strategy and Design -- Mobile Security -- Outputs -- Scenario -- Summary -- Chapter 10: Development Lifecycle &amp -- Deployment: Phase I -- Overview -- Development Lifecycle -- Govern the development and release of applications on the Salesforce platform -- Govern the testing strategies and test plan -- Deployment Techniques and Considerations -- Govern the deployment strategy and the platform tools, use cases, limitations, and best practices for environment management and data migration strategy -- Govern the tools (source control and continuous integration for release management) -- Method -- Approach -- Inputs -- Steps -- Development Lifecycle -- Deployment Techniques and Considerations -- Outputs -- Scenario -- Summary -- Chapter 11: Resource Base Introduction -- How to Use the Resource Base -- The Resource Base Structure -- The GitHub Repository -- A Final Word -- Chapter 12: Application Architecture (Phase A) Resource Base -- Guidelines and Best Practices</subfield></datafield><datafield tag="505" ind1="8" ind2=" "><subfield code="a">General Architecture</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Salesforce (Online service)</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Sales management</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Customer relations-Management</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Bayliss, Lee</subfield><subfield code="e">Sonstige</subfield><subfield code="4">oth</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druck-Ausgabe</subfield><subfield code="a">Harding, Lee</subfield><subfield code="t">Salesforce Platform Governance Method</subfield><subfield code="d">Berkeley, CA : Apress L. P.,c2022</subfield><subfield code="z">9781484274033</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-PQE</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-034185053</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">https://ebookcentral.proquest.com/lib/hwr/detail.action?docID=6897050</subfield><subfield code="l">HWR01</subfield><subfield code="p">ZDB-30-PQE</subfield><subfield code="q">HWR_PDA_PQE</subfield><subfield code="x">Aggregator</subfield><subfield code="3">Volltext</subfield></datafield></record></collection> |
| id | DE-604.BV048920962 |
| illustrated | Not Illustrated |
| index_date | 2024-07-03T21:55:16Z |
| indexdate | 2024-07-10T09:49:54Z |
| institution | BVB |
| isbn | 9781484274040 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-034185053 |
| oclc_num | 1301273680 |
| open_access_boolean | |
| owner | DE-2070s |
| owner_facet | DE-2070s |
| physical | 1 Online-Ressource (399 Seiten) |
| psigel | ZDB-30-PQE ZDB-30-PQE HWR_PDA_PQE |
| publishDate | 2022 |
| publishDateSearch | 2022 |
| publishDateSort | 2022 |
| publisher | Apress L. P. |
| record_format | marc |
| spelling | Harding, Lee Verfasser aut Salesforce Platform Governance Method A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform Berkeley, CA Apress L. P. 2022 ©2022 1 Online-Ressource (399 Seiten) txt rdacontent c rdamedia cr rdacarrier Description based on publisher supplied metadata and other sources Intro -- Table of Contents -- About the Authors -- About the Technical Reviewer -- Acknowledgments -- Introduction -- Chapter 1: Salesforce Platform Governance Method -- Overview -- The Method -- The Resource Base -- Key Points -- Basic Structure -- Method Adaption -- Architecture Governance -- Process Management -- Scoping the Application Governance Cycle -- Summary -- Chapter 2: Application Architecture: Phase A -- Overview -- General Architecture -- Localization / Global Deployments -- Workflow & -- Processes -- Formulas -- Files & -- Social -- Method -- Approach -- Inputs -- Steps -- General Architecture -- Localization & -- Global Deployments -- Workflow & -- Processes -- Formulas -- Files & -- Social -- Outputs -- Scenario -- Summary -- Chapter 3: Data Architecture & -- Management: Phase B -- Overview -- Design & -- Optimization -- Data Movement -- Method -- Approach -- Inputs -- Steps -- Design and Optimization -- Data Movement -- Outputs -- Scenario -- Summary -- Chapter 4: Identity & -- Access Management: Phase C -- Overview -- Single Sign-On -- Identity Management -- Method -- Approach -- Inputs -- Steps -- Single Sign-On -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 5: Sharing & -- Visibility: Phase D -- Overview -- Declarative Sharing -- Govern the core declarative platform features that are used to meet record-level, object, and field-sharing requirements -- Organization-Wide Defaults (OWDs) -- Profile-level object settings -- Permission set-level object settings -- Record ownership -- Manual sharing -- Govern the use of team functionality to meet business requirements -- Role hierarchies -- Teams (accounts, case, and opportunity) -- Queues -- Manager groups -- Govern list view, report folder, and dashboard folder security -- List view security Report folder and dashboard folder security -- Legacy folder sharing -- Enhanced folder Sharing -- Govern implicit sharing within the platform -- Implicit sharing -- Master-detail relationship -- Account relationship data sharing -- Govern the appropriate sharing design for the various community user types -- Sharing sets -- Sharing groups -- Super user access -- External account hierarchy -- Govern the application of territory management -- Programmatic Sharing -- Govern the core programmatic platform security features that have been used to meet sharing requirements -- Enforcing sharing rules -- Enforcing object and field permissions -- Enforcing SOQL data filtering -- Class security -- Apex-managed sharing -- Govern the security risks in programmatic customizations relative to data visibility, focus on difference in capabilities between programmatic sharing for standard vs. custom objects -- Performance -- Govern whether the solution is scalable to and maintainable at enterprise levels -- Data Security -- Govern any specific secured data implementation on the Salesforce platform -- Govern the use of "classic" encryption fields in the Salesforce platform and the limitations that need to be taken into consideration -- Method -- Approach -- Inputs -- Steps -- Declarative Sharing -- Programmatic Sharing -- Performance -- Data Security -- Outputs -- Scenario -- Summary -- Chapter 6: Integration: Phase E -- Overview -- Technologies & -- Overall Integration Strategy -- Govern the enterprise integration landscape and overall integration strategy, with associated risks, trade-offs, and business and technical considerations -- Govern the data backup/archiving/data warehousing integration strategies -- Govern whether the appropriate integration strategy and standard integration patterns have been used Govern the integration components involved in a flow and consider transaction management and error and exception handling -- Integration Solution Tools -- Govern the use of the appropriate platform-specific integration technology for integration with external systems -- Remote Process Invocation - Request and Reply -- Remote Process Invocation - Fire and Forget -- Batch Data Synchronization -- Remote Call-in -- UI Update Based on Data Changes -- Data Virtualization -- Govern the usage of the Lightning platform integration APIs and features and determine whether they have been appropriately used -- Security -- Govern how security requirements are met at each of the integration layers -- Method -- Approach -- Inputs -- Steps -- Technologies and Overall Integration Strategy -- Integration Solution Tools -- Security -- Outputs -- Scenario -- Summary -- Chapter 7: Apex, Visualforce & -- Lightning: Phase F -- Overview -- Visualforce -- Apex -- Lightning Components -- Design and Functionality -- Govern the continuum of UI options actually used against those available on the platform (buttons, mashups, Canvas, Visualforce pages, and Lightning components) -- Govern the sharing and visibility model in code solution -- Govern the code against security best practices to ensure all Visualforce and Apex code is developed per OWASP standards -- Govern the object-oriented design principles and design patterns that were adhered to when developing the solution (Singleton, etc.) -- Govern the appropriate use of the Model-View-Controller pattern -- Govern any Apex controllers against the technical standards (extensions to standard controllers and custom controllers) -- Govern the usage of custom settings and synchronous vs. asynchronous patterns, and all the available execution contexts (e.g., batch, trigger, callout, etc.) Govern the usage of batch Apex and the flex queue -- Govern the Apex / Visualforce solution against the governor limits -- Govern the order of execution of transactions within the platform (specifically against pre-existing triggers) -- Govern the quality of test coverage (required for production deployment, call-out testing is a special case) -- Govern the approach to error/exception handling -- Performance and Scalability -- Govern that performance and scalability best practices have been considered within Visualforce pages and Apex code (performance profiling, use of static resources) -- Govern the Apex and Visualforce performance to include LDV scenarios (Pagination, JavaScript remoting) -- Govern the use of external web technologies and complementary UI technologies -- Maintainability and Reuse -- Govern multi-language support and determine the appropriate solution has been used to support globalization -- Govern the options and techniques used to make programmatic components maintainable and reusable on the platform (custom settings, skeleton templates, custom metadata types) -- Method -- Approach -- Inputs -- Steps -- Design and Functionality -- Performance and Scalability -- Maintainability and Reuse -- Outputs -- Scenario -- Summary -- Chapter 8: Communities: Phase G -- Overview -- Design -- Govern the license types associated with the sites and communities -- Govern the sharing usage for partner, customer, and employee community users -- The project team has planned its sharing model -- The project team has defined its sharing requirements -- The project team has determined the sharing options it should use -- The project team has updated its sharing requirements with the sharing option it will implement -- Govern the different UI / UX capabilities to style a community -- Govern the mobile considerations for communities Identity Management -- Govern how identity management is handled within communities: provisioning, syncing, and de-provisioning -- Govern the use of external identity (Facebook, Google, etc.) if appropriate -- Method -- Approach -- Inputs -- Steps -- Design -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 9: Mobile Solutions Architecture: Phase H -- Overview -- Mobile Strategy and Design -- Govern the mobile solution for use of the appropriate mobile platform: HTML5, Native (iOS / Android), hybrid solutions, or Salesforce mobile app -- Govern the authentication / authorization (including SSO), offline storage, and sync requirements -- Govern the use of Salesforce mobile app declarative design -- Mobile Security -- Govern how the project has secured the mobile application and its data, including offline data encryption -- Method -- Approach -- Inputs -- Steps -- Mobile Strategy and Design -- Mobile Security -- Outputs -- Scenario -- Summary -- Chapter 10: Development Lifecycle & -- Deployment: Phase I -- Overview -- Development Lifecycle -- Govern the development and release of applications on the Salesforce platform -- Govern the testing strategies and test plan -- Deployment Techniques and Considerations -- Govern the deployment strategy and the platform tools, use cases, limitations, and best practices for environment management and data migration strategy -- Govern the tools (source control and continuous integration for release management) -- Method -- Approach -- Inputs -- Steps -- Development Lifecycle -- Deployment Techniques and Considerations -- Outputs -- Scenario -- Summary -- Chapter 11: Resource Base Introduction -- How to Use the Resource Base -- The Resource Base Structure -- The GitHub Repository -- A Final Word -- Chapter 12: Application Architecture (Phase A) Resource Base -- Guidelines and Best Practices General Architecture Salesforce (Online service) Sales management Customer relations-Management Bayliss, Lee Sonstige oth Erscheint auch als Druck-Ausgabe Harding, Lee Salesforce Platform Governance Method Berkeley, CA : Apress L. P.,c2022 9781484274033 |
| spellingShingle | Harding, Lee Salesforce Platform Governance Method A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform Intro -- Table of Contents -- About the Authors -- About the Technical Reviewer -- Acknowledgments -- Introduction -- Chapter 1: Salesforce Platform Governance Method -- Overview -- The Method -- The Resource Base -- Key Points -- Basic Structure -- Method Adaption -- Architecture Governance -- Process Management -- Scoping the Application Governance Cycle -- Summary -- Chapter 2: Application Architecture: Phase A -- Overview -- General Architecture -- Localization / Global Deployments -- Workflow & -- Processes -- Formulas -- Files & -- Social -- Method -- Approach -- Inputs -- Steps -- General Architecture -- Localization & -- Global Deployments -- Workflow & -- Processes -- Formulas -- Files & -- Social -- Outputs -- Scenario -- Summary -- Chapter 3: Data Architecture & -- Management: Phase B -- Overview -- Design & -- Optimization -- Data Movement -- Method -- Approach -- Inputs -- Steps -- Design and Optimization -- Data Movement -- Outputs -- Scenario -- Summary -- Chapter 4: Identity & -- Access Management: Phase C -- Overview -- Single Sign-On -- Identity Management -- Method -- Approach -- Inputs -- Steps -- Single Sign-On -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 5: Sharing & -- Visibility: Phase D -- Overview -- Declarative Sharing -- Govern the core declarative platform features that are used to meet record-level, object, and field-sharing requirements -- Organization-Wide Defaults (OWDs) -- Profile-level object settings -- Permission set-level object settings -- Record ownership -- Manual sharing -- Govern the use of team functionality to meet business requirements -- Role hierarchies -- Teams (accounts, case, and opportunity) -- Queues -- Manager groups -- Govern list view, report folder, and dashboard folder security -- List view security Report folder and dashboard folder security -- Legacy folder sharing -- Enhanced folder Sharing -- Govern implicit sharing within the platform -- Implicit sharing -- Master-detail relationship -- Account relationship data sharing -- Govern the appropriate sharing design for the various community user types -- Sharing sets -- Sharing groups -- Super user access -- External account hierarchy -- Govern the application of territory management -- Programmatic Sharing -- Govern the core programmatic platform security features that have been used to meet sharing requirements -- Enforcing sharing rules -- Enforcing object and field permissions -- Enforcing SOQL data filtering -- Class security -- Apex-managed sharing -- Govern the security risks in programmatic customizations relative to data visibility, focus on difference in capabilities between programmatic sharing for standard vs. custom objects -- Performance -- Govern whether the solution is scalable to and maintainable at enterprise levels -- Data Security -- Govern any specific secured data implementation on the Salesforce platform -- Govern the use of "classic" encryption fields in the Salesforce platform and the limitations that need to be taken into consideration -- Method -- Approach -- Inputs -- Steps -- Declarative Sharing -- Programmatic Sharing -- Performance -- Data Security -- Outputs -- Scenario -- Summary -- Chapter 6: Integration: Phase E -- Overview -- Technologies & -- Overall Integration Strategy -- Govern the enterprise integration landscape and overall integration strategy, with associated risks, trade-offs, and business and technical considerations -- Govern the data backup/archiving/data warehousing integration strategies -- Govern whether the appropriate integration strategy and standard integration patterns have been used Govern the integration components involved in a flow and consider transaction management and error and exception handling -- Integration Solution Tools -- Govern the use of the appropriate platform-specific integration technology for integration with external systems -- Remote Process Invocation - Request and Reply -- Remote Process Invocation - Fire and Forget -- Batch Data Synchronization -- Remote Call-in -- UI Update Based on Data Changes -- Data Virtualization -- Govern the usage of the Lightning platform integration APIs and features and determine whether they have been appropriately used -- Security -- Govern how security requirements are met at each of the integration layers -- Method -- Approach -- Inputs -- Steps -- Technologies and Overall Integration Strategy -- Integration Solution Tools -- Security -- Outputs -- Scenario -- Summary -- Chapter 7: Apex, Visualforce & -- Lightning: Phase F -- Overview -- Visualforce -- Apex -- Lightning Components -- Design and Functionality -- Govern the continuum of UI options actually used against those available on the platform (buttons, mashups, Canvas, Visualforce pages, and Lightning components) -- Govern the sharing and visibility model in code solution -- Govern the code against security best practices to ensure all Visualforce and Apex code is developed per OWASP standards -- Govern the object-oriented design principles and design patterns that were adhered to when developing the solution (Singleton, etc.) -- Govern the appropriate use of the Model-View-Controller pattern -- Govern any Apex controllers against the technical standards (extensions to standard controllers and custom controllers) -- Govern the usage of custom settings and synchronous vs. asynchronous patterns, and all the available execution contexts (e.g., batch, trigger, callout, etc.) Govern the usage of batch Apex and the flex queue -- Govern the Apex / Visualforce solution against the governor limits -- Govern the order of execution of transactions within the platform (specifically against pre-existing triggers) -- Govern the quality of test coverage (required for production deployment, call-out testing is a special case) -- Govern the approach to error/exception handling -- Performance and Scalability -- Govern that performance and scalability best practices have been considered within Visualforce pages and Apex code (performance profiling, use of static resources) -- Govern the Apex and Visualforce performance to include LDV scenarios (Pagination, JavaScript remoting) -- Govern the use of external web technologies and complementary UI technologies -- Maintainability and Reuse -- Govern multi-language support and determine the appropriate solution has been used to support globalization -- Govern the options and techniques used to make programmatic components maintainable and reusable on the platform (custom settings, skeleton templates, custom metadata types) -- Method -- Approach -- Inputs -- Steps -- Design and Functionality -- Performance and Scalability -- Maintainability and Reuse -- Outputs -- Scenario -- Summary -- Chapter 8: Communities: Phase G -- Overview -- Design -- Govern the license types associated with the sites and communities -- Govern the sharing usage for partner, customer, and employee community users -- The project team has planned its sharing model -- The project team has defined its sharing requirements -- The project team has determined the sharing options it should use -- The project team has updated its sharing requirements with the sharing option it will implement -- Govern the different UI / UX capabilities to style a community -- Govern the mobile considerations for communities Identity Management -- Govern how identity management is handled within communities: provisioning, syncing, and de-provisioning -- Govern the use of external identity (Facebook, Google, etc.) if appropriate -- Method -- Approach -- Inputs -- Steps -- Design -- Identity Management -- Outputs -- Scenario -- Summary -- Chapter 9: Mobile Solutions Architecture: Phase H -- Overview -- Mobile Strategy and Design -- Govern the mobile solution for use of the appropriate mobile platform: HTML5, Native (iOS / Android), hybrid solutions, or Salesforce mobile app -- Govern the authentication / authorization (including SSO), offline storage, and sync requirements -- Govern the use of Salesforce mobile app declarative design -- Mobile Security -- Govern how the project has secured the mobile application and its data, including offline data encryption -- Method -- Approach -- Inputs -- Steps -- Mobile Strategy and Design -- Mobile Security -- Outputs -- Scenario -- Summary -- Chapter 10: Development Lifecycle & -- Deployment: Phase I -- Overview -- Development Lifecycle -- Govern the development and release of applications on the Salesforce platform -- Govern the testing strategies and test plan -- Deployment Techniques and Considerations -- Govern the deployment strategy and the platform tools, use cases, limitations, and best practices for environment management and data migration strategy -- Govern the tools (source control and continuous integration for release management) -- Method -- Approach -- Inputs -- Steps -- Development Lifecycle -- Deployment Techniques and Considerations -- Outputs -- Scenario -- Summary -- Chapter 11: Resource Base Introduction -- How to Use the Resource Base -- The Resource Base Structure -- The GitHub Repository -- A Final Word -- Chapter 12: Application Architecture (Phase A) Resource Base -- Guidelines and Best Practices General Architecture Salesforce (Online service) Sales management Customer relations-Management |
| title | Salesforce Platform Governance Method A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform |
| title_auth | Salesforce Platform Governance Method A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform |
| title_exact_search | Salesforce Platform Governance Method A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform |
| title_exact_search_txtP | Salesforce Platform Governance Method A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform |
| title_full | Salesforce Platform Governance Method A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform |
| title_fullStr | Salesforce Platform Governance Method A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform |
| title_full_unstemmed | Salesforce Platform Governance Method A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform |
| title_short | Salesforce Platform Governance Method |
| title_sort | salesforce platform governance method a guide to governing changes development and enhancements on the salesforce platform |
| title_sub | A Guide to Governing Changes, Development, and Enhancements on the Salesforce Platform |
| topic | Salesforce (Online service) Sales management Customer relations-Management |
| topic_facet | Salesforce (Online service) Sales management Customer relations-Management |
| work_keys_str_mv | AT hardinglee salesforceplatformgovernancemethodaguidetogoverningchangesdevelopmentandenhancementsonthesalesforceplatform AT baylisslee salesforceplatformgovernancemethodaguidetogoverningchangesdevelopmentandenhancementsonthesalesforceplatform |