AEM as Cloud Service - Rollback to Previous Release | Community
Skip to main content
Asutosh_Jena_
Community Advisor
Community Advisor
January 13, 2023
Solved

AEM as Cloud Service - Rollback to Previous Release

  • January 13, 2023
  • 2 replies
  • 2292 views

We are observing the following issues after upgrading to the latest cloud release version 2022.12.10488.20221222T085327Z

  1. All the custom user group permissions are revoked and the user is now not able to edit any content. There is no change in permission but still the issue exists.
  2. <span> tags are getting removed from HTML markup.
  3. RTE styles are getting removed i.e. <p style="text-align: right;"><b>US-NON-1234v1.0 02/20</b></p> is shown as <p style><b>US-NON-1234v1.0 02/20</b></p> 

The above issues are reproducible on local SDK as well.

 

Is there any way we can roll back to the previous version of SDK as Adobe is not responding to the support ticket on priority?

 

Thanks,

Asutosh

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Please request a rollback via support (this is known issue with 10488).

2 replies

nitesh_kumar-1
Adobe Employee
Adobe Employee
January 13, 2023

Hi @asutosh_jena_ ,

 

AFAIK, you need to contact support for this.

 

Have you raised a P1 ticket? That is always taken on priority if it qualifies, you can add business justification and impact.

 

Also, you should have some contacts or escalation matrix provided by Adobe, your customer would have this information.

 

There is a support through call as well, not sure if you have tried already.

https://helpx.adobe.com/entp/enterprise-phone-numbers.html 

 

Hope this helps!

 

Regards,

Nitesh

Asutosh_Jena_
Community Advisor
Community Advisor
January 13, 2023

We have raised the ticket already but it cannot be marked as P1 as this issue does not occur on the production instance.

Asutosh_Jena_
Community Advisor
Community Advisor
January 13, 2023

You can call support team as they will first upgrade stage/prod instances only. hence issue must exist on production


They do not. It happens on the lower first and that's why we are unable to show this on PROD.

 

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
January 14, 2023

Please request a rollback via support (this is known issue with 10488).