Disabling order now button for the agent

[is_12]

Hello Community !..

When agent is ordering the item from configurable workspace then write a logic as follows. On change of primary contact, fetch the primary contact's account and then go to RITM table and check for the catalog item and the account fetched from primary contact. If there is an existing record then restrict the agent from ordering and also display the alert message "You are not allowed to order as there is an existing request for this customer"

already there is a UC for controlling the visibility for the items for customer.

Thanks,

 

[SumanthDosapati · Accepted solution]

@is_12 

Try below approach.

1. Write an onChange client script on primary contact as below"
   

   function onChange(control, oldValue, newValue, isLoading) {
       if (isLoading || newValue == '') {
           return;
       }
   
       // Call GlideAjax to check existing RITMs
       var ga = new GlideAjax('CheckUserRITMs');
       ga.addParam('sysparm_name', 'hasExistingRITM');
       ga.addParam('sysparm_user_id', newValue);
       ga.addParam('sysparm_catalog_item', g_form.getUniqueValue()); // catalog item sys_id
       ga.getXMLAnswer(function(response) {
           if (response == 'true') {
               g_form.showFieldMsg('primary_contact', 'This user has already requested this item.', 'error'); //check field name
           } else {
               g_form.hideFieldMsg('primary_contact', true); //check field name
           }
       });
   }
   ​

2. Write a New Client callable script include as below
   Name: CheckUserRITMs
   Accessible from: All application scopes
   Client Callable: True
   

   var CheckUserRITMs = Class.create();
   CheckUserRITMs.prototype = Object.extendsObject(AbstractAjaxProcessor, {
       
       hasExistingRITM: function() {
           var userId = this.getParameter('sysparm_user_id');
           var catalogItemId = this.getParameter('sysparm_catalog_item');
   
           if (!userId || !catalogItemId) {
               return 'false';
           }
   
           var ritmGR = new GlideRecord('sc_req_item');
           ritmGR.addQuery('cat_item', catalogItemId);
           ritmGR.addQuery('u_primary_contact', userId); // replace with actual field name if different
           ritmGR.query();
   
           if (ritmGR.hasNext()) {
               return 'true';
           }
   
           return 'false';
       }
   
   });
   

This will show an error message at the field level and also user cannot submit even if they click the order button.

Accept the solution and mark as helpful if it does, to benefit future readers.
Regards,
Sumanth

[is_12]

@Ankur Bawiskar 

one Uc is there to control the visibility on the support portal.

But now I need to control it on the workspace

Thanks,

[Ankur Bawiskar]

@is_12 

that user criteria should work when you open the catalog from workspace also

Did it not work?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[is_12]

@Ankur Bawiskar For the visibility of item to the customer(for this we have a different logic). this is working fine

for agent we have this logic how to implement this

Thanks,

[Ankur Bawiskar]

@is_12 

you can have catalog client script on your variable and use GlideAjax to validate

If already record exist then show error message on that variable and user won't be able to submit the form

what did you start with and where are you stuck?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[shantanu_patel8]

@is_12 

You can write a on change catalog client script on primary contact variable.

In the script you can check if the RITM already exists for the combination. If the RITM exists then you can display an alert or message as per your need and clear the selected Primary contact. This way you wont have to deal with disabling the order now button.

Please mark the answer helpful and correct if it helps the issue. Happy scripting 🙂

-Shantanu