Posted: 2 May 2020 11:08 EDT Last activity: 8 May 2020 15:57 EDT
Reuse OOTB Service Package "api"?
I always created my own Service Package by myself, because I believed we can never reuse OOTB Service Package "api". However, I just noticed that if I modify the access group from defaulted "PRPC:Administrators" to my own layer's access group, such as "MyApp:Administrators", api seem to work. Yes, Service Package is not a rule instance and it is updatable. The merit is I can keep "/api/" in the URI, which I think is pretty standard, but is this safe to do? What are the demerits of this reuse approach?
Or, creating our own Service Package is the best practice?
***Edited by Moderator Marissa to update Platform Capability tags****
nothing wrong in reusing service package 'api' , but this data instance is packaged with some of the ootb REST services which dealts with pega internal stuff with different version like v1,v2 and may extended with v3 also in future, I would say better to create an another service packages with your custom services instead of clubbing ootb rules and custom services also into the single package and managing the requestor pools for all the services calls from a single package.