/circulation/requests/allowed-service-points endpoint accepts requesterId parameter to determine requester’s patron group and use it for circulation rules execution. In ECS TLR context, this patron won’t exist in the data tenant when we’re requesting allowed service points because we only create (clone) the requester from central to data tenant during request creation. Allowed service points are needed by UI before request creation, obviously. To resolve this conflict, mod-circulation needs to accept a new parameter - patronGroupId. It can be used in circulation rules directly instead of requesterId, but one of these parameters (and only one) should always be present:

• patronGroupId parameter only - VALID

• requesterId parameter only - VALID

• Both patronGroupId and requesterId

• None of the patronGroupId and requesterId - INVALID

Important: Other parameters (such as instanceId, itemId, useStubItem, ecsRequestRouting) shouldn’t be affected by this change.

Note: This change only needs to be merged into ecs-tlr-feature branch.