Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Pattern detector suspicions

Avatar

Avatar
Validate 1
Level 1
dee_pdsj
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
dee_pdsj
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
dee_pdsj
Level 1

03-01-2021

Hi,

 

We are currently upgrading aem 6.4 to 6.5.7 version. When we ran pattern detector, we observed around 30+ suspicions in the report. There have been customizations done on the application overlaying the OOTB CQ Inbox, so we are seeing issues like below. Since there are suspicions, can these be ignored if the functionalities are working as expected in the first phase of upgrade?

 

pattern-detector.PNG

 

6.5 Upgrade AEM Pattern detector
View Entire Topic

Avatar

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

104 likes

Total Posts

164 posts

Correct Reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

104 likes

Total Posts

164 posts

Correct Reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile
sunjot16
Employee

04-01-2021

The reason why this happens:

* Some customers are provided with some hotfix for an issue, until the actual fix is released in any future updates/releases. Since the overlay exists(/apps), the actual fix(/libs) won't even show up as working, until that overlay is removed.

Moreover, the fixed file may have something more(e.g.: new feature/functionality or some optimization) than what exists in the overlay. Due to this, that new feature/functionality won't even work and thus, can result in other issues.

* Some customers overlay the OOTB functionalities to do customizations. Let's say, a new feature/functionality is released. The customers won't even be able to see that feature/functionality, until the overlay is removed. This could lead to several issues.

 

Once you remove/uninstall the overlays, do the upgrade and test OOTB functionalities first. Then, you can install your overlaid packages back. 🙂

 

Also, whenever you install some SP/CFP, always make sure that you uninstall the overlays and then do the installation, for similar reasons stated above. Then, you can install the overlaid package and/or modify your overlaid code on top of the OOTB feature/fix.

 

Hope it helps !!