Workflows deployed under /conf are not active in aem as cloud service.

Forum|Forum|1 year ago
January 10, 2025
2 replies
996 views

I have created a custom workflow under '/conf/global/settings/workflow/models' and deployed to aem I am able to see the workflows in crx/de but not visible in 'http://localhost:4502/libs/cq/workflow/admin/console/content/models.html'also the workflow is not present under '/var/workflow/models'

below is the .content.xml file of the wf:

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:jcr="http://www.jcp.org/jcr/1.0"
          xmlns:nt="http://www.jcp.org/jcr/nt/1.0"
          xmlns:cq="http://www.day.com/jcr/cq/1.0"
          xmlns:sling="http://sling.apache.org/jcr/sling/1.0"
          jcr:primaryType="cq:Page">

    <jcr:content
        cq:designPath="/libs/settings/wcm/designs/default"
        cq:lastModified="{Date}2025-01-09T05:48:13.628Z"
        cq:lastModifiedBy="admin"
        cq:template="/libs/cq/workflow/templates/model"
        jcr:primaryType="cq:PageContent"
        jcr:title="test-wf"
        sling:resourceType="cq/workflow/components/pages/model"
        lastSynced="{Date}2025-01-09T05:48:13.680Z"
        process.label="Test Workflow Model"> <!-- Added process.label -->

        <flow
            jcr:primaryType="nt:unstructured"
            sling:resourceType="foundation/components/parsys">
            
            <initiatorparticipant
                jcr:created="{Date}2016-12-14T08:11:19.175-05:00"
                jcr:createdBy="admin"
                jcr:description="Description of step 1"
                jcr:lastModified="{Date}2016-12-14T08:11:45.152-05:00"
                jcr:lastModifiedBy="admin"
                jcr:primaryType="nt:unstructured"
                jcr:title="Step 1"
                sling:resourceType="cq/workflow/components/workflow/initiatorparticipantchooser">
                
                <metaData
                    jcr:primaryType="nt:unstructured"
                    DYNAMIC_PARTICIPANT="/libs/workflow/scripts/initiator-participant-chooser.ecma"
                    PROCESS_AUTO_ADVANCE="true"/>
            </initiatorparticipant>
        </flow>
    </jcr:content>
</jcr:root>

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 narendiran_ravi

Hi @nandango1 ,

You need to include the workflow runtime model under var too in your code repo and deploy that along with the model created under the model. Refer -https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/extending-aem/extending-workflows/workflows-models#sync-your-workflow-generate-a-runtime-model

narendiran_raviAccepted solution

Level 6

Hi @nandango1 ,

You need to include the workflow runtime model under var too in your code repo and deploy that along with the model created under the model. Refer -https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/extending-aem/extending-workflows/workflows-models#sync-your-workflow-generate-a-runtime-model

N

NandanGo1Author

Level 2

Hi @narendiran_ravi thanks for the reply.

Earlier I kept the workflow under /etc but not under /var, it was working fine. Is it necessary to include the workflow too?