Book Image

Force.com Enterprise Architecture - Second Edition

By : Andrew Fawcett
Book Image

Force.com Enterprise Architecture - Second Edition

By: Andrew Fawcett

Overview of this book

Companies of all sizes have seen the need for Force.com's architectural strategy focused on enabling their business objectives. Successful enterprise applications require planning, commitment, and investment in the best tools, processes, and features available. This book will teach you how to architect and support enduring applications for enterprise clients with Salesforce by exploring how to identify architecture needs and design solutions based on industry standard patterns. There are several ways to build solutions on Force.com, and this book will guide you through a logical path and show you the steps and considerations required to build packaged solutions from start to finish. It covers all aspects, from engineering to getting your application into the hands of your customers, and ensuring that they get the best value possible from your Force.com application. You will get acquainted with extending tools such as Lightning App Builder, Process Builder, and Flow with your own application logic. In addition to building your own application API, you will learn the techniques required to leverage the latest Lightning technologies on desktop and mobile platforms.
Table of Contents (23 chapters)
Force.com Enterprise Architecture - Second Edition
Credits
Foreword
About the Author
Acknowledgements
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
Index

Making components customizable


The components included in this chapter will appear in Lightning App Builder and are thus available for the developer and consumers of the package to drag and drop them onto pages. Because they are global they can also use them in their own component code:

This is due to the following aspects:

  • The access attribute on the components is set to global.

  • They implement applicable flexipage and force interfaces.

  • Though not required, the .design files specify a component label:

    <design:component label="Race Calendar">
    </design:component>
  • The .svg file for the c:CheckCompliance component defines a custom icon that is displayed next to the component in the Lightning App Builder.

  • Though not required, the Race Result component also includes additional markup to indicate to Lightning App Builder, the component is only relevant to the Race__c custom object:

    <design:component label="Race Results">
    <sfdc:objects>
    <sfdc:object>Race__c</sfdc:object...