[MGNLWORKFLOW-320] Allow simple workflow changes be done in a simple way Created: 28/Jan/16  Updated: 26/Aug/22

Status: Open
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: 5.5.1
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Marvin Kerkhoff Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
relation
is related to DOCU-670 Document the OOTB workflow Closed
is related to MGNLWORKFLOW-302 Provide Configurable E-Mail based wor... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: AuthorX Support
Team: AuthorX

 Description   

It is a pain to change a workflow for simple things. In our case we want to add a Email Notification for Rejects or Approvements. We end up in a massive Configuration desaster. With 20 Bootstrap files (most of them to change every activation action to our custom action. But also to define a task, workItemHandler etc. We've added 6 Java Classes and 2 JBPM Workflows.
The biggest problem was that all configuration are fined in different locations. Some of them in /modules/workflow and some in /modules/workflow-jbpm.

You provide some tutorials but they all are bringing not a complete overview how the things are done. It would be good to have a complete documentation about how the standard workflow process is working.

I understand that it's more complex if you need a bigger change in the workflow, but it should be possible to add simple things easily. Or to desribe how things working and how we can change this.



 Comments   
Comment by Christian Ringele [ 28/Jan/16 ]

I totally agree with Marvin.

Simple things like:

  • Changing and/or adding groups the workflow is sent to (human task)
  • Adding notification behavior via Mail
  • Adding a second round trip of 2 eyes approval.

Should be doable in a simple manner.
This was achievable in OpenWFE within minutes knowing a bit the OpenWFE xml definitions.

Generated at Mon Feb 12 10:08:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.