Question
Maantic Inc
US
Last activity: 30 Nov 2017 11:32 EST
why always need to create work object in implementation class
Hi,
In my application, we are having all the rules in framework layer, I was told work object need to be created in implementation class
Let me know why work object need to be created in implementation class.
Pegasystems Inc.
US
Hi John,
Generally the Framework layer is just a template and the real time implementation is your actual application, so the work objects will be created in the implementation class itself. Hope this might help you.
Regards
Mahesh
Synechron
IN
Framework is a reusable layer which holds rules that can be used by multiple Applications, built on Framework Application.
You should always instantiate Implementation class. Framework class/layer should be used to hold/contain reusable rules.
SiXworks Limited
GB
This model gives you the flexibility to use the Framework in other applications, or introduce divisions.
If you create your Work Objects at the Framework level, you lose the reason behind having the Implementation and Framework in the first place.
In the future, if your organisation has multiple implementations using the same Framework, you will currently be able to specialise rules by class for each implementation; Whilst you technically can create Work Objects at the Framework level, this would cause you a world of pain if you elect to extend the application in the future.