IMHO - the transfer with ownership is not implemented very well - and causes bunches of issues. And I'm not completely sure that with your setup - you could succesfully use the ownership feature.
What I'd suggest is putting a field on the form "Owner_Server" (or something that makes sense) - and then do a "Send Copy" to ALL servers. Have workflow that checks the Owner_Server field to the server name - and then lock the ticket down for update. You can additionally control other workflow - like SLA, etc using the field as well... At my prior company we had 3 global servers (EU, AP, NA) and implemented the DSO Copy & ticket ownership via the Owner_Server field and it worked like a champ. HTH Robert Molenda On Wed, Jul 8, 2009 at 4:55 AM, Bala Patel <[email protected]> wrote: > ** Hello List, > > I am setting up DSO to distribute between 4 servers. The requirement is to > pass ownership between servers. Can anyone recommend the best method for > setting up the chained transfers? Is it better to actually set up a chain > which can potentially cause looping issues or is it better to send copies to > remote servers and send Ownership to the selected server. For example, If I > want to send a copy to all servers and send ownership to server 4, then > which would be a better recommended way to perform this? > > Also what is the best way to keep track of the servers? If I have a field > that sends it to server 4, then how do you typically keep track of each > server? > > > > Server 1 ------> Server 2 ---------> Server 3 -------------> Server 4 > > > Server 1 ---> Server2 (Copy) > Server 1 ---> Server3 (Copy) > Server 1 ----> Server4 (Ownership) > > Thanks in advance for help, > > Bala > Remedy Administrator > > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
