Genesys Cloud - Developer Community!

I learned that the relevant API was fixed on April 7 by inquiring with customer care.

■API: /api/v2/analytics/queues/observations/query

■Modifications:
- Before Fix:
The API could be executed without sufficient permission"analytics:queueObservation:view".

- After Fix:
The API cannot be executed without permission"analytics:queueObservation:view", and an error is displayed correctly.

The case owner responded that it is documented in existing documents, so it is not included in the "release notes." However, could you explain why it is not mentioned in the Bug fix?

Hello Nobuhisa,

I think I was able to track down the case that you had opened with Customer Care (#0003728842). After reviewing the case notes, we fixed an incorrect response that the /api/v2/analytics/queues/observations/query API call was returning. Previously, it would incorrectly return a 200 - successful operation response instead of the correct 403 - You are not authorized to perform the requested action response. We do not document every small change that is made to the platform, which is why this change does not show up in the Release Notes.

I learned that the relevant API was fixed on April 7 by inquiring with customer care.

■API: /api/v2/analytics/queues/observations/query

■Modifications:
- Before Fix:
The API could be executed without sufficient permission"analytics:queueObservation:view".

- After Fix:
The API cannot be executed without permission"analytics:queueObservation:view", and an error is displayed correctly.

The case owner responded that it is documented in existing documents, so it is not included in the "release notes." However, could you explain why it is not mentioned in the Bug fix?

Hi Jason,

Thank you for your response.

What I want to confirm is not why it wasn't mentioned in the release notes, but why it wasn't notified as a "Bug fix" in the "Genesys Cloud Developer Forum." I understand that changes to the API are noted as "Bug fixes" in the "Genesys Cloud Developer Forum."

regards,

Iwashima

Hello Nobuhisa,

I think I was able to track down the case that you had opened with Customer Care (#0003728842). After reviewing the case notes, we fixed an incorrect response that the /api/v2/analytics/queues/observations/query API call was returning. Previously, it would incorrectly return a 200 - successful operation response instead of the correct 403 - You are not authorized to perform the requested action response. We do not document every small change that is made to the platform, which is why this change does not show up in the Release Notes.

I learned that the relevant API was fixed on April 7 by inquiring with customer care.

■API: /api/v2/analytics/queues/observations/query

■Modifications:
- Before Fix:
The API could be executed without sufficient permission"analytics:queueObservation:view".

- After Fix:
The API cannot be executed without permission"analytics:queueObservation:view", and an error is displayed correctly.

The case owner responded that it is documented in existing documents, so it is not included in the "release notes." However, could you explain why it is not mentioned in the Bug fix?

Hi Jason,

Thank you for your response.

What I want to confirm is not why it wasn't mentioned in the release notes, but why it wasn't notified as a "Bug fix" in the "Genesys Cloud Developer Forum." I understand that changes to the API are noted as "Bug fixes" in the "Genesys Cloud Developer Forum."

regards,

Iwashima

Hello Nobuhisa,

I think I was able to track down the case that you had opened with Customer Care (#0003728842). After reviewing the case notes, we fixed an incorrect response that the /api/v2/analytics/queues/observations/query API call was returning. Previously, it would incorrectly return a 200 - successful operation response instead of the correct 403 - You are not authorized to perform the requested action response. We do not document every small change that is made to the platform, which is why this change does not show up in the Release Notes.

I learned that the relevant API was fixed on April 7 by inquiring with customer care.

■API: /api/v2/analytics/queues/observations/query

■Modifications:
- Before Fix:
The API could be executed without sufficient permission"analytics:queueObservation:view".

- After Fix:
The API cannot be executed without permission"analytics:queueObservation:view", and an error is displayed correctly.

The case owner responded that it is documented in existing documents, so it is not included in the "release notes." However, could you explain why it is not mentioned in the Bug fix?

Hi Nobuhisa,

We do not put bug fixes in the release notes.  The release notes are intended to be for new feature releases and deprecation fixes.  Not every bug fix on the platform is released in the release notes or published on the Developer Forum.  I hope that helps.

Thanks,
    John

Hi Jason,

Thank you for your response.

What I want to confirm is not why it wasn't mentioned in the release notes, but why it wasn't notified as a "Bug fix" in the "Genesys Cloud Developer Forum." I understand that changes to the API are noted as "Bug fixes" in the "Genesys Cloud Developer Forum."

regards,

Iwashima

Hello Nobuhisa,

I think I was able to track down the case that you had opened with Customer Care (#0003728842). After reviewing the case notes, we fixed an incorrect response that the /api/v2/analytics/queues/observations/query API call was returning. Previously, it would incorrectly return a 200 - successful operation response instead of the correct 403 - You are not authorized to perform the requested action response. We do not document every small change that is made to the platform, which is why this change does not show up in the Release Notes.

I learned that the relevant API was fixed on April 7 by inquiring with customer care.

■API: /api/v2/analytics/queues/observations/query

■Modifications:
- Before Fix:
The API could be executed without sufficient permission"analytics:queueObservation:view".

- After Fix:
The API cannot be executed without permission"analytics:queueObservation:view", and an error is displayed correctly.

The case owner responded that it is documented in existing documents, so it is not included in the "release notes." However, could you explain why it is not mentioned in the Bug fix?

Hi Nobuhisa,

We do not put bug fixes in the release notes.  The release notes are intended to be for new feature releases and deprecation fixes.  Not every bug fix on the platform is released in the release notes or published on the Developer Forum.  I hope that helps.

Thanks,
    John

Hi Jason,

Thank you for your response.

What I want to confirm is not why it wasn't mentioned in the release notes, but why it wasn't notified as a "Bug fix" in the "Genesys Cloud Developer Forum." I understand that changes to the API are noted as "Bug fixes" in the "Genesys Cloud Developer Forum."

regards,

Iwashima

Hello Nobuhisa,

I think I was able to track down the case that you had opened with Customer Care (#0003728842). After reviewing the case notes, we fixed an incorrect response that the /api/v2/analytics/queues/observations/query API call was returning. Previously, it would incorrectly return a 200 - successful operation response instead of the correct 403 - You are not authorized to perform the requested action response. We do not document every small change that is made to the platform, which is why this change does not show up in the Release Notes.

I learned that the relevant API was fixed on April 7 by inquiring with customer care.

■API: /api/v2/analytics/queues/observations/query

■Modifications:
- Before Fix:
The API could be executed without sufficient permission"analytics:queueObservation:view".

- After Fix:
The API cannot be executed without permission"analytics:queueObservation:view", and an error is displayed correctly.

The case owner responded that it is documented in existing documents, so it is not included in the "release notes." However, could you explain why it is not mentioned in the Bug fix?