- Force.com Enterprise Architecture - Second Edition
- Table of Contents
- Force.com Enterprise Architecture - Second Edition
- Credits
- Foreword
- About the Author
- Acknowledgements
- About the Reviewers
- www.PacktPub.com
- Customer Feedback
- Preface
- 1. Building, Publishing, and Supporting Your Application
- Required organizations
- Introducing the book's sample application
- Package types and benefits
- Creating your first managed package
- Package dependencies and uploading
- Becoming a Salesforce partner and benefits
- Introduction to AppExchange and listings
- Installing and testing your package
- Licensing
- Providing support
- Customer metrics
- Trialforce and Test Drive
- Summary
- 2. Leveraging Platform Features
- Packaging and upgradable components
- Understanding the custom field features
- Understanding the available security features
- Platform APIs
- Localization and translation
- Building customizable user interfaces
- E-mail customization with e-mail templates
- Process Builder, Workflow and Flow
- Social features and mobile
- Summary
- 3. Application Storage
- Mapping out end user storage requirements
- Understanding the different storage types
- Reusing the existing Standard Objects
- Importing and exporting data
- Options for replicating and archiving data
- External data sources
- Summary
- 4. Apex Execution and Separation of Concerns
- 5. Application Service Layer
- 6. Application Domain Layer
- Introducing the Domain layer pattern
- Implementation design guidelines
- Domain class template
- Implementing Domain Trigger logic
- Implementing custom Domain logic
- Object-oriented programming
- Creating a compliance application framework
- An Apex interface example
- Testing the Domain layer
- Calling the Domain layer
- Updating the FormulaForce package
- Summary
- 7. Application Selector Layer
- 8. User Interface
- Which devices should you target?
- Introducing Salesforce Standard UIs and Lightning
- Leveraging the Salesforce standard UIs
- Generating downloadable content
- Generating printable content
- Client server communication
- Managing limits
- Object and field-level security
- Managing performance and response times
- Using the Service layer and database access
- Considerations for using JavaScript libraries
- Custom Publisher Actions
- Creating websites and communities
- Mobile application strategy
- Custom reporting and the Analytics API
- Updating the FormulaForce package
- Summary
- 9. Lightning
- Building a basic Lightning user interface
- Lightning architecture
- FormulaForce Lightning Components
- Making components customizable
- Integrating with Lightning Experience
- Lightning Out and Visualforce
- Integrating with communities
- Testing
- Updating the FormulaForce package
- Summary
- 10. Providing Integration and Extensibility
- Reviewing your integration and extensibility needs
- Force.com platform APIs for integration
- Application integration APIs
- Exposing Lightning Components
- Extending Process Builder and Visualflow
- Alignment with Force.com extensibility features
- Extending the application logic with Apex interfaces
- Summary
- 11. Asynchronous Processing and Big Data Volumes
- 12. Unit Testing
- 13. Source Control and Continuous Integration
- Development workflow and infrastructure
- Developing with Source Control
- Hooking up Continuous Integration
- Releasing from Source Control
- Automated regression testing
- Summary
- Index
Normally, the total number of records retrieved within a single controller execution context is 50,000 records (in total across all SOQL queries executed). In addition, Visualforce components such as apex:dataTable and apex:repeat can only iterate over 1000 items before a runtime exception is thrown.
At the time of writing this, the readOnly attribute (specified on the apex:page component) changes this to 1 million records and 10,000 iterations within Visualforce components on the page (refer to the Salesforce documentation for the latest update). As the name suggests, no updates to the database can occur, which basically means no DML at all. Note that queries are still governed by timeouts.
Tip
If you require a more granular elevation of the SOQL query rows governor, you can apply the @ReadOnly Apex attribute to a JavaScript Remoting method in your controller, and not at the page level as described previously. Again, this method will not be able to use DML operations to update the database, but you will gain access to querying a higher number of query rows. Note that the iterator limit increase is not applicable in this context, as JavaScript Remoting and Visualforce iterator components cannot be used together.
-
No Comment