UCCE Finesse 12.0 REST API help for NOT_READY
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2020 04:43 PM
HI,
I am trying to play around the REST API to import NOT_READY. I am getting this error when I try to do this through postman.
https://developer.cisco.com/docs/finesse/#!reasoncodecreate/reasoncodecreate
I get error 403 which is but I am running this on pub (per the lab setup I finesse server only)
403 | Forbidden | The user attempted to run the API against the secondary Finesse server. Configuration APIs cannot be run against the secondary Finesse server. |
Here is the POST to http://10.10.20.50/finesse/api/ReasonCode
with Admin/Supplied password/data
where date =
<ReasonCode> <category>NOT_READY</category> <code>34</code> <label>TestLunch</label> <forAll>true</forAll> </ReasonCode>
Error I get is "Forbidden finesse.api.reasoncode.nonspog.forbidden. This resource cannot be modified from this portal.
Either I am getting the wrong error code from the API or I am running this command against the Fin sub which is not the case.
Thanks in advance.
Senthil
- Labels:
-
Other Sandbox Issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2020 05:31 PM
I think I may know the answer.
It looks like REST reason codes API are disabled in Finesse due to the new "SPOG" in PCCE 12.0. which means I have to create them only from SPOG interface and further debug proved that it uses JSON method to input the reason codes through the cceadmin API in awhds.
I hope Cisco updates this or let me know if I am doing something wrong.
I can create the reason codes in Finesse cfadmin page but it is not showing in SPOG interface. However if I create a new reason codes in SPOG, I do see them in cfadmin page.
-Senthil
