Custom Workflow Steps migration to AEM 6.4

Avatar

Avatar

Vasily_Lazerko

Avatar

Vasily_Lazerko

Vasily_Lazerko

03-09-2018

The workflow steps were inherited from cq/workflow/components/model/process as described in Extending Workflow Functionality.

AEM 6.4 has all nodes under /libs/cq/workflow/components/model marked as final (granite:FinalArea).
What is the 6.4 recommended way to extend the workflow steps with the step dialog customization?

Replies

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

6.0K

Likes

1.1K

Correct Reply

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

6.0K

Likes

1.1K

Correct Reply

1.1K
kautuk_sahni
Community Manager

07-09-2018

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

3.1K

Likes

1.2K

Correct Reply

883

Avatar

Arun_Patidar

MVP

Total Posts

3.1K

Likes

1.2K

Correct Reply

883
Arun_Patidar
MVP

07-09-2018

Hi,

As suggested by Kautuk, Please check

Extending Workflow Functionality

Creating Custom Workflow Step Components

Workflow step components can be created in the same manner as any other component.

To inherit from one of the (existing) base step components, add the following property to the cq:Componentnode:

  • Name: sling:resourceSuperType
  • Type: String
  • Value: One of the following paths that resolves to a base component:
    • cq/workflow/components/model/process
    • cq/workflow/components/model/participant
    • cq/workflow/components/model/dynamic_participant

Avatar

Avatar

Vasily_Lazerko

Avatar

Vasily_Lazerko

Vasily_Lazerko

19-09-2018

AEM 6.4 added the granite:FinalArea to the property jcr:mixinTypes of the nodes above.

If we extend them with sling:resourceSuperType the Pattern Detector reports the Cross-boundary override of final marked path.

The question is how to extend the process without FinalArea violation?