Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Michel Kraaij - van den Berg (Michel Kraaij)
Anamata
Pega Lead on Quality Awareness, Pega CSSA, Pega Trainer, Testconsultant
Anamata
NL
Michel Kraaij Member since 2016 43 posts
Anamata
Posted: May 17, 2022
Last activity: May 17, 2022
Posted: 17 May 2022 6:40 EDT
Last activity: 17 May 2022 12:32 EDT
Closed

Update and delete Participant issue (DX API v2)

I'm currently experimenting with the 'Update Participant' and 'Delete Participant' APIs (v2). One of the required parameters is the participantID. I assumed that this participantID is unique to a specific workparty, however this is not the case. Internally the participantID seems to be mapped to pyWorkPartyUri. And pyWorkPartyUri doesn't have to be unique.

When I run the 'Delete Participant' API with a participantID (pyWorkPartyUri) that is used in more than one workparty instances, it deletes *all* of the instances using that pyWorkPartyUri.

When I run the 'Update Participant' API with a participantID (pyWorkPartyURI) that is used in more than one workparty instance, it doesn't update any of the instances using that pyWorkPartyUri.

Is this a bug in the current implementation?

PS. For Delete Participant: When the If-Match is missing or incorrect, no error is being displayed. HTTP 200 is returned with an empty body.

PPS. "Select Party" is a placeholder, not a participant_role


***Edited by Moderator Marije to add Capability tags***
To see attachments, please log in.
Pega Platform 8.7.1
Case Management
DX API

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice