Skip to main content

Cookie settings

We use cookies to ensure the basic functionalities of the website and to enhance your online experience. You can choose for each category to opt-in/out whenever you want.



Analytics and statistics


This proposal has been implemented

  • Reviewed by @product and accepted in the main project
  • Developed by Codi Tramuntana
  • Available in release 0.28 via #9026

Possibility to automatically activate process steps

Avatar: AH

This issue originates from a GitHub issue 2 years back. In that issue you will find the proposed technical details which are left out from this. The issue has been modified with updated context information.

**Is your feature request related to a problem? Please describe.**

Many people don't want to wake up at midnight to manually change the step when the process phase ends. This could be avoided if the step changes could be scheduled.

**Describe the solution you'd like**

It should be possible to make schedule the steps to be activated automatically.

In the process step settings, the user could control with a checkbox if the step should be automatically scheduled to be activated at a given time. The activation time should be another configuration option that is apart from the step start and end dates. In the activation time, the user should also configure the time of the day when the activation happens with the timezone set for the Decidim instance.

The automated activation should be optional per step.

**Describe alternatives you've considered**

Custom cronjobs that run an SQL query at the given time but this would have to be configured each and every time specifically to the case. Does not sound very appealing or cost efficient.

**Additional context**

There can be conflict situations if multiple steps of the same process have been configured to be activated at different times. The last step in order should always "win" if multiple steps are configured to be activated at the exact same time.

In the original GitHub issue the suggested technical solution was ActiveJob+whenever. This should be designed so that it would be configurable on all platforms. It was mentioned that e.g. Heroku does not provide cron and therefore whenever would not work there.

**Does this issue could impact on users private data?**


**Funded by**

Currently no one has provided the funds to implement this but everyone constantly requests this feature.



Please log in

The password is too short.