Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED
Lock and unlock publish page using aem workflow
1 Accepted Solution
Correct answer by
This just a high level solution not exactly to your use case. But it will help to design your solution.
1. As soon workflow trigger. It will lock page.
2. You can use any Participant Chooser as per need. There are others which may be used for your need. You can have this before lock as per need.
3. Assigned reviewer can choose next step or you can write custom logic to move to next step as per your need.
4. Left Branch - If rejected. Assign this to workflow initiator(You can use ECMA script to get Workflow initiator)
5. Right Branch - If approved,
-> Reviewer can schedule publish. In this case activate step not required.
->You can write custom step, If this has to be done in workflow only(If don't want to use OOTB publish schedule)
-> Unlock Page
I hope this will help. Again, This is not the exact solution to your use case. But a high level solution as per how much I understood.
ECMA script function to get workflow initiator
function getParticipant() {
return workItem.getWorkflow().getInitiator();
}
Hi @bangar20
Sharing some code snippet!
To check page is published
public static Boolean isPublished(Resource resource) {
Boolean activated;
ReplicationStatus status = null;
activated = false;
if (resource != null) {
try {
Page page = resource.adaptTo(Page.class);
status = page.adaptTo(ReplicationStatus.class);
} catch (Exception e) {
LOG.debug(e.getMessage(), e);
}
if (status != null) {
activated = status.isActivated();
}
}
return activated;
}To check Page is locked
public class PageServiceImp implements PageService {
private final Logger logger = LoggerFactory.getLogger(getClass());
private String user = "";
private Session session;
//Inject a Sling ResourceResolverFactory
@Reference
private ResourceResolverFactory resolverFactory;
public String MovePage()
{
String pagePath = "/content/MovePage64/fr";
String newPagePath ="/content/MovePage64/en" ;
String templatePath = "/apps/AEMPage/templates/page-home";
String pageTitle = "AEM home page";
Page newPage;
PageManager pageManager;
ResourceResolver resolver = null;
String newPageName = "";
Map<String, Object> param = new HashMap<String, Object>();
param.put(ResourceResolverFactory.SUBSERVICE, "datapersist");
try {
//Invoke the adaptTo method to create a Session used to create a QueryManager
resolver = resolverFactory.getServiceResourceResolver(param);
Resource res = resolver.getResource(pagePath);
//Adapts the resource to another type - in this example to a com.day.cq.wcm.api.page
Page page = res.adaptTo(Page.class);
//Lock this page
page.lock();
logger.info("The page is locked!");
// session = resolver.adaptTo(Session.class);
return ""
} catch (Exception e) {
// TODO Auto-generated catch block
logger.info("&&&&& BIG ERROR" +e.getMessage());
}
return "" ;
}
}
To check page unlock
//Unlock this page page.unlock();
Refer above code snippet and customize your requirement in workflow.
Hope that helps!
Regards,
Santosh
Hi,
There are OOTB lock and unlock steps. You can use those within workflow model.
Arun Patidar
Hi,
You cannot unlock the page only for a user. If it is unlock then it can be acted by any of the user.
You can though lock the page.
You can use the approver/workflow initiator to lock by and once workflow is done, unlock step will unlock the page.
Select publish date and time can be part of first step where initiator can select that from custom dialog.
Arun Patidar
Correct answer by
This just a high level solution not exactly to your use case. But it will help to design your solution.
1. As soon workflow trigger. It will lock page.
2. You can use any Participant Chooser as per need. There are others which may be used for your need. You can have this before lock as per need.
3. Assigned reviewer can choose next step or you can write custom logic to move to next step as per your need.
4. Left Branch - If rejected. Assign this to workflow initiator(You can use ECMA script to get Workflow initiator)
5. Right Branch - If approved,
-> Reviewer can schedule publish. In this case activate step not required.
->You can write custom step, If this has to be done in workflow only(If don't want to use OOTB publish schedule)
-> Unlock Page
I hope this will help. Again, This is not the exact solution to your use case. But a high level solution as per how much I understood.
ECMA script function to get workflow initiator
function getParticipant() {
return workItem.getWorkflow().getInitiator();
}
I think @arunpatidar have given good clue about OOTB on this
I found a couple of links, check if these help -
- java - Workflow LockProcess AEM - Not locking the asset/page - Stack Overflow
- User Administration and Security - Locking a page can be performed when impersonating a user. However a page locked in this way can only then be unlocked as the user who was impersonated or a user with administrator privileges. Pages can not be unlocked by impersonating the user who locked the page. (this means that you can lock the page impersonating that system user who would unlock it in the last step of your custom workflow)
- AEM 6.2 Lock Payload workflow step behaving as NoOp
Regards,
Santosh
Related Conversations
