Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

AEMaaCS Build - Restricted Resourcetype Issue

Avatar

Level 2

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.

Screen Shot 2022-06-07 at 9.20.26 AM.png

Can someone please help with how to resolve this issue?

Thanks!!

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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-upgrad...

 

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-boun...

 

Thanks,

Fani

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

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-upgrad...

 

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-boun...

 

Thanks,

Fani

Avatar

Level 2

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?