Enable selection of workflow associated with an article

[robbiejackson]

Current Problem

When an article is created there is currently a workflow assigned automatically, which is the workflow associated with the category of the article.

However, in many cases the category will be related to the subject matter of the article, whereas the workflow is likely to be related more to the complexity or importance of the article. So there is often not a good correlation between the article category and the workflow which should be applied.

Proposed Solution

This feature request is to enable a user with the requisite authority to be able to select a workflow to be applied to the article. This would apply when the article is initially created (ie New operation) and also whenever the article is already created (Edit operation), to allow correction of a workflow initially assigned wrongly.

Suggested Design

It may be that this requirement could be satisfied by adding an additional permission "core.edit.workflow" within the com_content / category / article asset hierarchy, but this would need to be checked and confirmed.

[HLeithner]

This feature request is to enable a user with the requisite authority to be able to select a workflow to be applied to the article. This would apply when the article is initially created (ie New operation) and also whenever the article is already created (Edit operation), to allow correction of a workflow initially assigned wrongly.

Using the category to define a workflow is much more flexible in combination with permissions as any other way. I understand your concerns to set the workflow your self and maybe the "core.edit.workflow" permission is a way to go. This really depends on the hierarchy of the company/website users.

Maybe something that could be addressed later in J4.1.

[robbiejackson]

I'm not suggesting that the definition of the workflow based on the category is dropped. I'm just suggesting that someone with enough authority should be able to override that.

[HLeithner]

Yes makes sense. Better then "super user" only, like it's now.

[wilsonge]

I think this makes sense - but don't we already have the ability to change the workflow in batch at the moment without the extra permission?

[HLeithner]

I think this makes sense - but don't we already have the ability to change the workflow in batch at the moment without the extra permission?

Only as super user