Views management

Overview

Vews are preconfigured selection of attributes and associated preferences including a filter to list records for an itmSUITE® managed entity.

The following table show the modules where the View can be created:

Module	Description
Ticket	is used to define user searching record set or to create a Dashboard KPI
Ticket activity	is used to define user searching record set or to create a Dashboard KPI
Related Ticket	is used to define the column shown in Ticket Related Ticket Tab
Related ticket preview	is used to define the preview shown in Ticket Related Ticket Tab
Ticket activity multiple edit	is used to define the Ticket Activity column shown to the user when the Multiple Edit mode is activated on Ticket activity tab.
Ticket Custom View
Timesheet	is used to define the Timesheet column view
Timesheet Expenses	is used to define the Timesheet detail expenses column view
TODO List: Milestone	is used to define the Todo list columns based on 'Project Milestone information
TODO List: Project Activity	is used to define the Todo list columns based on Project Activity information
TODO List: Ticket Activity	is used to define the Todo list columns based on Ticket Activity information

Views can be categorized also as:

• Forced views
• Personal views

Forced views is defined by the Administrator and used by the itmSUITE® to enable users to:

• Open / search / export ticket
• Create a record set for Dashboard

Personal views are created by the Resource and are visible only by the creator.

Forced Views

This function is revered to the Administrator. This function is accessible from Menu at link General/Company/Forced Views

The local steps to create a forced view are:

• Define a forced view general data
• Define the forced view columns
• Define sorting and operation on data
• Define the assignment authorization
• Define a default filter

Forced View General Data

This step enable the Administrator to define main characteristic of the View. The information are present in the General Tab of session

The table below contains all the view attribute to set.

Field	Description
Name	Forced View name. This will be the name shown to the user if no language name is configured. This field is mandatory
English	English language specific Forced View name. This will be the name shown to the user if his profile is configured with the English language. For more information about use of Languages in itmSUITE(r) see Language Management
FR, IT	Language specific Forced View name. This will be the name shown to the user if his profile is configured with the selected Language. For more information about use of Languages in itmSUITE(r) see Language Management
Module	This field define the scope module of the Forced Views. The choose of Model determine the list of fields that will be available in the Fields Tab. This field is mandatory
Status	This field define the Forced view status: Available values are: Inactive, Published as View, Published as Link and Published as View and Link. This field is mandatory
Mode	This field define the available look at field of the view. Available values are: List, Agenda
Default Mode	This field define the start up look at field of the view.
Description	View description

Forced View columns

This step enable the Administrator to define Forced View columns. The information are present in the Fields Tab of session

The table below contains all the view attribute to set.

Sorting & Operations

This step enable the Administrator to define the data view data sorting. The information are present in the Sorting & Operation Tab of session

The table below contains all the view attribute to set.

Assignment

This step enable the Administrator to define who will be authorized to access the view. The settings parameter are present in the Assignements Tab of session

The table below contains all the view attribute to set.

Default Filter

This step enable the Administrator to define the default filter of view. The settings parameter are present in the FilterTab of session. For futher detail see the Filter Management section

Personal Data views

The logical step to define a Personal views are:

• Configuration enablment
• Personal view creation

Configuration enablement

The local steps to create a forced view are:

• Administrator enable the resoruce to manage Personal Views
• Administrator or Manager has to configure the column set per Module / Role that will be chosen in views