SDK Deprecations Announcements

Lucas_Arruda_Fernand · June 22, 2021, 4:21pm

Hi,

This topic is being created as suggested in support ticket 0002939890

The main point here is to understand if all Platform API deprecations are announced here https://developer.genesys.cloud/forum/c/announcements/20

The point being that WorkforceManagementApi().GetWorkforcemanagementManagementunit was removed from C# Platform API SDK and I don't see this deprecation anywhere.

tim.smith · June 22, 2021, 5:28pm

You are correct that removals will be announced in that category. In this case, however, there wasn't an announcement because nothing was removed; as far as I can tell, that method has never existed in the .NET SDK. It appears that API resource was first available on 6/2, but the latest build of the .NET SDK was on 5/20. If I'm wrong and it did exist in the past, please let me know what SDK version contains this method and I'll dig in deeper.

I've initiated a new build of all of the SDKs as they appear to have fallen out of date with the API's definition. Keep an eye on the github repo for a new release coming soon today. https://github.com/MyPureCloud/platform-client-sdk-dotnet/releases

Lucas_Arruda_Fernand · June 23, 2021, 1:31pm

Hi Tim,

This method was available at version 117, have a look:

tim.smith · June 23, 2021, 1:36pm

Thanks, I was spot checking old versions and missed it. I've involved our release management teams to investigate how this happened; removing released resources without an announcement goes against our standard procedure.

Lucas_Arruda_Fernand · July 7, 2021, 1:33pm

Hi Tim, any news about this ?

tim.smith · July 7, 2021, 1:35pm

What sort of news are you looking for? Have you been watching the releases page linked above?

Lucas_Arruda_Fernand · July 7, 2021, 2:25pm

I mean, news from your post:

tim.smith · July 7, 2021, 2:27pm

If you're looking for a RCA, please open a case with Genesys Cloud Care; RCAs are not communicated via the forum.

If you're looking for the release, check the releases page linked above.

Eos_Rios · July 8, 2021, 1:35pm

Just like it wasn't mentioned in the release notes when it was removed in 118, it also wasn't mentioned in the release notes when it was put back in 123.

tim.smith · July 8, 2021, 1:38pm

Please refer to the release notes for that version that document that the /api/v2/workforcemanagement/managementunits/{managementUnitId} API resource was added:

github.com

MyPureCloud/platform-client-sdk-dotnet/blob/123.0.0/releaseNotes.md

Platform API version: 4784


# Major Changes (38 changes)

**GET /api/v2/journey/actiontemplates** (2 changes)

* Parameter queryFields was added
* Parameter queryValue was added

**GET /api/v2/telephony/providers/edges/linebasesettings** (1 change)

* Parameter expand was added

**GET /api/v2/journey/outcomes** (2 changes)

* Parameter queryFields was added
* Parameter queryValue was added

**GET /api/v2/quality/conversations/{conversationId}/audits** (1 change)

This file has been truncated. show original

tim.smith · July 8, 2021, 1:39pm

It's also the very first thing in the release notes for 118:

github.com

MyPureCloud/platform-client-sdk-dotnet/blob/118.0.0/releaseNotes.md

Platform API version: 4585


# Major Changes (27 changes)

**/api/v2/workforcemanagement/managementunits/{managementUnitId}** (1 change)

* Path /api/v2/workforcemanagement/managementunits/{managementUnitId} was removed

**GET /api/v2/conversations/messaging/integrations/twitter** (2 changes)

* Parameter expand was added
* Parameter supportedContent.id was added

**GET /api/v2/flows/milestones** (1 change)

* Parameter divisionId was added

**GET /api/v2/conversations/messaging/integrations** (2 changes)

This file has been truncated. show original

Eos_Rios · July 8, 2021, 1:49pm

I stand corrected, but the fact it was notated after the fact in the release notes of the library itself doesn't qualify it as having been an announced change, and the fact it got put back still proves this was a fiasco and your support on the matter has been pretty poor. Thank you for reporting it to the team that actually fixed it, but if case management hadn't deflected this here it could've been handled better. The lack of ownership from Genesys is distressing.

tim.smith · July 8, 2021, 2:20pm

Could you share this case number please?

Eos_Rios · July 8, 2021, 2:43pm

From the original post:

tim.smith · July 8, 2021, 2:45pm

Ah, I didn't realize you were referring to the case posted above since you're not the original author. Thanks.

Becky_Powell · July 8, 2021, 3:11pm

Thank you for bringing this matter to our attention. First off, I am terribly sorry to hear about your experience here. I will work directly with our Care team as well as the service team who owns this route to find out how this change escaped our standard change policy and to debrief on how Genesys could have better managed this case.

I will post my findings here, but please feel free to email me directly at becky.powell@genesys.com if you would like me to follow up with you directly.

Kind regards,
Becky Powell
Director, Product Management

Becky_Powell · July 13, 2021, 5:41pm

We've determined the root cause of the visibility change to this route. The route was not actually removed from service - rather, there was a bug that temporarily hid it from swagger, which caused it to not be generated in the SDK. This was an edge-case bug that has been fully fixed.

We have also met with our Customer Care team to address the improper handoff to the Developer Forum and have introduced measures to better handle such cases moving forward.

Thank you for bringing this matter to our attention. Should you have any questions or wish to discuss further, please feel free to email me directly at becky.powell@genesys.com.

Best,
Becky Powell
Director, Genesys Cloud Product management

system · August 13, 2021, 5:47pm

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.