The replacement for this API will be available by the end of June, 2024. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to August 30th.
Hi @colin_mckibben. I didn’t see the /cc/api/app/uploadCustomIcons API referenced anywhere in the API deprecations. Is this one being included as part of “update”?
The access profile enrollment does not happen if there is an identity update going on in the back end. This results in an error message: ((SLPT-1211) Your updates cannot be saved while a related task is running. Please try again later.) and the customer has to wait a long long time just to update one application.
Is it going to be fixed with the new API?
1 Like
Hello all. Will there be a PATCH /api/app/update/{addId} api route available eventually? I’m sure there are other patch uses cases but we have code that associates access profiles with apps and current state you have to go retrieve all the currently associated access profiles, add any new ones, and then make the post call. A patch ability would be great so you could just submit which access profile(s) you’d like to append.
+1 on this question. This is a huge pain point for our support teams and our Governance customers. We had to implement a complex process using an AWS queue, AWS Lambda, and some custom message submission tools in order to work around this and it’s still a pinpoint as it can sometimes take up to 24 hours before access profiles can be associated with apps.
We are using workato recipe to make calls on interval as it never works with single call.
The replacement for this API will be available by the end of June, 2024. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to August 30th.
1 Like
Is the same api as /cc/api/app/update/
We are trying to migrate all of these over to the newer api’s so I am just double checking.
Yes, this is the same the API as you described. The end of life date has been pushed back to august.