AEMaaCS Build - Restricted Resourcetype Issue | Community
Skip to main content
Level 2
June 8, 2022
Solved

AEMaaCS Build - Restricted Resourcetype Issue

  • June 8, 2022
  • 1 reply
  • 777 views

Hi,

I am working on creating a custom workflow with participant steps, process steps and multiple "OR" steps. During the build process in CM, I am seeing the following "ERROR" as shown in the screenshot below.

Can someone please help with how to resolve this issue?

Thanks!!

 

 

 

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 Fanindra_Surat

Hi @nithindasyam - The path in your error is '/libs/cq/flow', and if you navigate to that particular path in AEM you would find that it belongs to the type 'granite:InternalArea', which by definition from Adobe docs can't be used directly.

  • Internal (granite:InternalArea) - Defines a node as internal. Nodes classified as internal cannot be overlaid, inherited, or used directly. These nodes are meant only for internal functionality of AEM.

Ref: https://experienceleague.adobe.com/docs/experience-manager-64/deploying/upgrading/sustainable-upgrades.html?lang=en

 

Please find the usage of this path in your custom code/components and re-evaluate if you can perform the same without referencing this path.

 

Reference to a similar thread - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-upgrade-cross-boundary-resource-type-usage-of-internal/m-p/305381

 

Thanks,

Fani

1 reply

Fanindra_Surat
Community Advisor
Fanindra_SuratCommunity AdvisorAccepted solution
Community Advisor
June 9, 2022

Hi @nithindasyam - The path in your error is '/libs/cq/flow', and if you navigate to that particular path in AEM you would find that it belongs to the type 'granite:InternalArea', which by definition from Adobe docs can't be used directly.

  • Internal (granite:InternalArea) - Defines a node as internal. Nodes classified as internal cannot be overlaid, inherited, or used directly. These nodes are meant only for internal functionality of AEM.

Ref: https://experienceleague.adobe.com/docs/experience-manager-64/deploying/upgrading/sustainable-upgrades.html?lang=en

 

Please find the usage of this path in your custom code/components and re-evaluate if you can perform the same without referencing this path.

 

Reference to a similar thread - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-upgrade-cross-boundary-resource-type-usage-of-internal/m-p/305381

 

Thanks,

Fani

Level 2
June 10, 2022

Hi @fanindra_surat, thanks for your response!

What is the correct resource type or alternative to adding workflow models or workflow steps in the code repository without getting this violation?