NEED MORE TECHNICAL EXPLANATION? HERE IT IS .ed
NEED MORE TECHNICAL EXPLANATION? HERE IT IS .
Above case studies have been covered by the following validations:
Run an iteration over the logged in users, and
Calculate average distribution capacity per logged-in user (say: AvgCapacityPerUser)
Calculate current distributed ticket per user (say: currentDistributedTickets)
Calculate ticket handling capacity per user/interval (say: handlingCapacity)
If currentDistributedTickets>= handlingCapacity , set handlingCapacity value to ‘0’
handlingCapacity value ‘0’ means stop distribution for the user
6. If AvgCapacityPerUser>0 and AvgCapacityPerUser<handlingCapacity, then distribute tickets as per AvgCapacityPerUser
7. If AvgCapacityPerUser>0 and AvgCapacityPerUser>handlingCapacity, then distribute tickets as per handlingCapacity
8. After ending the iteration, if any ticket remains to be distributed, run recursive iteration from step 1 to 8 again.
These validation conditions are applied for both inbox and feed tickets distribution.
Note:
Equal distribution may differ according to the handling capacity per individual user and if assignable tickets count is odd.The client browser sets a 5 min timer that checks and validates auto-assign interval. This timer will be reset and will start from the beginning of the user refreshes the browser. This means that if the user refreshes the browser just before the auto-assign process getting ready to start, it may delay max 5 min to start the process again.
Last updated