Re: Mid Tier Web Services

[Rocky Rockwell]

What we have done is create a custom web page outside of remedy that is 
the default for remedy. There we have links that depending on what they 
click on with either prompt for a login or just take them to the remedy 
page by automatically logging them into the system. For us we have setup 
normal end-user submit to be able to submit w/o having to login. We set 
the submitter field to the whatever the ID is for the customer that they 
enter. That way they can modify a few fields we allow them to modify if 
they want. To modify they have to login and a control panel comes up to 
let has buttons for them to go to the application they want and we allow 
them to modify.  For Analyst they login always and we take them to a 
slightly different control panel so they can do there work (these people 
have write licenses). That way we control what people can do based on 
permissions.


Hope this helps.

*Rocky*

Rocky Rockwell
eMA Team – Remedy Developer
[EMAIL PROTECTED] 
Ph#1: 214-567-8874
Ph#2: 325-884-1263



Koyb P. Liabt wrote:

**
We designed a custom web page #1 with a URL that opens
web page #2.
 
On Web page #2 there is another URL that opens the

remedy login. When the user logins in to remedy and a custom web
page opens that our end-users want to modify.  This custom web page is 
the not the Remedy
OOB home page, and has some workflow that does not work well. We have 
been tasked

with fixing this workflow.
 
Is it better to use web services to customize, reduce the logins and 
direct the user to the OOB Remedy home page (with links for 
Change/Incident, etc) or would it faster (less effort)t to scrap 
a customized web page and go back to the original OOB Remedy Home page?
 
 





See AOL's top rated recipes 
 and 
easy ways to stay in shape 
 
for winter.
__20060125___This posting was submitted with HTML 
in it___ 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Mid Tier Web Services

[Koyb P. Liabt]

We designed a custom web page #1 with a URL that opens
web page  #2.
 
On Web page #2 there is another URL that opens the
remedy login. When  the user logins in to remedy and a custom web
page opens that our end-users  want to modify.  This custom web page is the 
not the Remedy
OOB  home page, and has some workflow that does not work well. We have been  
tasked
with fixing this workflow.
 
Is it better to use web services to customize, reduce the logins and direct  
the user to the OOB Remedy home page (with links for Change/Incident, etc) or  
would it faster (less effort)t to scrap a customized web page and  go back to 
the original OOB Remedy Home page?
 
 



**See AOL's top rated recipes 
(http://food.aol.com/top-rated-recipes?NCID=aoltop000304)

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Mid Tier Web Services

[Kathy Morris]

We designed a custom web page #1 with a URL that opens
web page #2.



On Web page #2 there is another URL that opens the
remedy login.



When the user logins in to remedy – a custom web
page opens that our end-users



want to modify.  This web page is the not the Remedy
OOB home page, and has some



workflow that does not work well.  We have been tasked
with fixing this workflow.



 



My question – which would be easier and the
level of effort to point the URL from web page #1 to the original OOB
functionality,



or fix the issues thru web services?



 


Please advise.

More new features than ever.  Check out the new AOL Mail ! - 
http://webmail.aol.com

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"