AEM 6.2 Lock Payload workflow step behaving as NoOp

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

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.

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

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.

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.

In my test, adding "workflow-user" seems to have solved the problem in first attempt of testing, will post if there are any further updates.

For those who are reading this understand that this user won't exist in 6.3 anymore if its a fresh install. But if if you do any in place upgrade let's say from 6.1 to 6.3, you will find this user in useradmin screen.

Also, I believe in the list of steps provided, should we not change the service users that is configured to lock and unlock the payload based on workflow model definition? Please see the highlighted section below - In my case, applying the below steps didn't work. I will try to change the service users to our custom user group/user and update the results.

In my case, This issue should be fixed for workflow packages.

Workflow lock/ unlock steps not working in AEM 6.3

  To apply configurations to allow the Lock/ Unlock processes to function in AEM 6.3, follow these steps:

•   Go to http://host:port/system/console/configMgr.
•   Find Day CQ Workflow Service.
•   Mark Enable Lock/Unlock Process to true.
•   Click Save.
•   Find Adobe Granite Repository Service User Configuration, and add a new configuration.
•   Set Simple Subject Population to true.
•   Set Service Users to workflow-process-service.
•   Click Save.

Yes, I am getting notification to inbox but why in classic UI i am not able complete through side-kick?

Are you able to complete workflow from Classic UI inbox?

http://localhost:4502/inbox

Thank for prompt reply,

I have provide the admin right and able to complete the same process as mentioned in my screen shot in Touch UI?

But the same thing disabling in classic UI why? Please find the below Touch UI screen shot where I am to complete the process for the same rights?

Thanks,