Replacing the Default View for End Users

Sub Banner

The simplest use of the End User Views module is to replace the default View presented to all users of your Zendesk account.

The default View (3) for an end user is presented when selecting the Compact list link (2) from withing the CHECK YOUR EXISTING REQUESTS tab (1).

Using the End User Views module it is possible to replace this View with an alternative list of Tickets and/or fields when the Compact list link is selected.

Create an Alternative View for use as the Default

The first step is to create a new View using the standard Zendesk functionality, to be used as the replacement default View for all end users.

This View can make use of any of the available conditions in the drop downs (1) and (2), however, in order to serve as the replacement default for end users the View must include the condition in which the Requester is the {current user} (3).

Deploy the End User WaaS Service

End User Views is part of a WaaS solution and so includes a Widget Service component (3) that provides a set of back end services to extend the Zendesk core functionality.

This Widget Service must be deployed from within the CloudSET WaaS Library (see the section of this manual describing the deployment and configuration of WaaS Components).

Invoke the End User Views Configurator

*Note: if you haven't already done so, before attempting to configure this Widget please familiarize yourself with the section of this manual describing the deployment and configuration of Widgets.

Once deployed the End User Views Widget (3) can be configured (4) and utilized from within the CloudSET Widget Library.

*Note: the presence of the red warning triangle (5) indicates that the dependent Widget Services have yet to be deployed (see previous step).

Select the Alternative View as the Default

The new View to be used as the replacement default will be present within the list of all available Views (1).

*Note: the selected View must include the condition in which the Requester is the {current user} (see Create an Alternative View for use as the Default above).

Drag this View and drop it onto the Default End User View node (2).

The replacement View will be created as the child node (3) and will then be used to replace the default View for all end users.

If necessary the default View can be removed at any time by dragging and dropping onto the "RUBBISH" bin (4).

Once the default View has been replaced remember to save the form (5), otherwise the updates will be lost when navigating away from the configurator.

See the Replacement Default View in Operation

The replacement default View (3) for an end user is now presented when selecting the Compact list link (2) from withing the CHECK YOUR EXISTING REQUESTS tab (1).

*Note: At this time it isn't possible to control or replace the name of the View when selecting the Compact list link and so unfortunately this is fixed as "Open Requests" (4) even if the replacement view contains solved or closed Tickets.

As such it is generally best practice to replace the default with a View that displays only open Tickets belonging to the logged in end user, but with an alternative and/or extended field set.

*Note: replacing the default view will also remove availability 0f the Zendesk default "recently solved or closed requests" View from the side panel (5).

See Alternative End Users Views for instructions concerning the introduction of alternative views that might include Tickets that have been solved or closed.

Replacing the Default View for End Users

Sub Banner

Replacing the Default View for End Users

The simplest use of the End User Views module is to replace the default View presented to all users of your Zendesk account.

The default View (3) for an end user is presented when selecting the Compact list link (2) from withing the CHECK YOUR EXISTING REQUESTS tab (1).

Using the End User Views module it is possible to replace this View with an alternative list of Tickets and/or fields when the Compact list link is selected.

Create an Alternative View for use as the Default

The first step is to create a new View using the standard Zendesk functionality, to be used as the replacement default View for all end users.

This View can make use of any of the available conditions in the drop downs (1) and (2), however, in order to serve as the replacement default for end users the View must include the condition in which the Requester is the {current user} (3).

Deploy the End User WaaS Service

End User Views is part of a WaaS solution and so includes a Widget Service component (3) that provides a set of back end services to extend the Zendesk core functionality.

This Widget Service must be deployed from within the CloudSET WaaS Library (see the section of this manual describing the deployment and configuration of WaaS Components).

Invoke the End User Views Configurator

*Note: if you haven't already done so, before attempting to configure this Widget please familiarize yourself with the section of this manual describing the deployment and configuration of Widgets.

Once deployed the End User Views Widget (3) can be configured (4) and utilized from within the CloudSET Widget Library.

*Note: the presence of the red warning triangle (5) indicates that the dependent Widget Services have yet to be deployed (see previous step).

Select the Alternative View as the Default

The new View to be used as the replacement default will be present within the list of all available Views (1).

*Note: the selected View must include the condition in which the Requester is the {current user} (see Create an Alternative View for use as the Default above).

Drag this View and drop it onto the Default End User View node (2).

The replacement View will be created as the child node (3) and will then be used to replace the default View for all end users.

If necessary the default View can be removed at any time by dragging and dropping onto the "RUBBISH" bin (4).

Once the default View has been replaced remember to save the form (5), otherwise the updates will be lost when navigating away from the configurator.

See the Replacement Default View in Operation

The replacement default View (3) for an end user is now presented when selecting the Compact list link (2) from withing the CHECK YOUR EXISTING REQUESTS tab (1).

*Note: At this time it isn't possible to control or replace the name of the View when selecting the Compact list link and so unfortunately this is fixed as "Open Requests" (4) even if the replacement view contains solved or closed Tickets.

As such it is generally best practice to replace the default with a View that displays only open Tickets belonging to the logged in end user, but with an alternative and/or extended field set.

*Note: replacing the default view will also remove availability 0f the Zendesk default "recently solved or closed requests" View from the side panel (5).

See Alternative End Users Views for instructions concerning the introduction of alternative views that might include Tickets that have been solved or closed.

