Workflow name and transition mismatch between Pimcore Admin UI and Pimcore Studio UI when using single-state marking store with custom SupportStrategy

[Chauhan-Mukesh]

Context:

While integrating a single-state workflow with a custom support strategy (App\Workflow\WorkflowSupportStrategy), I’ve observed that the same workflow functions correctly in the Pimcore Admin UI, but fails when triggered through the Pimcore Studio UI.

---

Observed Error:

When trying to execute a transition (for example: move_to_reviewing) via Studio, the following error occurs:

Submitting action move_to_reviewing failed: Unable to find a workflow for class "Pimcore\Model\DataObject\ClassName"

---

Root Cause Analysis:

Tracing through submitAction() in the Studio backend:

$workflow = $this->workflowRegistry->get(
    $element,
    $parameters->getWorkflowName()
);

Here, $parameters->getWorkflowName() returns generic_workflow, while in configuration the workflow is defined as genericWorkflow.

Pimcore Admin internally references workflow names exactly as defined in the YAML configuration.
However, Pimcore Studio appears to normalize workflow names (likely converting camelCase to snake_case), leading to a mismatch.

Workflow Config (excerpt):

pimcore:
    workflows:
        genericWorkflow:
            enabled: true
            priority: 1
            label: 'genericWorkflow'
            type: workflow
            initial_markings: working
            audit_trail:
                enabled: true
            marking_store:
                type: single_state
                arguments:
                    - workflowStatus
            support_strategy:
                service: App\Workflow\WorkflowSupportStrategy

The submitAction() then throws WorkflowActionSubmissionException because $workflowRegistry->get() can’t locate the workflow under the normalized name.

---

Additional Finding:

If I manually rename the workflow in YAML to match (generic_workflow), the next issue appears during marking validation —
the Studio expects the transition name as move_to_reviewing, while the workflow defines it as working_to_reviewing.

Example config:

            places:
                working:
                    label: Working
                    title: Working
                    color: '#4b70c5'
                    visibleInHeader: true
                    permissions:
                        - condition: >
                            is_fully_authenticated() and 
                            ('ROLE_PIMCORE_ADMIN' in role_names or 
                            'ROLE_MASTER_DATA_CREATOR' in role_names or 
                            'ROLE_PRODUCT_VARIANT_CREATOR' in role_names)
                          publish: false
                          unpublish: false
                          save: true
                          delete: true
                          rename: true
                reviewing:
                    label: Reviewing
                    title: Reviewing
                    color: '#9217ca'
                    visibleInHeader: true
                    permissions:
                        - condition: >
                            is_fully_authenticated() and 
                            ('ROLE_PIMCORE_ADMIN' in role_names or 
                            'ROLE_MASTER_DATA_CREATOR' in role_names or 
                            'ROLE_PRODUCT_VARIANT_CREATOR' in role_names)
                          publish: false
                          unpublish: false
                          save: false
                          delete: false
                          rename: false
            places:
                working:
                    label: Working
                    title: Working
                    color: '#4b70c5'
                    visibleInHeader: true
                    permissions:
                        - condition: >
                            is_fully_authenticated() and 
                            ('ROLE_PIMCORE_ADMIN' in role_names or 
                            'ROLE_MASTER_DATA_CREATOR' in role_names or 
                            'ROLE_PRODUCT_VARIANT_CREATOR' in role_names)
                          publish: false
                          unpublish: false
                          save: true
                          delete: true
                          rename: true
                reviewing:
                    label: Reviewing
                    title: Reviewing
                    color: '#9217ca'
                    visibleInHeader: true
                    permissions:
                        - condition: >
                            is_fully_authenticated() and 
                            ('ROLE_PIMCORE_ADMIN' in role_names or 
                            'ROLE_MASTER_DATA_CREATOR' in role_names or 
                            'ROLE_PRODUCT_VARIANT_CREATOR' in role_names)
                          publish: false
                          unpublish: false
                          save: false
                          delete: false
                          rename: false

Excerpt from validation path:

if (!$workflow->can($element, $transitionName)) {
    throw new WorkflowActionNotAllowedException(
        $transitionName,
        $parameters->getWorkflowName()
    );
}

This shows Studio is passing the action name instead of the transition name as defined in the workflow definition.

---

Conclusion:

• Admin UI: Works correctly because it uses workflow name and transition identifiers exactly as defined.
• Studio UI: Fails due to:
  1. Converting workflow name from genericWorkflow → generic_workflow.
  2. Sending action name (move_to_reviewing) instead of transition name (working_to_reviewing) when invoking the backend.

---

Impact:

This causes all workflow transitions to fail in Studio UI for objects using custom support strategies and single-state marking stores.

--

Expected Behavior:

Studio UI should preserve exact workflow name and transition identifiers as defined in the YAML configuration, matching Admin UI behavior.

Environment:

• Pimcore 2025.2
• Pimcore Studio Bundle (latest)
• Symfony 7.x
• Workflow: single_state marking store
• Custom SupportStrategy: App\Workflow\WorkflowSupportStrategy

---

Could you please confirm if this is an actual issue in the Studio Bundle? If yes, is there any planned fix or known timeline for resolution?

In the meantime, is there any workaround or configuration adjustment I can apply on my side to align workflow name and transition handling between Studio UI and the Admin UI?

[markus-moser]

I checked it, yes this is a bug in studio-ui. Will fix it very soon: #2467

[Chauhan-Mukesh]

HI @markus-moser I have seen this issue is resolved and merged, how can I test it, is it available in 2025.2 studio UI or in 2025.3, I am currently on 2025.2 on my local, and it was a blocker for me.

[harshida-patel]

I am facing same issue please suggest which version has resolved this issue.

[markus-moser]

@Chauhan-Mukesh @harshida-patel Currently we only have this in the 1.x branch, so you would need to install the 1.x branch or concrete commit hash to test it. We will do a new release with this change included soon but currently don't have an exact ETA which I can provide.