Cross cutting concerns for apex code. This is the most up-to-date code. The code contains the latest DX Packages for Common, Platform Events, and Trigger handling. The other repositories I left for those not yet moving to DX.
See this highlevel blog on this framework.
This code designed to encapsulate common cross-cutting concerns (logging, exception handling, platform events, caching, etc.).Often times cross-cutting concerns are an after-thought; or, hastily injected without any ability to manage or control.This package encapsulates those concerns and provide a mechanism to change/augment. Changing behaviour is a matter of inheritance and specifying choice via custom metadata. See the Wiki for more information.
Incorporated Platform Events Consumer/Publisher
Platform Events has been incorporated into this framework . The overlap between the two was too much to ignore. However, with the DX package, it is up to the user to determine whether to install the PE/CDC (Accc_PE) package.
It now includes a section on Platform Events. The work is on-going and will be addressed in conjunction with requests. Currently, the updates for Platform Events includes:
- Added Summer '19 features AsyncOperationEvent,
- Updates include more data written into the BigObject (i.e. replayids and operation ids) for recovery on a queued high-volume event.
- The template will be started but will probably not be done before the merge.
- Incorporate Trigger Handling for Platform Events and CDC. There is a section that can tie in the trigger handling framework.
- Control Event Batching Size (initially via attributes before moving into CMDT)
This package utilities a good deal of Object Oriented Principles (OOP) (as outlined in the blog linked). This site provides information around OOP and elements therein. Without having a good Object Oriented base, you may be able to take advantage of the components within the package, but you will not fully realize the underlying benefits/intent.
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
You will need to have Platform Cache enable; otherwise, caching WILL NOT work. Please note, if you are developing in a Dev Org, there is no caching and those related unit tests will fail. In addition, tests will fail if email deliverability is disabled.
The unit tests have a minimum of 96% code coverage. Tests can be invoked from favortite case tool. In Salesforce Org, navigate to Setup->Apex Classes and run all tests
All code, files and objects related to Apex Cross-Cutting Concerns are prefixed with 'accc'
There are TWO repos now. One is the older version which does not have the Platform Events. The newer one incorporates Platform Events and Change Data Capture (CDC) into the cross-cutting concerns. This repo is for those using DX.
Use the scripts to install the ALL version (i.e. with Platform Events + Trigger Handler)
The DX Project has scripts that have ability to control which packages to deploy (either the base ACCC or ACCC + PE/CDC)
If you download CCCDocs directory and navigate to ApexDocumentation directory and bring up index.htm in the browser you will get the JavaDoc-like information. The documentation will also link to the Wiki
Please read Contributing for details on our code of conduct, and the process for submitting pull requests to us.
- Accc Domain v0.5.1.1
- Accc Common v1.2.9.1
- Accc PE Domain v0.5.2.1
- Accc PE v1.1.2.1
- Accc TH v1.0.2.1
- Bill Anderson
This project is licensed under the MIT License - see the LICENSE file for details