Custom Workflow Steps migration to AEM 6.4

Avatar

Avatar
Level 1
Vasily_Lazerko
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
Vasily_Lazerko
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile
Vasily_Lazerko
Level 1

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
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,199 likes

Total Posts

6,394 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,199 likes

Total Posts

6,394 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

07-09-2018

Avatar

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,442 likes

Total Posts

3,314 posts

Correct reply

941 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,442 likes

Total Posts

3,314 posts

Correct reply

941 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile
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
Level 1
Vasily_Lazerko
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
Vasily_Lazerko
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile
Vasily_Lazerko
Level 1

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?