Replacing the Default View for End Users

Sub Banner

The simplest use of the End User Views module is to replace the default View presented to all users of your Zendesk account.

The default View (3) for an end user is presented when selecting the Compact list link (2) from withing the CHECK YOUR EXISTING REQUESTS tab (1).

Using the End User Views module it is possible to replace this View with an alternative list of Tickets and/or fields when the Compact list link is selected.

Create an Alternative View for use as the Default

The first step is to create a new View using the standard Zendesk functionality, to be used as the replacement default View for all end users.

This View can make use of any of the available conditions in the drop downs (1) and (2), however, in order to serve as the replacement default for end users the View must include the condition in which the Requester is the {current user} (3).

Deploy the End User WaaS Service

End User Views is part of a WaaS solution and so includes a Widget Service component (3) that provides a set of back end services to extend the Zendesk core functionality.

This Widget Service must be deployed from within the CloudSET WaaS Library (see the section of this manual describing the deployment and configuration of WaaS Components).

Invoke the End User Views Configurator

*Note: if you haven't already done so, before attempting to configure this Widget please familiarize yourself with the section of this manual describing the deployment and configuration of Widgets.

Once deployed the End User Views Widget (3) can be configured (4) and utilized from within the CloudSET Widget Library.

*Note: the presence of the red warning triangle (5) indicates that the dependent Widget Services have yet to be deployed (see previous step).

Select the Alternative View as the Default

The new View to be used as the replacement default will be present within the list of all available Views (1).

*Note: the selected View must include the condition in which the Requester is the {current user} (see Create an Alternative View for use as the Default above).

Drag this View and drop it onto the Default End User View node (2).

The replacement View will be created as the child node (3) and will then be used to replace the default View for all end users.

If necessary the default View can be removed at any time by dragging and dropping onto the "RUBBISH" bin (4).

Once the default View has been replaced remember to save the form (5), otherwise the updates will be lost when navigating away from the configurator.

See the Replacement Default View in Operation

The replacement default View (3) for an end user is now presented when selecting the Compact list link (2) from withing the CHECK YOUR EXISTING REQUESTS tab (1).

*Note: At this time it isn't possible to control or replace the name of the View when selecting the Compact list link and so unfortunately this is fixed as "Open Requests" (4) even if the replacement view contains solved or closed Tickets.

As such it is generally best practice to replace the default with a View that displays only open Tickets belonging to the logged in end user, but with an alternative and/or extended field set.

*Note: replacing the default view will also remove availability 0f the Zendesk default "recently solved or closed requests" View from the side panel (5).

See Alternative End Users Views for instructions concerning the introduction of alternative views that might include Tickets that have been solved or closed.

Replacing the Default View for End Users

Sub Banner

Replacing the Default View for End Users

The simplest use of the End User Views module is to replace the default View presented to all users of your Zendesk account.

The default View (3) for an end user is presented when selecting the Compact list link (2) from withing the CHECK YOUR EXISTING REQUESTS tab (1).

Using the End User Views module it is possible to replace this View with an alternative list of Tickets and/or fields when the Compact list link is selected.

Create an Alternative View for use as the Default

The first step is to create a new View using the standard Zendesk functionality, to be used as the replacement default View for all end users.

This View can make use of any of the available conditions in the drop downs (1) and (2), however, in order to serve as the replacement default for end users the View must include the condition in which the Requester is the {current user} (3).

Deploy the End User WaaS Service

End User Views is part of a WaaS solution and so includes a Widget Service component (3) that provides a set of back end services to extend the Zendesk core functionality.

This Widget Service must be deployed from within the CloudSET WaaS Library (see the section of this manual describing the deployment and configuration of WaaS Components).

Invoke the End User Views Configurator

*Note: if you haven't already done so, before attempting to configure this Widget please familiarize yourself with the section of this manual describing the deployment and configuration of Widgets.

Once deployed the End User Views Widget (3) can be configured (4) and utilized from within the CloudSET Widget Library.

*Note: the presence of the red warning triangle (5) indicates that the dependent Widget Services have yet to be deployed (see previous step).

Select the Alternative View as the Default

The new View to be used as the replacement default will be present within the list of all available Views (1).

*Note: the selected View must include the condition in which the Requester is the {current user} (see Create an Alternative View for use as the Default above).

Drag this View and drop it onto the Default End User View node (2).

The replacement View will be created as the child node (3) and will then be used to replace the default View for all end users.

If necessary the default View can be removed at any time by dragging and dropping onto the "RUBBISH" bin (4).

Once the default View has been replaced remember to save the form (5), otherwise the updates will be lost when navigating away from the configurator.

See the Replacement Default View in Operation

The replacement default View (3) for an end user is now presented when selecting the Compact list link (2) from withing the CHECK YOUR EXISTING REQUESTS tab (1).

*Note: At this time it isn't possible to control or replace the name of the View when selecting the Compact list link and so unfortunately this is fixed as "Open Requests" (4) even if the replacement view contains solved or closed Tickets.

As such it is generally best practice to replace the default with a View that displays only open Tickets belonging to the logged in end user, but with an alternative and/or extended field set.

*Note: replacing the default view will also remove availability 0f the Zendesk default "recently solved or closed requests" View from the side panel (5).

See Alternative End Users Views for instructions concerning the introduction of alternative views that might include Tickets that have been solved or closed.