Pattern detector suspicions | Community
Skip to main content
D
dee_pdsj
Level 2
January 4, 2021
Solved

Pattern detector suspicions

  • January 4, 2021
  • 2 replies
  • 1614 views

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?

 

 

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 sunjot16

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 !!

2 replies

SureshDhulipudi
Community Advisor
SureshDhulipudiCommunity Advisor
Community Advisor
January 4, 2021

Above mentioned CAV issues are NOT mandatory to be fixed for Up- grading to 6.5 but it is recommended to be picked up as a post upgrade activity.

If these functions are working as expected, proceed and complete with your upgrade and post up grade, see if these can be addressed, don’t have any immediate issues post upgrade to AEM 6.5

CAV – Content Area Violation, refer https://helpx.adobe.com/experience-manager/pattern-de-tection/CAV.html

 

Please refer to following link to get more details on Pattern Detector -
https://helpx.adobe.com/experience-manager/6-5/sites/deploying/using/pattern-de- tector.html

    sunjot16
    Adobe Employee
    sunjot16Adobe EmployeeAccepted solution
    Adobe Employee
    January 4, 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 !!

      Terms & ConditionsAccessibility statement

      Loading footer...