Differenze tra le versioni di "Views management"
Da itm wiki.
(Etichetta: visualeditor) |
(Etichetta: visualeditor) |
||
| Riga 54: | Riga 54: | ||
=== Forced Views === | === Forced Views === | ||
| − | + | This function is revered to the ''[[Glossary|Administrator]]. '' | |
| + | |||
| + | The local steps to create a forced view are: | ||
| + | * Define a Forced view master data | ||
| + | * Define the column to visualize in the view | ||
| + | * Define sort columns | ||
| + | * Define a publication authorization | ||
| + | * Define a default filter | ||
=== Personal Views === | === Personal Views === | ||
The logical step to define a Personal views are: | The logical step to define a Personal views are: | ||
| − | * ''[[Glossary|Administrator]] | + | * Configuration enablment |
| + | * Personal view creation | ||
| + | |||
| + | Tonfiguraiton enablementhe local steps to create a forced view are: | ||
| + | * ''[[Glossary|Administrator]] enable the resoruce to manage Personal Views'' | ||
| + | * ''[[Glossary|Administrator]] or Manager has to configure the scope per Module / Role data to show in a view'' | ||
* Resource define hisown Personal View | * Resource define hisown Personal View | ||
Versione delle 15:16, 23 gen 2018
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 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.
The local steps to create a forced view are:
- Define a Forced view master data
- Define the column to visualize in the view
- Define sort columns
- Define a publication authorization
- Define a default filter
Personal Views
The logical step to define a Personal views are:
- Configuration enablment
- Personal view creation
Tonfiguraiton enablementhe local steps to create a forced view are:
- Administrator enable the resoruce to manage Personal Views
- Administrator or Manager has to configure the scope per Module / Role data to show in a view
- Resource define hisown Personal View
