What should be the scope of D_AppExtension? Requestor, Thread or Node level scope?
In the Application Build solution jar file provided in Pega Academy, the D_AppExtension is at the Requestor level whereas in the Pega Academy lesson for DCR, it has shown a screenshot showing the D_AppExtension on the thread scope.
But i feel it should be at the Node level as it is very constant for any application. Can somebody help me to have some clarity around this?
Though DCR design doesn't mention any specific practice for scope. But according to me, it should be good to use "Requestor" scope. As DCR primary objective is to have in-memory for Class, Flow & Workbaskets. There can be a case we may want to extend DCR to get different properties for different Requestor's instead of just Node level properties.
Its a bad idea to have in Thread level, because then it will be created per thread, which will be waste of memory.
Requestor is appropriatte but you have to be careful if you are a developer switching between fw and implementation layers for a single app as it will not refresh. When switching between apps as a developer, make sure to logout/in to get the refreshed page and correct settings.
Okey.... and why not Node scope if we already know that there is no difference in diferent requestors? which is generally the case....... for exp the D_AppExtension in the Warranty Claim Scenario in Practice Application solution.....