Contents
How does apex work in the domain layer?
Apex triggers – Create, read, update, and delete (CRUD) operations, including undelete, occur on your custom objects as users or tools interact via the standard Salesforce UIs or one of the platform’s APIs. The operations are routed to the appropriate Domain class code corresponding to that object and operation.
Is the selector pattern based on a mapper pattern?
The Selector pattern that we are going to talk about helps with the above issues. The following is Martin Fowler’s definition of the Mapper pattern on which the Selector pattern is based. Mapper pattern, “A layer of Mappers (473) that moves data between objects and a database while keeping them independent of each other and the mapper itself.”
How is the selector layer used in Salesforce?
It is mostly used by classes within the Service layer (behind the service boundary), such as Domain and the Service classes themselves. However, UI Controllers and Batch Apex classes can also leverage them directly. A Selector layer contains code responsible for querying records from the database.
Is it easy to Test selector in apex?
Unfortunately, Apex runs at the system level, making it the developer’s responsibility to check security ahead of making the query. Fortunately, it doesn’t take a lot of Apex code to do this, but it’s easily overlooked and not easy to test for in unit tests. Keeping this in a selector makes life much easier.
Can a class be created as an object in apex?
As in Java, you can create classes in Apex. A class is a template or blueprint from which objects are created. An object is an instance of a class.
How to deploy open source libraries in apex?
To complete these challenges, you need to deploy some open source libraries unless you have already deployed them as part of the Apex Enterprise Patterns: Service Layer module. You’ll need to install the ApexMocks library first and then Apex Commons library.
When to use fflib _ sobjectunitofwork method in apex?
The fflib_SObjectUnitOfWork method is used in a Apex trigger context rather than a service context as per the SOC module. In this case, its scope is a trigger event or method. These methods are directly called by the platform, not the service layer.