[MGNLWORKFLOW-119] As a developer of a workflow I can steer the availability of actions so that I can guide the user Created: 27/Aug/13  Updated: 02/May/14  Resolved: 02/May/14

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

Type: Story Priority: Neutral
Reporter: Espen Jervidalo Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: 3d
Time Spent: Not Specified
Original Estimate: 3d

Issue Links:
duplicate
is duplicated by 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:

 Comments   
Comment by Jan Haderka [ 28/Aug/13 ]

Steer in what way? Isn't whole purpose of workflow to have different actions available at different steps? Isn't this what is described in workflow definition by edges between different workflow steps? What kind of steering are we talking about here?

Comment by Espen Jervidalo [ 28/Aug/13 ]

Exactly, the problem is that with current implementation this is not possible in pulse. So we want to fix that.

Comment by Jan Haderka [ 28/Aug/13 ]

Ah so the button to "approve" is currently hardcoded in pulse instead of read from workflow step?

Comment by Espen Jervidalo [ 28/Aug/13 ]

Not hardcoded, still read from the messageView definition, but I can't toggle the actions using action availability.

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