lock process in custom workflow | Community
Skip to main content
Level 6
October 11, 2024
Solved

lock process in custom workflow

  • October 11, 2024
  • 1 reply
  • 526 views

Hello Community,

 

We have a requirement to lock the payload until the workflow is approved and finally unlock the payload as part of the workflow process. My question is: in the workflow, can the user add one or multiple pages? If it is a single page, I believe the OOTB unlock process step can lock the payload and unlock it once approved. However, in the case of multiple pages, the payload is a package and all the pages will be part of the package. In this scenario, will the lock process be capable of locking and unlocking the pages, or do we need to write some custom code to perform the lock/unlock for all the pages attached as part of the workflow? Can someone advise on this?

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 lukasz-m

Hi @test1234567,

OOTB lock/unlock steps support packages with multiple pages in it. In other words all pages included in the package will be locked via lock step, and unlocked via unlock step. Customization/changes for given scenario are not needed.

1 reply

lukasz-m
Community Advisor
lukasz-mCommunity AdvisorAccepted solution
Community Advisor
October 11, 2024

Hi @test1234567,

OOTB lock/unlock steps support packages with multiple pages in it. In other words all pages included in the package will be locked via lock step, and unlocked via unlock step. Customization/changes for given scenario are not needed.