Order Guide Check Out button

[mamann]

I've set up an Order Guide with 5 possible choices that will spawn the associated Catalog Items (Two Step checkout is active)

I've noticed an issue related to the Check Out Button not changing color to Orange under specific circumstances

Example. I choose Item(s) 1 and 3

Item 1 has 10 fields and one of them is a Yes/No field, if Yes is selected a Client Script is fired to show 5 more fields which are mandatory, if No or -None- is selected, the fields stay hidden and are not mandatory.
For test case, I will keep the value at No and ensure all other fields are populated on Item 1
The order guide now allows me to click the tab for Item 3

Item 3 has all fields shown and will be filled out; however I cannot choose Check Out.

Item 1 shows the * in the tab indicating it is missing populated fields, however if I switch back to tab 1, I can choose checkout from there.

I assume this is happening because I'm hiding the fields via Client Script (haven't tried UI policy yet) and when I switch tabs the client script does nothing because Item 1 is no longer the focused form. I do find it a bit odd that even if I switch focus back to Item 1, the * still appears in the tab next to Item 1's name even though the Client Script should now be active and will allow me to use Check Out from that tab.

Just curious if anyone else has noticed this before.
A possible workaround would be to use a UI Policy or just move Item 1 to be last in the tab selection since it is the only form that has hidden fields.

I'll test the UI Policy option and update this.

Thanks

[mamann]

So I switched out the Client Script for a UI Policy on the fields and still have the same issue

Has anyone run into this or am I missing something? 🙂

[jfarrer]

We have run into something like this that had to do with the order of operations. Depending on how we set up the logic and then how we ordered the script statements it would behave similar to what you described.

The issue we ran into had a couple of causes depending on how we were hiding and showing and setting it mandatory.

When we were using UI Policies we were running into issues of the order not being applied consistently across variable sets and catalog items. To fix this we moved the functionality to client script that gave us more control.

With Client Scripts we ran into this when we were trying to change the mandatory and display settings in the wrong order. If I remember right you can only set the Mandatory flag when the field is showing.

I'm not sure if you're having the same issue, but it sounded similar enough that it might be. Good luck!

[mamann · Accepted solution]

The issue seems to be stemmed from the variable having the Mandatory flagged checked
Once I removed this and let the UI Policy control Mandatory the issue was fixed