PHPackages                             studio1/workflow-extend - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. studio1/workflow-extend

ActivePimcore-bundle[Utility & Helpers](/categories/utility)

studio1/workflow-extend
=======================

This bundles extends Pimcore's workflow engine and workflow designer with additional features.

v2.0.0(2y ago)230[1 issues](https://github.com/studio1gmbh/pimcore-workflow-extend/issues)GPL-3.0-or-laterJavaScriptPHP ^8.2CI failing

Since Mar 21Pushed 2y ago2 watchersCompare

[ Source](https://github.com/studio1gmbh/pimcore-workflow-extend)[ Packagist](https://packagist.org/packages/studio1/workflow-extend)[ Docs](https://github.com/studio1gmbh/pimcore-workflow-extend)[ RSS](/packages/studio1-workflow-extend/feed)WikiDiscussions pimcore-11 Synced 1mo ago

READMEChangelog (4)Dependencies (4)Versions (7)Used By (0)

Studio1® Pimcore Workflow Extend Bundle
=======================================

[](#studio1-pimcore-workflow-extend-bundle)

This bundles extends Pimcore's workflow engine and workflow designer with additional features.

It adds the possibility to change data during the workflow transition. It also adds a readonly field to place editor of the Pimcore workflow designer to display the state id.

> **Warning:** This bundle is completely untested with the Pimcore community edition and will probably not work. Further work is needed to make it work with the community edition.

Dependencies
------------

[](#dependencies)

Will be automatically installed with composer:

- [Pimcore Enterprise Asset Metadata Bundle](https://pimcore.com/docs/asset-metadata/current/)
- [Pimcore Workflow Designer](https://pimcore.com/docs/workflow-designer/current/)
- [Composer Patches](https://github.com/cweagans/composer-patches)

Installation
------------

[](#installation)

### Preparation

[](#preparation)

Before you require the bundle via composer, you need to add the following to your composer.json:

```
  "extra": {
    "enable-patching": true
  }
```

This will enable the composer patches plugin, for external dependencies.

### Composer

[](#composer)

```
composer require studio1/workflow-extend:[version]
```

During the installation process, the composer patches plugin will automatically apply the needed patches to the pimcore core files.

Please check if the patches were applied correctly. If not, you need to remove the vendor folder and run `composer install` again.

### Enable Bundle

[](#enable-bundle)

Enable the bundle as with any other Pimcore bundle, add it `bundle.php`.

### Uninstall

[](#uninstall)

```
composer remove studio1/workflow-extend
```

> Please note that the composer patches plugin will not remove the patches automatically. You need to remove them manually.

Usage / Configuration
---------------------

[](#usage--configuration)

> **Warning:** The bundle currently supports data objects and assets only (no documents etc.).

ConfigurationExplanationclassMAM- or PIM ClassattributeAttribute that will be changed during the transitionvalueValue that will be set on the given object/attributelanguagesLanguages for which the value should be set. Comma separated e.g. (de,de\_DE,en,en\_US). Not needed, if localized fields are not available or `languagesSetAll` is set.languagesSetAllThe value will be applied for all available languagesFor Pimcore Enterprise Projects, you can configure the workflow transitions in the backend:

[![Backend Configuration](docs/backend_configuration.png)](docs/backend_configuration.png)

In Pimcore Community Edition, you need to populate the `data` option (implemented by this bundle) in your workflow configuration:

```
  transitions:
    example-transition:
      options:
        label: 'Example transition'
        # ...
        # data that will be changed during the transition
        data:
          class: Basic
          attribute: Title
          value: test
          languages: 'de,de_DE'
          languagesSetAll: true
```

Logs
----

[](#logs)

Can be found in `var/log/workflow-extend-bundle.log`.

Main components
---------------

[](#main-components)

- [transitionSettings.js.patch](patches/transitionSettings.js.patch)
    - Extends the Pimcore Workflow Designer by additional fields for the transition settings popup
- [SetAttributeSubscriber.php](src/EventSubscriber/SetAttributeSubscriber.php)
    - Listens to the `workflow.transition` event and changes the data
- [addDiConfiguration.patch](patches/addDiConfiguration.patch)
    - Adds the `data` option to the workflow configuration
    - A patch file is needed, since there is no other way to extend the dependency injection configuration of the workflow bundle
- [placeSettings.js.patch](patches/placeSettings.js.patch)
    - Extends the Pimcore Workflow Designer by additional field for the state id
    - [![Backend Configuration](docs/place_settings.png)](docs/place_settings.png)

###  Health Score

26

—

LowBetter than 43% of packages

Maintenance10

Infrequent updates — may be unmaintained

Popularity10

Limited adoption so far

Community12

Small or concentrated contributor base

Maturity61

Established project with proven stability

 Bus Factor2

2 contributors hold 50%+ of commits

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~75 days

Total

4

Last Release

919d ago

Major Versions

v1.1.0 → v2.0.02023-09-14

PHP version history (2 changes)v1.0.1PHP ^8.0

v2.0.0PHP ^8.2

### Community

Maintainers

![](https://www.gravatar.com/avatar/0878488b7b834b709a6078d7a4b4122690059decc471aab2c0e9f1b99695a7fc?d=identicon)[studio1gmbh](/maintainers/studio1gmbh)

---

Top Contributors

[![Lars77](https://avatars.githubusercontent.com/u/44695203?v=4)](https://github.com/Lars77 "Lars77 (5 commits)")[![AKriebisch](https://avatars.githubusercontent.com/u/72006118?v=4)](https://github.com/AKriebisch "AKriebisch (4 commits)")[![Alanin](https://avatars.githubusercontent.com/u/1335755?v=4)](https://github.com/Alanin "Alanin (4 commits)")[![isekep](https://avatars.githubusercontent.com/u/30919062?v=4)](https://github.com/isekep "isekep (2 commits)")

---

Tags

pimcore-10pimcore-11pimcore-bundle

### Embed Badge

![Health badge](/badges/studio1-workflow-extend/health.svg)

```
[![Health](https://phpackages.com/badges/studio1-workflow-extend/health.svg)](https://phpackages.com/packages/studio1-workflow-extend)
```

###  Alternatives

[civicrm/civicrm-core

Open source constituent relationship management for non-profits, NGOs and advocacy organizations.

728272.9k17](/packages/civicrm-civicrm-core)[symplify/vendor-patches

Generate vendor patches for packages with single command

1876.7M27](/packages/symplify-vendor-patches)[farmos/farmos

A web-based farm record keeping application.

1.2k6.7k1](/packages/farmos-farmos)[elements/process-manager-bundle

The Process Manager allows you to manage (define,execute...) arbitrary processes/commands in the Pimcore backend.

49633.0k5](/packages/elements-process-manager-bundle)[pimcore/data-importer

Adds a comprehensive import functionality to Pimcore Datahub

44763.4k2](/packages/pimcore-data-importer)[pimcore/object-merger

13550.4k1](/packages/pimcore-object-merger)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)