To get list of published pages from a specific workflow

Hi @newbie34,

In a Sling Job Consumer service, you’re working in an OSGi background thread, not a script or servlet. Therefore:

• There's no current HTTP request (SlingHttpServletRequest)

• There's no SlingBindings, so no automatic resource injection

• You must explicitly resolve a resource using the ResourceResolver API

You can Manually get the resource using a ResourceResolver

If you know the path to the resource (e.g., /var/workflow/instances/...), you can adapt it manually in your Sling Job like this:

Example Code in a Sling Job Consumer:

@Component(service = JobConsumer.class, immediate = true,
           property = { JobConsumer.PROPERTY_TOPICS + "=your/job/topic" })
public class WorkflowPageTrackerJob implements JobConsumer {

    @Reference
    private ResourceResolverFactory resolverFactory;

    @Override
    public JobResult process(Job job) {
        Map<String, Object> authInfo = new HashMap<>();
        authInfo.put(ResourceResolverFactory.SUBSERVICE, "your-subservice-name");

        try (ResourceResolver resolver = resolverFactory.getServiceResourceResolver(authInfo)) {

            String workflowPath = "/var/workflow/instances/server0/2024-05-21/model_123456"; // example
            Resource resource = resolver.getResource(workflowPath);

            if (resource != null) {
                // Access workflow metadata
                ValueMap properties = resource.getValueMap();
                String state = properties.get("state", String.class);
                // etc.
            }

        } catch (LoginException e) {
            // handle
        }

        return JobResult.OK;
    }
}

Steps you must take:

1. Create a System User and map it in user.mapping in your org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended config.

2. Use the ResourceResolverFactory.getServiceResourceResolver() to get a safe session.

3. Access the workflow resource like /var/workflow/instances/...

4. Extract and filter based on state = COMPLETED, model ID, or payload path.

Optional: Use WorkflowSession if Needed

If you need more than just reading the resource (e.g., interacting with the workflow API), you can also adapt WorkflowSession:

WorkflowSession wfSession = workflowService.getWorkflowSession(session);
List<Workflow> workflows = wfSession.getAllWorkflows(WorkflowState.COMPLETED);

 Hope that helps!

Hi @newbie34 ,

Use a Sling Job Consumer – this runs in the background and doesn't need an HTTP request.

Read workflow data from /var/workflow/instances

Filter the workflows:

  - Only those with status = COMPLETED

  - Only those that used your target workflow model (e.g., /var/workflow/models/publish-page-workflow)

  - Only payloads that start with /content/ (these are pages)

  - Only those that were completed in the last 7 days

1. Create a System User

In CRXDE: create workflow-tracker-service-user under /home/users/system/your-project

Give it read access to /var/workflow/instances

2. Map the Service User

In OSGi config (ServiceUserMapper):

Java Code Example (Sling Job Consumer)

Regards,
Amit