Posted: 9 Nov 2020 2:27 EST Last activity: 8 Jan 2021 10:21 EST
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
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 .