AEM 6.2 Lock Payload workflow step behaving as NoOp

Hello,

I am using a custom workflow process step to lock and unlock the page. But when I lock the page with a specific user, I am unable to unlock it until unless I login as the admin. Is there anyway that I can use the custom step to lock it through the workflow and the initiator(the person who starts the workflow) must be able to unlock the page.

Regarding the unlock I am not able to do it at all. I am using the page.unlock() same as page.lock().

Can some one please help me out on this.

Hi,

Only lock acquiring user or admin can unlock the page.

I would suggest to unlock page using either in different workflow or same workflow using another process step. I used OOTB lock and unlock steps to achieve same.

@Arunpatidar thanks for the response. Here we have a specific use case where an initiator can  unlock the page manually. So we need to use custom workflow process step not the OOTB Lock and Unlock steps. While doing this if the initiator is trying to unlock the page it is saying to reach out to admin to get the page unlock. can we achieve the same functionality as Only lock acquiring user or admin can unlock the page??????? by using custom process step

I am using the different process step to unlock the page by using page.unlock() but this is not working where when used page.lock() is working fine. This is a custom process step.

Hello All,

I tried both OOTB workflow process and custom workflow process to Lock and Unlock the page. The page is getting locked and unlocked using service user but my requirement is this lock and unlock should be acquired by author/Initiator. Can someone help me out on this to achieve this functionality.

You can check AEM 6.3 Custom Lock - Lock payload by logged in user