AEM trigger workflow from Java - Create translation project

Triggering workflow from Java and automate the process to create translation project using workflow.

Code snippet 

import com.day.cq.workflow.model.WorkflowModel; 

import com.day.cq.workflow.WorkflowService; 


@Reference

private WorkflowService workflowService;

WorkflowSession wfSession = workflowService.getWorkflowSession(session);

// We can have any workflow model here - For creating language copy I am using create_language_copy workflow.

String workflowName = "/var/workflow/models/wcm-translation/create_language_copy";

// Get the workflow model

WorkflowModel wfModel = wfSession.getModel(workflowName); 


String languageEnMasterPath = "master page path";

// Get the workflow data

// Workflow Data - Provide the master language page path from where the language copy to be created 

WorkflowData wfData = wfSession.newWorkflowData("JCR_PATH", languageEnMasterPath);

// Add meta data values

final Map<String, Object> workflowMetadata = new HashMap<>();

workflowMetadata.put("model", "/etc/workflow/models/wcm-translation/create_language_copy/jcr:content/model");

// If parent pages to be auto created when not present - false to not create

workflowMetadata.put("createNonEmptyAncestors", true);

// Pass true if child pages to be created

workflowMetadata.put("deep", false);

workflowMetadata.put("projectFolderLanguageRefCount", "Count of total language masters available");

// Pass comma separated languages list like en,fr,es etc. For only 1 language pass workflowMetadata.put("language", "fr")

workflowMetadata.put("languageList", "comma separated language list");

//Pass project type - add_structure_only will create only structure no translation will happen

workflowMetadata.put("projectType", "add_structure_only");

workflowMetadata.put("projectTitle", "");


// Run the Workflow.

wfSession.startWorkflow(wfModel, wfData, workflowMetadata);




Comments

Post a Comment

Popular posts from this blog

AEM integration with Akamai Fast Purge API for Single/multiple urls

Image
In AEM we can clear dispatcher cache on page activation by adding dispatcher flush agent but if we have Akamai on top of dispatcher as CDN then we need to manually clear Akamai Cache by going to akamai console. Akamai provides fast purge API and using that we can clear page cache using single URL, CPCode, multiple urls etc We can integrate Akamai Fast Purge API with replication agent so that for every page activation akamai cache gets cleared. To integrate with Akamai Fast Purge we need below details (Contact Akamai for details related to your account) 1) Access Token 2) Client Secret 3) Client Token 4) Akamai Host API End Points ( https://developer.akamai.com/api/core_features/fast_purge/v3.html ) Once above details are gathered you can refer below code for multiple urls cache clear Create a map with array list of urls  Map<String, List<String>> akamaiRequestMap = Maps.newHashMap(); ArrayList<String> arrayList = new ArrayList<>(); arrayList.add("Ad...
Read more

AEM Results count using query builder

Image
 Using below query builder we can get the list of pages/assets count returned in json format Page Count: http://localhost:4502/bin/querybuilder.json?path=/content/we-retail&property=jcr:primaryType&property.1_value=cq:Page&p.limit=-1 Assets Count: http://localhost:4502/bin/querybuilder.json?path=/content/dam&property=jcr:mimeType&property.1_value=image/gif&property.1_value=image/png&property.2_value=image/jpeg&property.3_value=image/svg+xml&p.limit=-1
Read more

AEM - Rollout a page programmatically and update references

 Out of the box RolloutManager provides below 3 methods by using that we can rollout the page programmatically. 1) void rollout(RolloutParams params) throws WCMException; 2) void rollout(ResourceResolver resolver, LiveRelationship relation, boolean reset) throws WCMException; 3) void rollout(ResourceResolver resolver, LiveRelationship relation, boolean reset, boolean autoSave) throws WCMException; But when using 2nd and 3rd method we are able to rollout the page but the link references are not getting updated to the corresponding locale. This is because we are not providing the rollout trigger in 2nd and 3rd methods, so referenceUpdate is not getting triggered.  In order to update the link references in the rollout page we need to use 1st method and pass/set the required details in RolloutParams class. Below is example code for setting the RolloutParams                               ...
Read more