PCCE 12.5 api question regarding agent update

[Elliot Dierksen]

I have looked at the PCCE API guide, but I didn't find an answer to a question regarding updates to agents and supervisor. I am inferring that I need to get the existing agent information, make the changes to attribute that could have multiple values like supervised teams and skills groups, and the write back a complete list to PCCE. Is that correct? I don't see a way I could just add things to the list of skillGroups and supervisorTeams.

[rvaliyap · Accepted solution]

Hi Elliot,

There are update only parameters skillGroupsAdded, skillGroupsRemoved, agentAttributesAdded and agentAttributesRemoved which can be used to add/remove skill groups and attributes. But supervisorTeams should be the full set if you are updating it. Please refer the API reference guide for parameter details and payload.

Thanks

[Elliot Dierksen]

Thanks, I was looking at an older version of the API guide. I'll check that out. I have another question though. I can't seem to get a username query to work when I specify that as a specific search. This works.

https://cce-adminws.company.com/unifiedconfig/config/agent?q=e331759d

and this works

https://cce-adminws.company.com/unifiedconfig/config/agent?q=teams:(MY_TEAM)

But this does not work (meaning finds nothing).

https://cce-adminws.company.com/unifiedconfig/config/agent?q=usernames:(e331759d)

Any ideas? The API guide says this:

• usernames:(username1|username2|username3, ...) find all agents who belong to any of the specified
username. Up to fifteen usernames can be specified. The username name is fully matched.

[rvaliyap]

Hi Elliot,

There was an issue with user name advanced search which is resolved now. It is available as an ES for 12.5.2 release(https://software.cisco.com/download/specialrelease/2db89e92094d0403290db259080878a2).

Thanks

[Elliot Dierksen]

Good to know. Getting the newer ES on there could be a challenge though.

This is specified in the API guide, but I missed it on the first pass. You must include the "changeStamp" attribute when you "put" the update, or it will fail. Actually seems like a good sense way to keep from overwriting with data that is stale. Quite the challenge in a stateless environment!