Workflow failing in the second iteration | Community
Skip to main content
Level 2
October 16, 2015
Solved

Workflow failing in the second iteration

  • October 16, 2015
  • 11 replies
  • 3095 views

ISSUE:

The workflow we require is a multi-approval workflow which means once the author create the content it gets reviewed and approved by 2 roles (First by a Brand Manager and then finally by a Brand Director). The workflow works as expected if both Brand Manager and the Brand Director approves the content in the first go. However in a specific case where the Brand director is rejecting the content the 2nd iteration breaks. Below is the flow which is breaking (Steps to reproduce):

  1. Editor create the content and send it to Brand Manager for approval. (Use any geometrixx page. Put it in the workflow and from the inbox assign it to manager.)
  2. Brand Manager approves it and send it to Brand Director for the final review.
  3. Brand Director rejects the content. (For the rejection process we are using a custom process. The source code for the same is in the attached bundle. We tried using the go to step available with 5.6.1 but it doesn't seems to work.)
  4. The content is now back with the editor with the rejection comment.
  5. The editor changes the content and send it back to the Brand Manager.
  6. The Brand Manager approves the content and send it to the Brand Director for the final approval.
  7. At this step the Brand director is unable to do anything. He is not able to approve/reject the content.

 Package details:

I do have a package which one can use as is to reproduce the issue on a vanilla instance of AEM 5.6.1. However just learned that i cant attach a zip file in this forum. Anyone willing to help me please reply back and i can share the package by any possible way.

Screenshot:

Here is the screenshot of our workflow model.

 [img]acme workflow.PNG[/img]

Appreciate any help in investigating or suggesting if anyone has achieved a similar flow using a different approach.

thanks,
Himanshu

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 Himanshu_Pathak

Hi Kish,

Thanks for asking the question. Gives me an opportunity to get this thread to a logical conclusion. Adobe finally provided a hotfix to resolve the issue. The hotfix number is NPR-3850.

You can check the hotfix details at https://helpx.adobe.com/experience-manager/kb/cq561-available-hotfixes.html and request adobe for the same.

thanks,

Himanshu

11 replies

Adobe Employee
October 16, 2015

Hi,

Can you explain why the built-in GOTO step for 5.6.1 did not work?  

As for looking at this in great detail, the best thing for you to do is log a daycare ticket so it gets prioritized properly.

Thanks,

Will

Sham_HC
Level 10
October 16, 2015

hope you are using granite api. What is the error. You can provide link of zip file by attaching at sendnow https://www.acrobat.com/sendnow/en/home.html

Level 2
October 16, 2015

Thanks for the quick response Will and Sham.

@Will, I tried using the GOTO step at the beginning but it simply didn't work for us. Since we used a custom process in the previous project (CQ5.5) we adopted the same approach. I have raised an adobe ticket for the same and the support person suggested me to reach out to these forums for experts opinion.

@Sham, Not sure i am answering your question correctly but in our workflow model we have used out of the box participant steps and one custom process which is written by extending com.day.cq.workflow.exec.WorkflowProcess. There are no errors in the logs. I have tried sending the zip to myself using sendnow and the same is available https://sendnow.acrobat.com/?i=0qQDXD96okHMRHyhbIYiYA

Package Details:

acme-editorial-workflow.zip is the package which contains workflow model, user-groups, users associated with the groups and access permissions.

While importing please make sure that the Access Control Handling option is set to Overwrite (this should populate automatically as i have taken care of this while building the package.)

the users are 'editor', 'manager', 'director'. Password for all of them is 'password'.

Once again really appreciate your help on this.

thanks,

Himanshu

Sham_HC
Level 10
October 16, 2015

Had a quick look at code. Seems you are still using com.day.cq.workflow please use granite api.

Level 2
October 16, 2015

Hi Sham,

I rewrote the class using the granite APIs but that didn't solve the issue. The behavior remains exactly the same.

Thanks,

Himanshu

Sham_HC
Level 10
October 16, 2015

Hi Himanshu,

Can you send your latest package. Let me try in local instance.

Thanks,
Sham

Level 2
October 16, 2015

Hi Sham,

You can get the latest at https://sendnow.acrobat.com/?i=nNuMSotRQdkT8ILb0TIing

 

Thanks,

Himanshu

Level 3
October 16, 2015

Hi Himanshu,

I am using Adobe CQ5.5. I am also writing similar kind of Use Case but OOTB Step Back and Delegate are not working for the second Iteration. I used all OOTB steps. I used Workflow Initiator Script for Rejection. Can you explain about your Custom Step written for Adobe CQ5.5. Please let me know or can you share the sample code so that i can go through that as an reference.

Thanks a lot in advance

Himanshu_PathakAuthorAccepted solution
Level 2
October 16, 2015

Hi Kish,

Thanks for asking the question. Gives me an opportunity to get this thread to a logical conclusion. Adobe finally provided a hotfix to resolve the issue. The hotfix number is NPR-3850.

You can check the hotfix details at https://helpx.adobe.com/experience-manager/kb/cq561-available-hotfixes.html and request adobe for the same.

thanks,

Himanshu

Level 3
October 16, 2015

Thank You so much for the information Himanshu. This helps.

As of now i a using Adobe CQ5.5. I am not sure if this hotfix solves the issue in 5.5. 

If you can provide an idea how you managed to write custom step for CQ5.5 . can you share the code if possible?