Catalog items slow for some and fast for others

[AbooK]

Hey,

I got some issues as in regards to a client I am working for. On the self service portal,

we are experiencing that for some none-itil licensed users the catalog items they are opening in the portal can take up to several seconds to open (15 - 20 seconds), and for licensed users such as myself the catalog item immediately opens.

This only apply to certain catalog items, and I cant really see any difference on them when i try to compare them to others that opens faster.

Does anyone know what the reason for this might be?

[RodGallegos]

Do you have any screenshots of the Catalog Item forms from the portal? Do you know if any of them are using catalog client scripts, custom security, or a custom widget? There could be reasons hidden in the implementation of these components. If the catalog client script is making multiple calls to the server to retrieve a logged in employee's user data and then prepopulate fields on the form, that might explain why it loads slowly for the employee. The form may not load slowly for you because perhaps your user profile doesn't contain the quantity of data that a FT employee's user profile might contain. If there is custom security, the same explanation could be slightly altered. If you have Admin privileges, then you get a green light to pass up most security that is provided OOTB and possibly even custom security. If a standard user logs in to view the same form, there are security checks that are occurring in the background that slow down the client (browser). If this is a custom widget, then the issue might be in the code somewhere. Hope this sets you in the right direction for an answer!

[AbooK]

On this spesific catalog item. There is only 1 simple catalog client script. There is no custom widget here. And where do I check for custom security?

Is there also a way to check these security checks that is occuring in the background that might slow down the client (browser)?

As I can see on this specific catalog item its very simple and straight forward, without much customization.  

[RodGallegos]

What is in the catalog client script?

Custom security might be in the "Available for" or "Not available for" which leverages the User criteria records. 

One way to check for additional security is to turn on "Debug security". Though you might be looking for a needle in a haystack.

If you can reproduce this in your PDI, then opening a HI ticket with ServiceNow is your best bet. 

[AbooK]

Its an onChange Catalog Client Script.

The code in the script is:

function onChange(control, oldValue, newValue, isLoading) {

   if (isLoading ) {

      return;

   }

   if (newValue == ''){

   g_form.setValue('system_number', '');

   }

   else{

   g_form.setValue('system_number', newValue);

   }//

}

Both "Available for" and "Not available for" is empty.