Auto-Cooling of cases

[dale]

On a busy Connect server one ends up a large number of shared cases quickly. It would be useful to be able to set a number of days (e.g. 90 days) after which cases will be taken offline automatically and the 'auto-sharing' flag removed if no access has occurred.

[ŁukaszBachman]

Hi Dale!

 

Would it be possible for you to measure the amount of memory that some of those cases consume? You see we already have the mechanism that puts cases to sleep (I'm sure you are aware of that). One can notice that when he opens a case URL and see the "Your case is being prepared" screen. When case is asleep it should hardly consume any resources. Perhaps something is causing your cases not to go asleep or they consume more memory that we thought they would?

[dale]

Lukasz - I'd like to revive this one. The Auto-cooling function would not so much be needed because of memory shortage. The reason is more that over time we build up a seriously long list of cases on Intella Connect. Then at some point matters enter a different stage where access to the data on Intella is no longer required. However, we may receive notification of this until the matter is truly closed and will keep the case live. So, during a Intella Connect service restart or system reboot we'll be experiencing significant delays as there is a seriously large list of cases that needs to be shutdown and then restarted. If a case hasn't seen activity for 3 months, we'd want to take it offline automatically. If it is needed again, we could re-share it with the flick of a button.

[Chris]

Hello Dale,

 

I made a note of this functionality request. I understand the use case and think it makes sense to add this. No promises though, we have a long list of good ideas...

[AdamS]

This actually feeds nicely to a previous request I'd made to have the ability to set a time limit that cases are actually shared for, that way we could set a case to share based on a date range (or no limit for permanent shares).