| **
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: 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 |
- Question: Group Name / Employee Name Change i... Carter, Craig J Civ ARPC/DPD
- Re: Question: Group Name / Employee Name... Peter Romain
- Re: Question: Group Name / Employee Name... Carter, Craig J Civ ARPC/DPD
- Re: Question: Group Name / Employee ... Peter Romain

