Setting a read-only HTML field onChange of Requested for is not working on Service Portal

Community Alums
Not applicable

Hello All,

 

There is a read-only HTML field on a catalog form which shows the details related to the requested for user field.

 

For this I have created a script include a catalog client script to set the value onChange of the Requested for field, it was working fine till yesterday in prod (As per the created requested item data shows).

Now for instance it is working fine, however, for the portal it is not working and showing the default value (UI type is set to All).

 

Please help, if anyone has any idea about this.

 

Thanks in advance

Anand

4 REPLIES 4

Amit Verma
Kilo Patron
Kilo Patron

Hi @Community Alums 

 

Any errors being reported in the browser when you set the value of Requested for ? Also, did you checked if the Script Include is being called or not from the client script and the client script is executing or not ?

 

Thanks & Regards

Amit Verma


Please mark this response as correct and helpful if it assisted you with your question.

Jeffrey Siegel
Mega Sage

I think a patch applied in december broke this for us too,  We have a catalog item, where when we fill it out on the Portal, the HTML field used to update and show an image.  now unless the HTML field is editable, the field does not update via a catalog client script, on change behavior.  If we script the field to remove the read only, set the new value, then re-set the read only attribute, it takes it, but it flashes the HTML toolbar on the screen and looks very clunky from a UI standpoint.  I put a ticket in with HI portal, lets see if they have a fix or something for this...

Community Alums
Not applicable

Hello Jeffrey,

 

Please reply to this thread if you get any reply from the HI team, we did the same to fix this issue for now, however, this doesn't look good.

 

They did! there is a workaround until they fix this in Vancouver Patch 8, Washington DC Patch 1 or Xanadu...

check out this kb and it'll provide you with the xml needed to temporarily fix this issue (i attached it here as well),  it worked for us.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1587072

Please mark this response as correct or helpful if it assisted you with your question.