Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Breaking change on Create Site

  • 1.  Breaking change on Create Site

    Posted 06-05-2025 18:49

    ngiannopoulos | 2020-10-12 21:29:50 UTC | #1

    Hi all, We are using Java SDK to create a new Site (postTelephonyProvidersEdgesSites). Today we noticed there is a breaking change that is not yet supported on the SDK. A new required field has been introduced but not supported on v106.0.0. The error is: "Field 'mediaModel' is required and cannot be empty." How can we add this field in our request? It seems it is not yet included in the SDK. Thank you.

    John_Carnell | 2020-10-13 01:18:12 UTC | #2

    Hi Nikos,

    Thanks for reaching out to us. Just one quick question. Is this API worked for you in the past in production and now it doesn't work. I have opened a ticket with our internal dev team, but can you please open a ticket with our Care group and reference this post and (ticket ES-10002). This will ensure we follow the right processes are followed and make sure that the ticket is getting tracked by our support organization. Here is a link to our care group.

    https://help.mypurecloud.com/articles/contact-genesys-cloud-care/

    Thanks, John Carnell

    P.S.

    As a workaround it does appear the UI still allows you to add sites so if you are blocked you can probably use this approach until we get this worked out.

    ngiannopoulos | 2020-10-13 07:49:53 UTC | #3

    Hi @John_Carnell, This API worked as expected in the past yes. Thankfully we didn't put anything in the production yet but such changes will definitely affect our planning. The proposed workaround does not work for us because we will be automating everything we need so we cannot break the process, add a manual step and then continue with the automated process. I will open a ticket with Care group as well.

    John_Carnell | 2020-10-13 11:44:51 UTC | #4

    Hi Nikos,

    I totally understand the automation piece. We do everything through automation too and manually setting up things is frowned up. I talked with the development team lead this morning and he is in agreement that this is a bug and is related to a feature toggle that was turned on. Unfortunately, the feature toggle is pretty broad and can not be turned off, so he is going to have the dev who wrote the code look at it as soon as he gets in. I would recommend you check the ticket on a regular basis that you opened up with CARE.

    Sorry for the inconvenience that this is causing you.

    Thanks, John

    John_Carnell | 2020-10-13 14:30:09 UTC | #5

    Hi Nikos,

    I received further information from the development team. They have turned off their feature toggle that caused this breaking change and you should be able to use the SDK again as before. The development and testing teams are taking a step back to see how they can avoid this in the future.

    Thanks, John Carnell

    ngiannopoulos | 2020-10-16 07:49:32 UTC | #6

    Hi John,

    Thank you for your immediate help. I can confirm we can use the SDK again without issues. We have an open ticket on CARE in case the feature is turned back on.

    Thanks, Nikos

    system | 2020-11-16 07:49:35 UTC | #7

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

    This post was migrated from the old Developer Forum.

    ref: 9034



Related Content