On Submit not working in order guides

kannann_
Kilo Expert

Hi All,

I have an order guide which has 4 catalog items associated with it. I have few On Submit catalog client scripts on these catalog items. They don't seem to work when I click checkout.

Please help.

Thanks,

Kannan

1 ACCEPTED SOLUTION

kannann_
Kilo Expert

Hey All,



I got the issue, the system property glide.sc.guide.tab.validate was set to false. I changed it to True and it is working fine now.


View solution in original post

17 REPLIES 17

Your script looks good. I believe "alpha_app_server_count", "alpha_db_server_count", "app_server_count", "db_server_count" these variables are on the order guide and the catalog items you get after you click on choose items. Please confirm.


When you say the script is not working, is it not setting the variable values in the catalog item? Can you try using alert('') to check if the script is being executed?


Yes, the variables are on both order guide and catalog items, have the same names in both places, and variables are set to cascade on the order guide level. I'm not seeing any values being set after the items are ordered (the variables are hidden on the catalog item forms to reduce clutter for the user). I know the cascading variables work because I originally was only using "app_server_count" and "db_server_count" until it was requested that we split these out by environment - previously those variables were answered by the user on the first page of the order guide and the items were correctly receiving the values.



I will test with alert() and get back to you.


I finally figured out what is happening... I had unchecked the "Visible on Guides" options for these questions and that dropped them off of the forms. When they aren't visible on guides, that actually means the system is not adding them to the HTML at all, instead of just adding them and then hiding them. So I checked this box for the two variables I was trying to edit through the script (app_server_count & db_server_count) and then added a UI policy to hide them anyway.