https://academy.pega.com/topic/enterprise-class-structure/v1
https://krishnapega.blogspot.com/2016/05/enterprise-class-structure.html
https://www.pegahelp.com/2020/05/pega-enterprise-class-structure-ecs.html
https://rulesware.com/pega-evolution-of-the-enterprise-class-structure-a-perspective-of-the-last-decade/
1) Reusability - While creating/refactoring rules, always evaluate the reusability aspect. Create/move the rules to WorkPool/Work- class for better reusability.
2) Prefer Declarative over procedural processing.
3) Avoid creating section rules with 1-2 fields.
4) Avoid creating the top level scalar properties on the Casetype class (or WorkPool class). Designing better data model always fetch the future maintenance of the application.
5) For properties that hold 'Amount' (or other decimal values) create property with type Decimal (with the desired precision as qualifier)
6) Leverage Background requestor for better user experience - Delegate the processing to background requestor such as queue processor/Agent.
7) Do not use the OOTB top-level properties for handling the processing logic. (For example, pyErrorMessage property was being used in svcPerformFlowAction OOTB activity).
8) Keep in mind the DB column size of the below properties (Especially pyLabel, PyDescription..etc)
1) DB Indexes : Analyze the query plan. Create DB Indexes on the columns that used on the filter conditions of the RD.
2) Avoid reading from Blob : Lookups read the entire blob column, so avoid reading the BLOB. Prefer to use RD's.
3) Background processing : Leverage background processing, wherever the need of processing and the data need not be shown to the user immediately. ( Agents, QueueProcessor, Async activity, load-datapage, Queue method)
4) Keyed data page : Read the data
5) Node level : Cache the frequently accessed data in-memory.
6) Deferred loading : Configure the deferred loading on the parts of the screen (sections) that they are not interested to see imemediately.
