[MAGNOLIA-2985] Activation with Workflow mappings fails to chose the right activation command Created: 31/Dec/09  Updated: 01/Jun/11  Resolved: 01/Jun/11

Status: Closed
Project: Magnolia
Component/s: activation, workflow
Affects Version/s: 4.2.1, 4.2.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Françoise Gérard Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File screenshot-1.jpg     JPEG File screenshot-2.jpg     JPEG File screenshot-3.jpg    
Issue Links:
Cloners
duplicate
is duplicated by MAGNOLIA-3588 Workflow mappings: work just once, ne... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Hi again,

I would like my workflow "activation2" to be started on website folder /poc-hm
I adapted the configuration (as read on the wiki if i remember correctly), see the attached screenshot

But still the workflow "activation" is started.
What did I miss?

Françoise



 Comments   
Comment by Françoise Gérard [ 31/Dec/09 ]

If also affects 4.2.3 (I did the update in the meantime)

Comment by Teresa Miyar [ 31/Dec/09 ]

What happens is when you define a mapping with a path and a new command for the activation workflow, when you try to activate the whole tree including subtrees the new defined activation command is used, but is you select to activate children from that node, in some cases uses the mapping activation command and in some cases uses the default one.
When testing this issue with Magnolia 4.2.3, first child was activated using the regular workflow and the children below were activated using the workflow defined in the mapping.
When activating the parent and all subnodes, it did use the workflow in mapping. This issue was reported using Magnolia 4.2.1 and the wrong behavior is different. See Support-468

Comment by Ondrej Chytil [ 01/Jun/11 ]

Resolved with MAGNOLIA-3588.

Generated at Mon Feb 12 03:42:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.