You can now more easily maintain custom timeouts
for applications as you move from a port-based policy to an application-based
policy. Previously, you might have had to override App-ID (losing
application visibility) or create a custom App-ID (expending time
and research) in order to maintain custom timeouts for applications.
get started, configure custom timeout settings as part of a service
Then add the service object in a policy
rule to apply the custom timeouts to the application(s) the rule
enforces. See the full workflow to Maintain Custom Timeouts for Legacy Applications—you
can follow these same steps to apply custom timeouts to user groups.