**

… not changing the group names as there is no way I know of that you can stop the recaching.

 

What I was getting at is that it’s not a workflow issue.

 

I’m not sure if the recache time is different depending on the group type, you could experiment with that.

 

Otherwise you’ll need to have an alternative way of presenting the group telehone number.

 

What about displaying the long group name instead of the group name and changing this as the phone number changes? This probably doesn’t cause a recache.

 


From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Carter, Craig J Civ ARPC/DPD
Sent: 08 November 2006 18:40
To: [email protected]
Subject: Re: Question: Group Name / Employee Name Change in CSS Time Out

 

…and the fix / work-around is?

 

//SIGNED//

CRAIG J. CARTER


From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Peter Romain
Sent: Wednesday, November 08, 2006 11:17 AM
To: [email protected]
Subject: Re: Question: Group Name / Employee Name Change in CSS Time Out

 

I think you’ll find that this is a server caching issue.

 

Changes to groups cause the server to recache and it’s this that’s causing the timeouts.

 


From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Carter, Craig J Civ ARPC/DPD
Sent: 08 November 2006 16:18
To: [email protected]
Subject: Question: Group Name / Employee Name Change in CSS Time Out

 

ARS 6.3 P16

CSS 5.0.1

SQL Server 2000

 

Has anyone had experience updating group names when there are a lot of assigned issues against those groups?  When set up, our group names included the phone number suffix to make it easy for the agent to contact that group as needed and when transferring issues.  Because phone numbers change, these group names need to be updated occasionally.  We’re now receiving time-out messages from the server when we try to update some of the names.  Although you get a message stating the change was accepted by the server and will generally succeed, it never does.

 

For example, I have a group with 149 assigned issues.  I can’t update the name through the customer support admin interface without it timing out.  A name change for a group with less than 100 issues generally succeeds.   I’ve tried changing time-out limits in various places with no success.  Short of reassigning all of these issues to another group, updating the name, and reassigning them all back, does anyone have a work-around or know where the time-out limit for this process exists?  My assumption is workflow is going through all of these issues to update the group name…

 

//SIGNED//

CRAIG J. CARTER

__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___

Reply via email to