Dispatch Console and "System Filter" in Filters (Scheduling)

Hi DEBRIE,

By default, filters are stored on a per user basis, so each filter is only available to the user who created it and the default filter is activated when you open Dispatch Console. System filters are activated for all users. so in a way it a GLOBAL filter.

Also you can control user access by using the Security Setup Module.

• Go to the Security Setup module
• Choose the security role type (employee/admin etc..) 

• Search/filter for the module.
• Enable/Disable access as required using the checkboxes, as shown below.

Hi 

Thank you but it doesn’t really meet the need.

We need to have some “read only” filters (created by the admins and useable by all end-users), and end-users filters, created and used by them.

1st case : all user can use but can’t modify the filter

2nd case : only the owner can use, share or update the filter

so they all need to be able to create, and update some filters. What we need is to define some “read only” filters.

Thanks

Hi

Can you try the Custom settings in the Security Setup module.

From here you can add is_system_filter to the id field and set the permission as disabled for the user roles you want to restrict access.

This will make the field read-only for the specified user role, they can create and manage default/user specific filters but not system/global ones.

Note - A log off is required for effects to take place.

It looks great but we don’t have this custom field because running ALLIANCE V15, I guess, using only SMART CLIENT  :( 

Any other suggestion ?

Hello,

I found the custom permission settings and did like you’ve suggested. This prevents indeed any end-user to flag/unflag the system filter field, but it is still posssible to update the filter parameters, add, suppress or modifiy lines. So it doesn’t work, sorry.

Hi Laurence,

I had a similar discussion with R&D in regards to Views within modules.  From this discussion, I understood that a user always has the option to create their own views, even if the same name as the original view. Thus in the database, there are say two view rows, one being the global view and one being the personal view.

The personal view will ALWAYS override the global view which was meant to provide a standard view to ALL users when they have the same name.  To resolve going back to global view, it was necessary to delete the personal view and then the global view was available to the user again.

I suspect the same situation is occurring with the Dispatch Console filters… you have a system filter but the user can set up their own filter based on the system filter and it overrides the system filter.  To go back, you would have to use default again. 

I don’t believe it is possible to *lockdown* the system filters in a way that the user cannot override it with their own filter.  At least not without a change request customization.  I believe it is the application design that a user can always create their own views even if it is starting from the global system view.