I using FUJI and have read through all the postings. While Junior’s post was very helpful it appears to be missing something. I can get the checkMandatorySubmit to fire and receive the message “‘The following mandatory fields are not filled in: ” .. but the request is still being submitted.

Any solutions for this

Junior,

Thanks for the info you’ve posted. However, there is still some piece missing in your post. You did not mention which part of the sc_cart_view_buttons macro has to be edited and how the UI script can be called from it. I’m also working over Fuji version and finding it difficult to edit the xml.

Thanks!

Junior

I found our reply to “Mandatory Fields on Service Catalog Checkout Form” about getting this to work in FUJI. I would like to use it but you seemed to have omitted something I need. You stated

” So, open this macro, find the line for the checkout button:

Change it to this:

Notice the change in the onClick property. We are calling a function, and if that function returns true, then we perform the checkout method.”

Can you please provide the rest of the what “Change it to this:” actually is?

Junior

I found our reply to “Mandatory Fields on Service Catalog Checkout Form” about getting this to work in FUJI. I would like to use it but you seemed to have omitted something I need. You stated

” So, open this macro, find the line for the checkout button:

Change it to this:

Notice the change in the onClick property. We are calling a function, and if that function returns true, then we perform the checkout method.”

Can you please provide the rest of the what “Change it to this:” actually is?

First step, navigate to cart layouts and find the proper screen. I’m using the two-step, so I go to Maintain Cart Layouts -> Browser Screen -> Cart Preivew Screen (Two Step). This is the cart screen, and it’s made up of UI Macros which compose each section. Now, you don’t want to (and you cannot) update these UI Macros, or you own them. The great thing they’ve done with Fuji is make it easier to update the cart without invalidating upgrade paths, we just have to figure out the rest now. So, take the ui macro sc_cart_view_buttons at order 800. This is the footer buttons, one of which is checkout. Create a new UI Macro, and copy the XML from the sc_cart_view_buttons ui macro over to the new macro (I called my sc_cart_view_buttons_new). Now, go back to the cart screen, select Edit, and remove the sc_cart_view_buttons, then add the sc_cart_view_buttons_new ui macro. Now, make sure you set it to order 800 or 900 or whatever to have it last. Now you can edit this macro (make sure you didn’t just do insert and stay on the OOTB one or it will be protected and read only as well). So, open this macro, find the line for the checkout button:

Change it to this:

Notice the change in the onClick property. We are calling a function, and if that function returns true, then we perform the checkout method.

Now, we have to capture that new function, so go to System UI -> UI Scripts, create a new UI Script. I called mine, much like Mark did above, checkMandatorySubmit. Here, you will actually check to see if the fields you want are populated. I am checking the special_instructions as well as a custom field I’ve added called sc_cart.approver. Make sure to tick the Global checkbox, and below is the code you will need:


function checkMandatorySubmit(parm1, parm2){
//g_form.getValue('sc_cart.approver'),g_form.getValue('special_instructions')
//alert("Here");
var manFields = '';
var si = gel('sc_cart.approver');
//alert("parm1.value is: " + si.value);
if(si.value == ''){
manFields = 'Approver';
}

}


Now, that UI Script uses GlideAjax to call a script include. You will need to create this as well. Below is the information on the script include:
Name: cartAjaxProcessor_Custom
Client Callable: Make sure you check this
Script:
var cartAjaxProcessor_Custom = Class.create();

cartAjaxProcessor_Custom.prototype = Object.extendsObject(AbstractAjaxProcessor, {

updateApprover: function(){
var approver = this.getParameter(‘sysparm_value’);
gs.log(“Approver is: ” + approver);

var cart = new GlideRecord(‘sc_cart’);
cart.addQuery(‘user’, gs.getUserID());
cart.addQuery(‘active’, ‘true’);
cart.orderBy(‘sys_created_on’);
cart.query();

if(cart.next()) {
cart.u_approver = approver;
cart.update();
}
}
});

This script include updates the cart so that the cart will grab the new values. For the custom approver field I added, I had to add a field to the cart to hold this. Now that the cart is updated, we need to get this data over to the request. So, on the request, you create a new business rule to pull the data in from the cart. Below is the information on that Business Rule:
Name: Set Approver from Cart
Table: Request [sc_request]
Insert: True
When: before
Script:
function onBefore(current, previous) {
//This function will be automatically called when this rule is processed.
var user = gs.getUserID();
gs.addInfoMessage(“user is: ” + user);
var gr = new GlideRecord(‘sc_cart’);
gr.addQuery(‘user’, user);
gr.addQuery(‘active’, ‘true’);
gr.orderBy(‘sys_created_on’);
gr.query();

if(gr.next()) {
gs.addInfoMessage(“approver is: ” + gr.u_approver);
current.u_approver = gr.u_approver;
} else {
gs.addInfoMessage(“couldn’t find cart”);
}
}

This should just about do it. I hope this helps you all out, as I know that I spent a very long time figuring this all out.

I think your issue here is that the code has further changed with fuji. Now the onlick is this: “onclick=”checkout(this, forms[‘sc_cart.do’]);””
I’m not sure exactly what all is being done, but it definitely deviates further from what Mr. Stanger had. I am trying to figure this out myself right now, hopefully will find a solution shortly.

Mark, works a treat. Thanks

Looks like SN changed a few things in Eureka. You should be able to fix this by creating a global UI script. I’ve modified the instructions above to reflect this workaround.