I don't think command line syntax is the problem here, because when I run command below, I can see the value that I set:aio cloudmanager list-pipeline-variables <pipeline-id>Current output for my pipeline:Name Type Value────────────────────────── ────── ───────CM_CUSTOM_VAR_NODE_VERSION string 16.20...

Developing Sites with the Front-End Pipeline document mentions that it is possible to set NodeJS version to 12 or 16 using pipeline variable CM_CUSTOM_VAR_NODE_VERSION. However, it does not mention which value should be used. I tried setting this variable to 16 and 16.20.0, but neither worked, pipel...

Hi,Yes, OSGI configuration. You can access it using this path: /system/console/configMgr/com.adobe.granite.workflow.core.WorkflowSessionFactory.Superuser property contains a list of users that I described.Hope this helps.

Hi, try checking configuration of Workflow Session Factory. It has been changed since 6.1 (more users/groups were added to the list), and those additional groups need to be present in configuration during upgrade.Hope this helps.Thanks

Although we have not figured out yet how we can handle workflow versions issues I described (for now we are going to just replace version ids in workflow instances with the new ones), other issues are indeed caused by permissions.The problem is that we have a custom configuration for Workflow Sessio...

We are planning an upgrade to 6.3 from 6.1 SP1 and we ran into some issues with workflows after in place upgrade.First:Workflow statuses are not shown in the UI (e.g in damadmin or siteadmin) after the upgrade for pages and assets. Although it seems that all workflow instances are migrated correctly...