Let assume I am creating new application for ZPlus organization. This is organization does not have any multiple line of business (LOB). This organization deals with few specific set customers who applies for building plan approvals, building extension approvals, building safety and renewals etc. All these journeys are handled by one single department.
Therefore, while designing application realized there is no need for framework layer and Only implementation layer sufficient.
Implementation layer is built on top of Pega industry framework.
Question comes how reusability is achieved to the ZPlus?
Of course, our answer would be if there are any reusable data entities or common processes/integrations can be developed in Zplus-work- , Zplus-Data- and Zplus-Int- in organization rulesets Zplus and ZplusInt
In future, if HR application need to be developed and want to leverage reusable assets then organization rulesets can be plugged in HR application. Is this OK to do it.
Whether we need to create separate application aka enterprise application just to plug these organization rulesets and provide them?
***Edited by Moderator: Pooja Gadige to change content format from Discussion to Question, add capability tag***
@mulukasu-1 It is always better to create Org layer (thin) application for having reusability in future which could contains org branding/styling, integrations assets & any reusable utilities for that org.
Reusability of the rules can be done through various methodology. I have mentioned some of the frequently used reusable methodology features below.
Having an enterprise application design.
Having a component application design.
Having reusable rule-set design.
In the latest LSA architecture exam course pega have explained all the above mentioned implementation more clearly and when we need to go for which reusable design. Please check that once that would be more interesting.