AEM 6.2 Lock Payload workflow step behaving as NoOp | Community
Skip to main content
Level 2
July 12, 2017
Solved

AEM 6.2 Lock Payload workflow step behaving as NoOp

  • July 12, 2017
  • 15 replies
  • 9034 views

I've got a custom workflow with a "Lock Payload Process" step but it doesn't seem to function as expected. I get the following in the logs:

com.day.cq.workflow.impl.process.LockProcess Locking is not currently enabled.  This is a No-Op

I've tried setting the "cq.workflow.config.allow.locking" property of the "Adobe Granite Workflow Configuration Service" but that doesn't seem to fix it... Moreover, I'm able to lock the page via Touch UI just fine so locking is working on the repository.

Thanks for your help!

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 MC_Stuff

Hi Mick,

Not on granite but at  CQWorkflowService configure  cq.workflow.service.allow.locking

Thanks,

15 replies

MC_Stuff
MC_StuffAccepted solution
Level 10
July 12, 2017

Hi Mick,

Not on granite but at  CQWorkflowService configure  cq.workflow.service.allow.locking

Thanks,

Level 3
May 4, 2018

Hi ,

I have done the below steps as mentioned in the below URL after Upgrading from AEM 6.1 to AEM 6.3

and it's disabling the side-kick in classic UI..Is it a feature in AEM 6.3 or any other issue? Howe ever same thing working in Touch UI

Workflow lock/ unlock steps not working in AEM 6.3

Thanks,

arunpatidar
Community Advisor
Community Advisor
May 4, 2018

Hope below will help:

  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.
Arun Patidar
Level 3
May 4, 2018

I have done the same steps after content-administrator not able to approve the workflow from side-kick and it's disabling the properties as mentioned in above screen shot in Classic UI

arunpatidar
Community Advisor
Community Advisor
May 4, 2018

I tried same in AEM 6.3, I am able to complete workflow in both Touch and Classic UI.

The dialog will be disabled in classic UI only when user don't have rights to act to workflow.

Arun Patidar
Level 3
May 4, 2018

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,

arunpatidar
Community Advisor
Community Advisor
May 4, 2018

Are you able to complete workflow from Classic UI inbox?

http://localhost:4502/inbox

Arun Patidar
Level 3
May 7, 2018

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

sureshr19072451
Level 3
May 8, 2018

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.
sureshr19072451
Level 3
May 8, 2018

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.