Hi Piet,

For the situation with a person logged in a customiser, it is by design that changes made by a customizer user affects the organization and thus does not allow saving a personal view while still a customizer.

If you want to save personal views, you must disable the Customizer option in Employees Security and switch back when you want to save Organization views. The thinking behind this is a Customizer is supposed to impact the organization.

Regarding saving views, they are saved in a table call ap_application_views when saving from the Web Employee Portal.

Unfortunately, views saved while using the Astea Browser (which is being phased out) are not visible in the Web Employee portal and vice versa. This is confirmed with R&D. If you want to save views and have them visible in the Web Employee portal, they must be saved from the Web Employee Portal.

Key point is the Astea Browser is being deprecated and will eventually no longer be used in later versions.  Most of the functionality has already moved to the Web Employee Portal already with a few things still present in the Astea Browser such as Customizer and Dispatch Console.

Piet,

I reproduced the issue when saving the view to the Organization using Chrome and then logged into the application using MS Edge.  The new view is not visible for selection.  I have raised this to our development center to double-check this.

Plus, the views are saved to cp_application_views. I mistyped the table name in my previous response, my apologies.

For example, to retrieve the organization views for the customer support module, the following query:

select * from cp_application_views with(nolock)
where view_category = 'Organization'
and module_name = 'service_request_maint'

Kind regards,

Phil