Cache of source files when filters are being used

We noticed that the cache folder in the user profile gets very big with source files from packages which are not applicable.

After doing some research with support we found the cause because of the way we use filters and the behavior of the filters:

Predictive filters (e.g., platform filters like checking for Windows OS) are static and their conditions are known to never change. As the filter isn’t met and will never be met, the package won’t be cached.

Non-predictive filters (e.g., condition sets and contexts) are dynamic and can change based on factors like group membership. Since there is a possibility these conditions might be met in the future, the system caches the files preemptively to ensure they’re available for offline use if needed.

We are using filters on packages to decide to which devices a package is applicable.

In our best practices we use the condition set (connected to a context) to be able to decide on which type of device an application will be available.

We do so by creating a context. This contexts has some checks including a part of the device naam to make sure if it is one of our virtual devices or physical devices, etc. We connect this context to a condition set. We know we can use the context directly but because condition sets have much more options, and we want to use a consistent procedure, we choose to always use condition sets as general filters, never a context.

For example:

• Application 1 can only be available on a managed laptops: Filter is set to the Condition set which check if you are using a managed laptop

• Application 2 can only be available on a Citrix full desktop: Filter is set to the Condition set which check if you are using a managed Citrix desktop

• Application 3 can be both available on a Citrix full desktop and laptop: Filter is set to the Condition set which check if you are using a managed Citrix desktop and another condition set to check if you are using a managed laptop

This way this packages are also not available on BYOD devices.

But because a condtion set is set to Non-predective filters, we cannot use the cache feature at all.

I would suggest not to remove the Non-predective filters feature, because I do understand the use.

Maybe it would be an extra option for the non-predivtive filters to have a checkbox to make it a predictive filter.