[MGNLWORKFLOW-225] Introduce Human Tasks Created: 17/Apr/14  Updated: 02/May/14  Resolved: 28/Apr/14

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4

Type: Improvement Priority: Neutral
Reporter: Espen Jervidalo Assignee: Espen Jervidalo
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
supersedes MGNLWORKFLOW-127 As a user I get notified in Pulse abo... 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:

 Description   

We allow adding Human Tasks to a process which will be delegated to the newly created task management module.



 Comments   
Comment by Richard Unger [ 17/Apr/14 ]

yes yes yes! awesome!

Comment by Richard Unger [ 17/Apr/14 ]

perhaps also consider the use cases:

human task needs to be executed on front-end but workflow is on author instance and vice versa

Comment by Espen Jervidalo [ 22/Apr/14 ]

That's indeed an interesting use case. While we won't be able to deliver this out of the box for 5.4, it should be fairly straight forward to implement this using the REST API. Instead of creating local tasks inside the process on author, you would call the REST API on public instance to create a user task in pulse, then make sure you call back to the process on author to proceed the process, when the task on public is completed.

Thanks for the feedback!

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