@Alexander Heinze Thanks Alexander,Those 4,000 resources are for Crown, all in the USA, split across 73 “branches” each of which is a site, and those branches are grouped into 10 regions. Each branch/site handles its own dispatch of around 50 technicians. Reframing my questions I would ask, what is a recommended maximum number of resources per dataset when not using PSO? And to understand the potential performance impact, why would a dispatch console that is filtered to show only a few dozen resources suffer a performance problem even with an underlying dataset of thousands of resources?
Unfortunate, unlisted fields in the ARP, aka a Data Management List Type, can not be added via Lists. I’ve tried, and this inability is confirmed by:
The Baseline FSM-PSO integration is hard-coded to use the PRIMARY Response Code for accepted appointment offers. But in the Community of Practice it was mentioned that Ericsson had a customization in this area, and it seems that customization may be the issue here. Do you have a good handle on the details of that customization?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
