[MGNLWORKFLOW-253] Use asynchronous command execution by default Created: 06/Jun/14  Updated: 30/Sep/16  Resolved: 10/Jun/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: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2014-06-06 at 13.14.17.png     PNG File Screen Shot 2014-06-06 at 13.14.57.png    
Issue Links:
relation
is related to MGNLWORKFLOW-244 CLONE - Enable workflow to run activa... Closed
supersession
supersedes MGNLWORKFLOW-146 All workflow steps are executed synch... 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)

 Description   

Currently you can configure the command work item handler to run async, but it's not default. This should be changed. See screenshots


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