Hello:
I have the next problem, I created a custom workflow process and it does not appears on the process list on the dropdown field ( process step) ,
but If I change the version of :
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-scr-plugin</artifactId>
<version>1.23.0</version>
</plugin>
from 1.23.0 to 1.20.0 this appears correctly and works.
I tried this answer from this forum but it does not work for me Custom Workflow Step Not Showing up in Process List Dropdown
I tried this link also AEM Developer Learning : July 2017 like possible solution ( it is the most recent article I have found) but this does not work for maven-scr-plugin version 1.23.0
We need to keep maven-scr-plugin on version 1.23.0 to guarantee the stability of our project.
Here is an example of Workflow process we are using.
import org.apache.felix.scr.annotations.Component;
import org.apache.felix.scr.annotations.Properties;
import org.apache.felix.scr.annotations.Property;
import org.apache.felix.scr.annotations.Service;
import org.osgi.framework.Constants;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import com.day.cq.workflow.WorkflowException;
import com.day.cq.workflow.WorkflowSession;
import com.day.cq.workflow.exec.WorkItem;
import com.day.cq.workflow.exec.WorkflowProcess;
import com.day.cq.workflow.metadata.MetaDataMap;
@Component
@Service
@Properties({
@Property(name = Constants.SERVICE_DESCRIPTION, value = "Testing workflow"),
@Property(name = Constants.SERVICE_VENDOR, value = "TEST"),
@Property(name = "process.label", value = "Testing workflow test") })
public class WorkFlowTest implements WorkflowProcess{
private static final Logger LOG = LoggerFactory.getLogger(WorkFlowTest.class);
@Override
public void execute(WorkItem arg0, WorkflowSession arg1, MetaDataMap arg2) throws WorkflowException {
// TODO Auto-generated method stub
LOG.info("Hellooooooooooooooooooo testing !!!!!!!");
}
}
There is any way to implement a custom Workflow Process without changing the version of maven-scr-plugin?
Thank you.
Solved! Go to Solution.
Views
Replies
Total Likes
Finally I figured out what was missing:
Was missing add the line @Property(name = "service.pid", value = "com.test.yourpackage.name.WorkFlowTest"), so the Java class will be like it is:
The solution was the line number 20.
Views
Replies
Total Likes
Did you try generating your workflow step by using Maven 10 Archetype - which is the recommended version to use for 6.2.
Views
Replies
Total Likes
I will test that too right now on AEM 6.2 and post back my findings.
Views
Replies
Total Likes
I just tested our article on 6.2 and it works -- see: Adobe Experience Manager Help | Creating custom AEM workflow steps that send email messages
Views
Replies
Total Likes
Finally I figured out what was missing:
Was missing add the line @Property(name = "service.pid", value = "com.test.yourpackage.name.WorkFlowTest"), so the Java class will be like it is:
The solution was the line number 20.
Views
Replies
Total Likes
Hi,
Eventually it is working without property - service.pid as per the article. We have tested article many times.
Also, We will add that line no 20 in HELPX article when smacdonald2008 back to work!!
Thanks,
Ratna.
Views
Replies
Total Likes
Views
Likes
Replies