The SOAP interface is Web Services.  Web Services are used to push/get data 
from a server.  They do not interface directly to a user interface  (i.e. You 
can use SOAP to push data to a Remedy server, but that will not pop up anything 
on a user's machine).

You could do some fancy coding (with interval Active Links) to continuously 
check a form for new records and use that method to pop up a client screen.

Fred

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Angus Comber
Sent: Saturday, July 03, 2010 5:29 AM
To: arslist@ARSLIST.ORG
Subject: Re: AR User Tool Deprecated?

Hi Joe

Our thin client integrations do in fact use javascript for integration.

In a nutshell the client programming issues with web are as follows:
1. To access the javascript you need to first latch onto the web browser 
instance which requires custom code for each web browser.
2. WUT has a MDI interface which yes is a proprietary Windows technology but 
you can have powerful control of form instances etc.  This is harder with 
web clients.
2. WUT has more control from Remedy client -> third party client due to the 
fact that there are not the same security restrictions as on a web browser. 
Eg you can't run process with a web client.

We support whichever versions of Remedy clients are likely to be using.

The ideal interface from our point of view would be a interface which we can 
access via the server but which would provide the ability to 'push' to the 
relevant client.  I am thinking the Remedy soap interface may provide this. 
We need to test.  Service Desk Express have something like this with their 
push service.  We also need a way for a user to send a message from web 
client and be able to detect this message - hopefully via soap or some other 
interface.

Does anyone know if the soap interface could provide this?  I have doc, just 
need to get reading.

Angus


----- Original Message ----- 
From: "Joe D'Souza" <jdso...@shyle.net>
Newsgroups: public.remedy.arsystem.general
To: <arslist@ARSLIST.ORG>
Sent: Thursday, June 24, 2010 9:44 PM
Subject: Re: AR User Tool Deprecated?

> Hello Angus,
>
> I would agree with some of your statements a few versions ago when Remedy
> Web was the web application tool. Mid-Tier since then has evolved to a 
> much better product, and sometimes there is a very thin difference between
> the performance gains experienced on the thick client as opposed to the web. 
> In fact in my experience the web client tends to be a lot more faster on 
> remote connections than the native thick client.
>
> Yes you are going to loose and have to give up on client based API
> customizations that use the COM libraries, but many of these can be
> re-engineered or re-written using JavaScript that would work from the web
> client.
>
> I think it would be a good idea for Remedy to focus on continuing to 
> improve the already 'much improved' web client, rather than utilize their 
> resources developing and improving a client that is lesser and lesser used 
> with 
> every passing version. Many of the sites I have recently been to use only the 
> thin client.
>
> Just curious, but what versions do you currently work on?
>
> Joe
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org]on Behalf Of Angus Comber
> Sent: Thursday, June 24, 2010 4:19 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: AR User Tool Deprecated?
>
>
> I believe this is true and think BMC are making a big mistake for the
> following reasons:
>
> 1. The thick client has a client based API, using COM, which is used by 
> many third party products, including our own, and this capability is really
> useful for integration with other products.  All this functionality will 
> be lost.
>
> 2. It is administrators, not users, pushing for web front ends, simply for
> deployment reasons.  Users prefer responsive, rich functionality
> applications.  Anyone who has used Siebel will know what I mean.
>
> I have no problem with a web alternative but if they go for thin client
> only, then that is not good news from my perspective.
>
> Angus
>
> ----- Original Message -----
> From: "NNMN" <naveen...@gmail.com>
> Newsgroups: public.remedy.arsystem.general
> To: <arslist@ARSLIST.ORG>
> Sent: Thursday, June 24, 2010 8:40 AM
> Subject: AR User Tool Deprecated?
>
>
>> Hi ARSers,
>>
>> I have been hearing that AR User tool is getting deprected. I have few
>> questions on this.
>>
>> - Is it really going to get deprecated? Is ARS8.0 going to have a thick
>> client?
>> - If it is just through mid-tier then will the DDE, OLE, macros etc be
>> removed from active link actions.
>> - Is mid-tier expected to come up with more capabilities so as to tackle
>> client dependencies?
>>
>> Not sure who can answer this. But would also be cool to get your own 
>> views on this.
>>
>> Cheers,
>> Naveen
>>
>> -----
>> With Warm Regards,
>> Naveen

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to