I'm using the jQuery Validation plugin and jQuery Steps to re-create a form wizard that was very straightforward in BC.
Specifically, I need to figure out how to get Siteglide's standard javascript submission process... (triggered by the submit button below)
<button type="button" class="btn buttonAccent" onclick="s_form_submit_v2(this,'form_X')">Submit</button>...to properly execute within the Validation plugin's submitHandler callback function following validation.
I migrated this site from BC. Implementing this in BC was easy because it simply fired the form's action. However, because Siteglide's form action of "/api/customizations" (??) appears to be dependent on the system-generated submit button's onclick function firing, I need to better understand what's going on behind the scenes with the form submission process in order to concoct a working callback function.
Currently this is the primary thing keeping me from launching this migrated site onto Siteglide. So, any assistance or insight into the standard form validation/submission process would be much appreciated.
Hi Bruce it sounds like your in the final stages of migrating a site. let me see if I can get some more attention to your post I'm sure we'll find a solution for you.
Hi Bruce,
I'm not so familiar with the jQuery validation. Is it possible to simply run the function s_form_submit_v2(this,'form_X') after the validation succeeds, instead of trying to submit data to the form "action"?
You'd then remove our function from the "onclick" function and put your own validation function to run instead, knowing that our function would run later, after validation success.
A good way of getting a summary of what the function does behind the scenes is to record the requests in the network tab when you submit a Form. The real answer is, "it depends" based on what kind of Form it is e.g. a Secure Zone Form will make a request which logs the User into a Secure Zone. This functionality will be lost if you just submit data to the form "action", which would only succeed in saving data in the "case" in the database.
Hi Matt,
That is exactly what I had done but because there are multiple ways to accomplish this using these two plugins, I think I confused myself a bit putting it all back together, post migration. (I'm still learning) :-)
Anyway, I've now managed to get it to submit a form properly. Thanks for your response.
Oh perfect! Glad I could help!