How to manage multiple versions for Pega REST API
The requirement is we have a rest service which is used by multiple consumers and whenever there is a change in request / response structure or functionality we want to give the consumer some time before they had to upgrade to new service structure.
For example look at the below scenario where consumer has to do a change right away if there is no versioning
V1- Employee-Page
V2- Employee-Pagelist
Since access group is being maintained at service package level, the v2 changes still applies to v1 inbound calls unless the logic is handled based on version number explicitly in service activity?
Is it possible to change the service requestor AG based on version number before invoking the service activity .
Updated: 8 Jan 2021 10:21 EST
Masking Technology
NL
Hello Bramesh,
When you use a custom authentication service on your service package rule, you can do whatever you want during authentication. Including setting the access group of the operator.
On your server there is probably an example you can look at. The most important part of the authentication activity is to set the pyOperPage parameter.
Met vriendelijke groet, Bas Meeuwissen