GlideAjax.getXmlWait()Not working on Portal

[cg_snow]

Hi,

I have used getXmlWait() {without Callback} on a multiple occasions to Validate my form before submission.

I intentionally wanted to make it synchronous.

Now this signature doesnt work on portal (mobile). Any work arounds?

[Chuck Tomasi]

Service Portal does not support synchronous GlideAjax. I recommend you take a look at using the client controller to do an HTTP call using one of the REST APIs or scripted REST API.

I believe we covered this one one or more of the TechNow episodes on Service Portal, Scripted REST APIs, or even the CreateCon 17 Part 2.

TechNow Episode List

[cg_snow]

Chuck,

Thanks for the reply. I watched your videos. But my case is a little different.

Our system is legacy and our service management is written for CMS prior to Istanbul.

Your solution is suited for a fresh portal development using the angular $http ( success and failure ) approach.

We cannot possibly convert all our existing codes to portal compatible structure.

What about the existing code isnt there a way to make it work in Portal?

or is it the end of the road and we need to ask the client to re design ALL their Catalog Items ( service management ) if they want to go ahead with Portal and Mobile?

[Chuck Tomasi · Accepted solution]

HI Debarata,

I wasn't aware that you were using CMS. CMS isn't natively mobile friendly whereas Service Portal is.

This goes beyond a simple "how do I fix this technical issue". It sounds like a mobile strategy is in order and the technical issues like synchronous calls in client scripts needs to be addressed as part of that strategy.

[cg_snow]

Chuck,

very true. But like all tech teams we guys were not part of the strategic decision phase !

I am stuck only with this OnSubmit synchronous call issue. we have planned manual fixes for all other instances on incompatible codes ( GlideRecord.query(), GetReference() ) with proper call back implementations.

But I am stuck with this. cant think of any possible fix !

I can delete the generated RITM post a submit but that way the user will be even more confused. Cant go ahead with that .

Anything ?