[MGNLDEMO-178] Multistep form condition fails due to case sensitivity Created: 17/Aug/16  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia Demo Projects
Component/s: magnolia-travels
Affects Version/s: 0.13
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File next-step-condition.png    
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   

The book-a-tour multistep form in the travel demo fails. It does not direct the visitor to the correct next step. The condition that checks if the visitor has a special meal requirement should skip the meal choice step when the visitor says "No". But we always asks for a meal preference.

To reproduce: book a tour, say "No" to special meal requirements, and click next.

The error happens in the next step condition. Possible values to the meal question are lower-case "yes" or "no" but the condition checks for a mixed-case "No" which never matches.

An easy fix would be to the change the bootstrapped condition value from "No" to "no" in website.travel.xml. But I'm not sure if this ever worked. Did the evaluation of form conditions change from case insensitive to case sensitive at some point? Please verify.



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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