Hi. If the workflow actions are not rendered into the CMS (e.g. WorkflowApplicable extension fails permission check line ~186) then the advancedworkflow.js script fails trying to process a click event because fields it is trying to do a replace on non-existant attribute 'name' value , see advanced-workflow-cms.js:~12. Should be some defensive coding in there to check that the field/attribute exists.
This is an issue in CWP as we can't seem to disable the AdvancedWorkflows module as part of the recipe.
Hi. If the workflow actions are not rendered into the CMS (e.g. WorkflowApplicable extension fails permission check line ~186) then the advancedworkflow.js script fails trying to process a click event because fields it is trying to do a replace on non-existant attribute 'name' value , see advanced-workflow-cms.js:~12. Should be some defensive coding in there to check that the field/attribute exists.
This is an issue in CWP as we can't seem to disable the AdvancedWorkflows module as part of the recipe.
Cheers, Steve