http://wiki.itmsuite.eu/api.php?action=feedcontributions&user=Francesco.bertuletti&feedformat=atomitm wiki - Contributi utente [it]2024-03-29T12:58:54ZContributi utenteMediaWiki 1.31.1http://wiki.itmsuite.eu/index.php?title=BIRT_View&diff=4021BIRT View2018-11-22T15:07:17Z<p>Francesco.bertuletti: /* SERVICE CATALOGUE REQUEST (SRCS) VIEW */</p>
<hr />
<div>itmSUITE® propose to a customer a set of Standard view to facilitate the reporting development.<br />
The paragraphs below report the standard view collection and explains the relation between data’s<br />
<br />
== COMPANY VIEW ==<br />
This view report some company information. The View's name is: _STD_COMPANY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Company Id<br />
|-<br />
|NAME || nvarchar (400)|| Name of the company<br />
|-<br />
|DESCRIPTION || nvarchar (400)|| Description of the company<br />
|-<br />
|STATUS || nvarchar (510)|| Company Status<br />
|-<br />
|APPLICATION_URL || nvarchar (512)|| Applicaiton url, use to set a detail link information in notification<br />
|-<br />
|CONTACTS || nvarchar (400)|| Email of Application referent<br />
|-<br />
|TIMEZONE || nvarchar (64)|| Company Time Zone<br />
|-<br />
|DURATION_FORMAT || nvarchar (510)|| Unit of measure of Timesheet declaration<br />
|-<br />
|LABOURUNIT_ID || int (4)|| id of Labor<br />
|-<br />
|LABOUR_UNIT || nvarchar (8000)|| Unit of Measure of Labor. This is the unit of measure use in Budget estimation<br />
|}<br />
<br />
== CLIENT VIEW ==<br />
This view report some company information. The View's name is: _STD_CLIENT_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|- <br />
|ID || int (4)|| Client Id<br />
|-<br />
|CODE || int (4)|| Company internal identifier<br />
|-<br />
|NAME || nvarchar (400)|| Client Name<br />
|-<br />
|PARENT_ID || int (4)|| Parent Client id<br />
|-<br />
|CLSTATUS_ID || int (4)|| Status id<br />
|-<br />
|CLIENT_STATUS || nvarchar (8000)|| Status name<br />
|-<br />
|CLTYPE_ID || int (4)|| Id of client type <br />
|-<br />
|CLIENT_TYPE || nvarchar (512)|| Client Type<br />
|-<br />
|CREATOR_ID || int (4)|| Client Creator id <br />
|-<br />
|NATION_ID || int (4)|| Country id<br />
|-<br />
|NATION || nvarchar (512)|| Country Name<br />
|-<br />
|LANGUAGE_ID || int (4)|| Language Id<br />
|-<br />
|LANGUAGE || nvarchar (512)|| Language Name<br />
|-<br />
|PAYMENTTERM_ID || int (4)|| Payment terms id<br />
|-<br />
|PAYMENTTERM || nvarchar (512)|| Payment terms<br />
|-<br />
|REMARK || nvarchar (400)|| REMARKs<br />
|-<br />
|TAX_NUMBER || nvarchar (100)|| Vat number<br />
|-<br />
|AII || bit (1)|| Flag stated that All Invoice has been Issued <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field<br />
|}<br />
<br />
== CLIENT ORGANIZATION UNIT VIEW ==<br />
This view report some company information. The View's name is: _STD_CLIENT_ORGANIZATION_UNIT_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Organization Unit Id<br />
|-<br />
|CODE || int (4)|| Organization Unit internal identifier<br />
|-<br />
|NAME || nvarchar (512)|| Organization Unit name<br />
|-<br />
|STATUS || nvarchar (510)|| Organization Unit status<br />
|-<br />
|CLIENT_ID || int (4)|| Reference to client the Organization Unit belongs to<br />
|-<br />
|PARENT_ID || int (4)|| Reference to father Organization Unit <br />
|-<br />
|PATH || nvarchar (8000)|| Chain of Organization Unit <br />
|-<br />
|CUSTOM_FIELD_1 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_2 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|CUSTOM_FIELD_3 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_4 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_5 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|CUSTOM_FIELD_6 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|ADDRESS || nvarchar (400)|| Organization Unit Address<br />
|-<br />
|POSTAL_CODE || nvarchar (200)|| Organization Unit Postal Code<br />
|-<br />
|CITY || nvarchar (200)|| Organization Unit City<br />
|-<br />
|REGION || nvarchar (200)|| Organization Unit Region<br />
|-<br />
|NATION || nvarchar (512)|| Organization Unit Nation<br />
|-<br />
|PHONE || nvarchar (200)|| Organization Unit Phone number<br />
|-<br />
|FAX || nvarchar (200)|| Organization Unit Fax number<br />
|-<br />
|MAIL || nvarchar (200)|| Organization Unit Email address<br />
|-<br />
|REMARK || nvarchar (400)|| Organization Unit Address remark<br />
|}<br />
<br />
== RESOURCE VIEW ==<br />
This view report some company information. The View's name is: _STD_RESOURCE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Resource Id<br />
|-<br />
|CODE || int (4)|| Resource internal identifier<br />
|-<br />
|LOGIN || nvarchar (400)|| Resource login<br />
|-<br />
|NAME || nvarchar (400)|| Resource name<br />
|-<br />
|SURNAME || nvarchar (400)|| Resource surname<br />
|-<br />
|FULLNAME || nvarchar (802)|| Resource surname + name<br />
|-<br />
|RESOURCE_STATUS_ID || int (4)|| Resource Status id<br />
|-<br />
|RESOURCE_STATUS || nvarchar (512)|| Resource Status name<br />
|-<br />
|CREATOR_ID || int (4)|| Resource Creator id<br />
|-<br />
|NATION_ID || int (4)|| Resource Nation id<br />
|-<br />
|NATION || nvarchar (512)|| Nation<br />
|-<br />
|CLIENT_ID || int (4)|| Id of client the resource belongs to<br />
|-<br />
|CLIENT || nvarchar (400)|| Name of client the resource belongs to<br />
|-<br />
|ORGANIZATION_UNIT_ID || int (4)|| Organization Unit id the resource belongs to<br />
|-<br />
|PATH || nvarchar (8000)|| Organization Unit path<br />
|-<br />
|SALEROLE_ID || int (4)|| Sale Role id, this information can drive sales revenue amount<br />
|-<br />
|SALES_ROLE || nvarchar (512)|| Sale Role name<br />
|-<br />
|SUPPLIER_ID || int (4)|| Id of supplier the resource belongs to<br />
|-<br />
|SUPPLIER || nvarchar (400)|| Name of supplier the resource belongs to <br />
|-<br />
|PURCHASEROLE_ID || int (4)|| Purchase Role id, this information can drive Purchase cost amount<br />
|-<br />
|PURCHASE_ROLE || nvarchar (512)|| Purchase Role name<br />
|-<br />
|BIRTH_DAY || datetime (8)|| Resource birth day<br />
|-<br />
|BIRTH_PLACE || nvarchar (400)|| Resource birth Place<br />
|-<br />
|EXTERNALCODE || nvarchar (400)|| Field used to store external resource reference <br />
|-<br />
|RESTYPE_ID || int (4)|| Id of Resource type<br />
|-<br />
|VIP_TYPE || int (4)|| Resource type name<br />
|-<br />
|CANDECLAREHOLIDAY || bit (1)|| Flag that identify if the resource can declare his own holiday<br />
|-<br />
|CANDECLAREILLNESS || bit (1)|| Flag that identify if the resource can declare his own illness <br />
|-<br />
|IS_EDIT_RESOURCE_DATA || bit (1)|| This flag enable the resource to modify his own data<br />
|-<br />
|IS_PERSONAL_VIEW_RIGHT || bit (1)|| This flag enable the resource to define personal view<br />
|-<br />
|CMS_ACCESS || bit (1)|| This flag enable the resource to access the Configuration Management System<br />
|-<br />
|USER_MAPPING_MODE || nvarchar (510)|| <br />
|-<br />
|EXT_CMDB_MODIFY || bit (1)|| <br />
|-<br />
|EXT_CMDB_VIEW || bit (1)|| <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field<br />
|}<br />
<br />
== PROJECT SERVICE VIEW ==<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Project Id<br />
|-<br />
|CODE || int (4)|| Project internal identifier<br />
|-<br />
|MAIN_TYPE_ID || int (4)|| Automatically field by system<br />
|-<br />
|MAIN_TYPE || varchar (7)|| This field can assume Project or Service value<br />
|-<br />
|GANTT_ESTIMATION_MODE || nvarchar (510)|| This field can assume Budget or Forecast value<br />
|-<br />
|NAME || nvarchar (400)|| Project Name<br />
|-<br />
|DESCRIPTION || nvarchar (400)|| Project Description<br />
|-<br />
|OBJECTIVES || nvarchar (1600)|| Project Objectives <br />
|-<br />
|COMMENT || nvarchar (1600)|| Project Comments <br />
|-<br />
|OPER_START_DATE || datetime (8)|| Internal Operational Start Date<br />
|-<br />
|OPER_END_DATE || datetime (8)|| Internal Operational Start End <br />
|-<br />
|EFFECTIVE_START || datetime (8)|| Actual Start Date<br />
|-<br />
|EFFECTIVE_END || datetime (8)|| Actual End Date <br />
|-<br />
|INITIAL_EXPECTED_START || datetime (8)|| Initial expected Start Date <br />
|-<br />
|INITIAL_EXPECTED_END || datetime (8)|| Initial expected Start Date <br />
|-<br />
|CURRENT_EXPECTED_START || datetime (8)|| Current Start Date <br />
|-<br />
|CURRENT_EXPECTED_END || datetime (8)|| Current End Date <br />
|-<br />
|CLIENT_ID || int (4)|| Id of client the resource belongs to<br />
|-<br />
|CLIENT || nvarchar (512)|| Name of client the resource belongs to <br />
|-<br />
|CREATOR_ID || int (4)|| Resource Creator id<br />
|-<br />
|CURRENCY_ID || int (4)|| Currency id<br />
|-<br />
|currency || nvarchar (512)|| Currency<br />
|-<br />
|FINALCLIENT_ID || int (4)|| Second reference on Client id<br />
|-<br />
|FINALCLIENT || nvarchar (400)||Second reference Client Name<br />
|-<br />
|PARENT_PRJ_ID || int (4)|| Parent project id<br />
|-<br />
|PRJADMSTATUS_ID || int (4)|| Project administrative status id<br />
|-<br />
|PROJECT_ADM_STATUS || nvarchar (8000)|| Project administrative<br />
|-<br />
|PRJ_CLASS_ID || int (4)|| Project Class id<br />
|-<br />
|CLASS || nvarchar (400)|| Project Class<br />
|-<br />
|PRJOPSTATUS_ID || int (4)|| Project Operative status id<br />
|-<br />
|PROJECT_STATUS || nvarchar (8000)|| Project Operative <br />
|-<br />
|PRJTYPE_ID || int (4)|| Project Type id<br />
|-<br />
|PROJECT_TYPE || nvarchar (512)|| Project Type <br />
|-<br />
|STATPRJ_ID || int (4)|| Statistical project id<br />
|-<br />
|STATISTICAL || nvarchar (512)|| Statistical project id <br />
|-<br />
|EXTERNAL_CODE || nvarchar (100)|| External reference code<br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field <br />
|}<br />
=== PROJECT SERVICE ACTIVITY VIEW ===<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|id || int (4)|| Project Activity Id<br />
|-<br />
|CODE || int (4)|| Project Activity internal identifier<br />
|-<br />
|ORDERING_NUMBER || int (4)|| Sort order<br />
|-<br />
|TASK_NAME || nvarchar (2048)|| Task name<br />
|-<br />
|DESCRIPTION || nvarchar (1000)|| Task Description<br />
|-<br />
|START_DATE || datetime (8)|| Activity start date <br />
|-<br />
|END_DATE || datetime (8)|| Activity end date <br />
|-<br />
|ACTPRIORITY_ID || int (4)|| Activity priority id<br />
|-<br />
|PRIORITY || nvarchar (512)|| Priority<br />
|-<br />
|ACTSTATUS_ID || int (4)|| Activity status id <br />
|-<br />
|STATUS || nvarchar (512)|| Activity status <br />
|-<br />
|ACTIVITY_TYPE_ID || int (4)|| Activity type id <br />
|-<br />
|ACTIVITY_TYPE || nvarchar (512)|| Activity type <br />
|-<br />
|PRJ_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|DURATION || float (8)|| Estimated duration of task <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationUser || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation date, Automatic field<br />
|}<br />
<br />
== TICKET VIEW ==<br />
This view report some company information. The View's name is: _STD_TICKET_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Project Id<br />
|-<br />
|CODE || int (4)|| Project internal identifier<br />
|-<br />
|TICKETTYPE_ID || int (4)|| Ticket type reference id<br />
|-<br />
|TICKET_TYPE || nvarchar (512)|| Ticket type name<br />
|-<br />
|PROJECT_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|SERVICE_REQUEST_ID || int (4)||Service catalogue request reference id<br />
|-<br />
|SERVICE_REQUEST || nvarchar (1024)|| Service catalogue request reference name<br />
|-<br />
|CURRENT_SERVICE_REQUEST_ID || int (4)|| Current Service catalogue request reference id<br />
|-<br />
|CURRENT_SERVICE_REQUEST || nvarchar (1024)|| Current Service catalogue request reference name <br />
|-<br />
|SHORT_DESCRIPTION || nvarchar (-1)|| Ticket short description<br />
|-<br />
|DESCRIPTION || nvarchar (-1)|| Ticket Description<br />
|-<br />
|ANALYSIS || nvarchar (-1)|| Ticket Analisys description<br />
|-<br />
|SOLUTION || nvarchar (-1)|| Ticket Solution description<br />
|-<br />
|WORKAROUND || nvarchar (-1)|| Ticket Workaound description <br />
|-<br />
|COMMENTS || nvarchar (-1)|| Ticket Comments<br />
|-<br />
|OWNER_ID || int (4)|| Ticket Owner Resource reference <br />
|-<br />
|OWNER || nvarchar (512)||Ticket Owner Resource <br />
|-<br />
|REQUESTER_ID || int (4)|| Ticket Requester reference id<br />
|-<br />
|REQUESTER || nvarchar (802)||Ticket Requester reference<br />
|-<br />
|RESOURCE_ID || int (4)|| Ticket Resource reference id<br />
|-<br />
|RESOURCE || nvarchar (802)||Ticket Resource reference<br />
|-<br />
|REQUIRED_SOLUTION_DATE || datetime (8)|| Ticket required solution date <br />
|-<br />
|FORECAST_SOLUTION_DATE || datetime (8)|| Forecast solution date of ticket<br />
|-<br />
|SOLUTIONGROUP_ID || int (4)|| Group reference id. At each group per workflow is assigned a specific role.<br />
|-<br />
|DSG1 || nvarchar (512)|| Group reference name<br />
|-<br />
|MASTER_SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DSG2 || nvarchar (512)|| Group reference name<br />
|-<br />
|THIRD_SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DSG3 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG4_ID || int (4)|| Group reference id<br />
|-<br />
|DSG4 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG5_ID || int (4)|| Group reference id<br />
|-<br />
|DSG5 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG6_ID || int (4)|| Group reference id<br />
|-<br />
|DSG6 || nvarchar (512)|| Group reference name<br />
|-<br />
|WORKFLOW_ID || int (4)|| Workflow reference id<br />
|-<br />
|WORKFLOW_DESCRIPTION || nvarchar (2048)|| Workflow description<br />
|-<br />
|WORKFLOW_TICKET_ADM_STATUS_ID || int (4)|| Workflow administrarive status id<br />
|-<br />
|WORKFLOW_TICKET_ADM_STATUS || nvarchar (512)|| Workflow administrarive status<br />
|-<br />
|WORKFLOW_TICKET_OP_STATUS_ID || int (4)|| Workflow operative status id<br />
|-<br />
|WORKFLOW_TICKET_OP_STATUS || nvarchar (512)|| Workflow operative status<br />
|-<br />
|RESOLUTION_CAUSE_ID || int (4)|| Ticket resolution cause reference id <br />
|-<br />
RESOLUTION_CAUSE || nvarchar (512)|| Ticket resolution cause reference <br />
|-<br />
|TICKET_CLOSURE_CAUSE_ID || int (4)|| Ticket closure cause reference id<br />
|-<br />
|TICKET_CLOSURE_CAUSE || nvarchar (512)|| Ticket closure cause reference <br />
|-<br />
|REQUESTED_PRIORITY_ID || int (4)|| Ticket requested priority id<br />
|-<br />
|REQUESTED_PRIORITY || nvarchar (512)|| Ticket requested priority <br />
|-<br />
|TARGET_ENVIRONMENT_ID || int (4)|| Target environment reference id <br />
|-<br />
|TARGET_ENVIRONMENT || nvarchar (512)|| Target environment reference <br />
|-<br />
|TICKET_IMPACT_ID || int (4)|| Ticket impact id<br />
|-<br />
|TICKET_IMPACT || nvarchar (512)|| Ticket impact reference <br />
|-<br />
|TICKET_URGENCY_ID || int (4)|| Ticket urgency id<br />
|-<br />
|TICKET_UREGENCY || nvarchar (512)|| Ticket urgency reference <br />
|-<br />
|TICKET_PRIORITY_ID || int (4)|| Ticket priority id, usually this is calculated field value based on Ticket Impact and Urgency<br />
|-<br />
|TICKET_PRIORITY || nvarchar (512)|| Ticket priority reference <br />
|-<br />
|TICKET_ACTIVITY_TEMPLATE_ID || int (4)|| Ticket activity id of template used to load the Ticket activity<br />
|-<br />
|TICKET_ACTIVITY_TEMPLATE || nvarchar (200)||Ticket activity template used to load the Ticket activity <br />
|-<br />
|TUPLE_TICKET_AREA_ID || int (4)|| First level of Standard Tuple. Ticket Area reference id<br />
|-<br />
|TUPLE_TICKET_AREA || nvarchar (512)|| First level of Standard Tuple. Ticket Area reference name<br />
|-<br />
|TUPLE_TICKET_CATEGORY_ID || int (4)|| Second level of Standard Tuple. Ticket Category reference id<br />
|-<br />
|TUPLE_TICKET_CATEGORY || nvarchar (512)|| Second level of Standard Tuple. Ticket Category reference name <br />
|-<br />
|TUPLE_TICKET_TOPIC_ID || int (4)|| Third level of Standard Tuple. Ticket Topic reference id <br />
|-<br />
|TUPLE_TICKET_TOPIC || nvarchar (512)|| Third level of Standard Tuple. Ticket Topic reference name <br />
|-<br />
|ESTIMATION_START || datetime (8)|| Ticket Estimation Start range date <br />
|-<br />
|ESTIMATION_END || datetime (8)|| Ticket Estimation End range date <br />
|-<br />
|ESTIMATION_DATE || datetime (8)|| Ticket Estimation cutoff date <br />
|-<br />
|ESTIMATION_MODE || int (4)|| Ticket Estimation mode<br />
|-<br />
|COST_METHOD || nvarchar (510)|| Ticket cost method, can assume a value Standard or Fixed Cost Only <br />
|-<br />
|ATTACHMENT_PRESENT || bit (1)|| Flag stated at least on document is attached to a ticket <br />
|-<br />
|ACTIVITY_ASSIGN || varchar (21)|| This field can assume a value Activity Not Assigned or Activity Assigned<br />
|-<br />
|TICKET_USER_INFO_ID || int (4)|| Ticket requester information reference id <br />
|-<br />
|CREATION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|CREATION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|CLOSE_DATE || datetime (8)|| Ticket close date<br />
|-<br />
|CLOSE_USER || nvarchar (512)|| Ticket close user <br />
|}<br />
=== TICKET ACTIVITY VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Ticket activity Id<br />
|-<br />
|CODE || int (4)|| Ticket activity internal identifier<br />
|-<br />
|TICKET_ACTIVITY_TYPE_ID || int (4)|| Ticket Activity type reference id <br />
|-<br />
|TICKET_ACTIVITY_TYPE || nvarchar (1600)|| Ticket Activity type reference name<br />
|-<br />
|TICKET_ACTIVITY_SUB_TYPE_ID || int (4)|| Ticket Activity Subtype reference id <br />
|-<br />
|TICKET_ACTIVITY_SUB_TYPE || nvarchar (1000)|| Ticket Activity Subtype reference name<br />
|-<br />
|TICKET_ACTIVITY_STATUS_ID || int (4)||Ticket Activity status reference id <br />
|-<br />
|TICKET_ACTIVITY_STATUS || nvarchar (8000)|| Ticket Activity status reference name<br />
|-<br />
|NAME || nvarchar (512)|| Ticket Activity Name<br />
|-<br />
|DESCRIPTION || nvarchar (-1)|| Ticket Activity Description<br />
|-<br />
|COMMENTS || nvarchar (-1)|| Ticket Activity Comment<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|-<br />
|ASSIGNEE || nvarchar (8000)|| Resource reference name<br />
|-<br />
|SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DURATION || float (8)|| Estimated duration of task <br />
|-<br />
|REQUIRED_START_DATE || datetime (8)|| Ticket required solution start date <br />
|-<br />
|REQUIRED_END_DATE || datetime (8)|| Ticket required solution end+ date <br />
|-<br />
|FORECASTED_START_DATE || datetime (8)|| Forecast solution start date of ticket<br />
|-<br />
|FORECASTED_END_DATE || datetime (8)|| Forecast solution end date of ticket<br />
|-<br />
|EFFECTIVE_START_DATE || datetime (8)|| Actaul solution start date of ticket<br />
|-<br />
|EFFECTIVE_END_DATE || datetime (8)|| Actual solution end date of ticket<br />
|-<br />
|PAID || bit (1)|| If true the recored Timesheet hours are taken in account into the balance column of estimation<br />
|-<br />
|ORDERING_NUMBER || int (4)|| Sort Order<br />
|-<br />
|CREATION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|CREATION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
<br />
|}<br />
=== TICKET CONFIGURATION ITEM VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_CONFIGURATION_ITEM_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Configuration Item Id<br />
|-<br />
|GUID || nvarchar (100)|| Configuration Item GUID<br />
|-<br />
|NAME || nvarchar (510)|| Configuration Item Name<br />
|-<br />
|TYPE || nvarchar (510)|| Configuration Item type<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|}<br />
<br />
=== TICKET CUSTOM FIELD VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_CUSTOM_FIELDS_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Ticket custom field reference Id<br />
|-<br />
|NAME || nvarchar (512)|| Ticket custom field reference Name<br />
|-<br />
|TYPE || nvarchar (8000)|| This field contains the type of the data inserted<br />
|-<br />
|VALUE || nvarchar (-1)|| Ticket custom field value<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|}<br />
=== TICKET ESTIMATION VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_ESTIMATION_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
<br />
<br />
=== TICKET FIELD VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_FIELD_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Field reference Id<br />
|-<br />
|NAME || nvarchar (256)|| Field reference Name<br />
|-<br />
|TICKET_FIELD_TYPE_ID || nvarchar (255)|| This field contains the type of the data inserted. Three possible values can be present <br />
* "PREDEFINED": used to define that the field is a Standard Field<br />
* "CUSTOM": used to define that the field is a Custom Field<br />
* "OBJECTIVE":automatically added by the system when the cusomer declare an Objective<br />
|}<br />
<br />
=== TICKET OCE OBJECTIVE VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_OCE_OBJECTIVE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET RELATED VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_RELATED_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET USER INFO VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_USER_INFO_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET USER NOTE VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_USER_NOTE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET WORKER VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_WORKER_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
== TIMESHEET VIEW ==<br />
This view report some company information. The View's name is: _STD_TIMESHEET_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Timesheet Id<br />
|-<br />
|CODE || int (4)|| Timesheet internal identifier<br />
|-<br />
|PRJ_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|CURRENCY_ID || int (4)|| Currency reference id <br />
|-<br />
|CURRENCY || nvarchar (512)|| Currency reference name<br />
|-<br />
|RESRC_ID || int (4)|| Resource reference id<br />
|-<br />
|RESOURCE || nvarchar (802)|| Resource reference<br />
|-<br />
|GROUP_ID || int (4)|| Group reference id<br />
|-<br />
|GROUP || nvarchar (512)|| Group reference name<br />
|-<br />
|WPLACE_ID || int (4)|| Location reference id <br />
|-<br />
|LOCATION || nvarchar (512)|| Location reference name<br />
|-<br />
|PURCHASE_ROLE_ID || int (4)|| Pruchase Role reference id <br />
|-<br />
|PURCHASE_ROLE || nvarchar (512)|| Pruchase Role reference name<br />
|-<br />
|ACTIVITY_DATE || datetime (8)|| Timesheet activity date<br />
|-<br />
|DURATION || float (8)|| Timesheet duration. This is the duration declared in a resource section<br />
|-<br />
|PM_DURATION || float (8)|| Timesheet duration. This is the duration declared in a PM section<br />
|-<br />
|MANAGER_DURATION || float (8)||Timesheet duration. This is the duration declared in a Manager section <br />
|-<br />
|ACT_DESCRIPTION || nvarchar (2000)||Timesheet Actvity description. This is the duration declared in a resource section<br />
|-<br />
|PM_ACT_DESCRIPTION || nvarchar (2000)|| Timesheet Actvity description. This is the duration declared in a PM section <br />
|-<br />
|MANAGER_ACT_DESCRIPTION || nvarchar (2000)|| Timesheet Actvity description. This is the duration declared in a Manager section <br />
|-<br />
|ACTIVITY_ID || int (4)|| Timesheet Actvity id. This is the id related to a resource section <br />
|-<br />
|PM_ACTIVITY_ID || int (4)|| Timesheet Actvity id. This is the id related to a PM section <br />
|-<br />
|MANAGER_ACTIVITY_ID || int (4)||Timesheet Actvity id. This is the id related to a Manager section <br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|-<br />
|TICKETACTIVITY_ID || int (4)|| Ticket Activity reference id <br />
|-<br />
|TICKETDESCRIPTION || nvarchar (8000)|| Ticket Activity description, copied from Ticket Activity <br />
|-<br />
|TICKETCOMMENTS || nvarchar (8000)|| Ticket Activity Comment<br />
|-<br />
|ROWRPMSTAT_ID || int (4)|| Timesheet Operational status Resource / PM section<br />
|-<br />
|ROWMSTAT_ID || int (4)|| Timesheet Operational status Manager section<br />
|-<br />
|COMMENT || nvarchar (400)|| Comment inserted by resource <br />
|-<br />
|PM_COMMENT || nvarchar (400)|| Comment inserted by PM <br />
|-<br />
|MANAGER_COMMENT || nvarchar (400)|| Comment inserted by Manager <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationUser || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation date, Automatic field<br />
|}<br />
<br />
== TUPLE VIEW ==<br />
This view report some company information. The View's name is: _STD_TUPLE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int|| Tuple Identifier<br />
|-<br />
|CODE || int|| Tuple Identifier<br />
|-<br />
|COMPANY_ID || int|| Company Identifier<br />
|-<br />
|TUPLE_NAME || varchar(256)|| Tupla Name<br />
|-<br />
|TUPLE_AREA_ID || int|| First level of Tuple, Area, Identifier<br />
|-<br />
|TUPLE_AREA || varchar(256)|| Tuple Area Name<br />
|-<br />
|TUPLE_CATEGORY_ID || int|| Second level of Tuple, Category, Identifier<br />
|-<br />
|TUPLE_CATEGORY || varchar(256)|| Tuple Category Name<br />
|-<br />
|TUPLE_TOPIC_ID || int|| Third level of Tuple, Topic, Identifier<br />
|-<br />
|TUPLE_TOPIC || varchar(256)|| Tuple Topic Name<br />
|}<br />
<br />
== SERVICE CATALOGUE REQUEST (SRCS) VIEW ==<br />
This view report some company information. The View's name is: _STD_SRCS_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|CATALOGO || nvarchar (2048)|| Identify a complete set of service catalogue requests <br />
|-<br />
|SECTION || nvarchar (512)|| Sub session of catalogue of requests <br />
|-<br />
|TOPIC_1 || nvarchar (1024)|| Level 1 of nested level of section <br />
|-<br />
|TOPIC_2 || nvarchar (1024)|| Level 2 of nested level of section <br />
|-<br />
|TOPIC_3 || nvarchar (1024)|| Level 3 of nested level of section <br />
|-<br />
|ID || int (4)|| Service request catalogue Id<br />
|-<br />
|SERVICE_REQUEST || nvarchar (1024)|| Service catalogue request reference name<br />
|-<br />
|ENABLED || bit (1)|| Flag stated if the SRCS request is enabled <br />
|-<br />
|PROJECT_ID || int (4)|| Project reference id<br />
|-<br />
|TICKET_TYPE_ID || int (4)|| Ticket type reference id <br />
|-<br />
|TRANSITION_RULE_ID || int (4)|| Transition rule activated when a new ticket is created<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|TICKET_TYPE || nvarchar (512)|| Ticket type reference name <br />
|-<br />
|TRANSITION_RULE || nvarchar (512)|| Transition rule name<br />
|-<br />
|TATPL_ID|| int || Ticket Activity Template id<br />
|-<br />
|TA_TEMPLATE|| nvarchar (100)|| Ticket Activity Template name<br />
|-<br />
|SOLUTIONGROUP || nvarchar (-1)|| Group reference name<br />
|-<br />
|MASTER_SOLUTIONGROUP || nvarchar (-1)|| Group reference name<br />
|-<br />
|OWNER || nvarchar (-1)|| Owner reference name<br />
|-<br />
|TAB_RESOURCES || nvarchar (-1)|| Tab of SRCS session used to grant a request to Resources<br />
|-<br />
|TAB_SOLUTIONGROUP || nvarchar (-1)|| Tab of SRCS session used to grant a request to Groups<br />
|-<br />
|TAB_ORGANIZATIONUNIT || nvarchar (-1)|| Tab of SRCS session used to grant a request to Organization Unit<br />
|-<br />
|CLIENT || nvarchar (-1)|| Client reference name<br />
|-<br />
|OU Name || nvarchar (-1)|| Organization Unit reference name<br />
|-<br />
|Ticket Requester || nvarchar (-1)|| Requester of ticket reference name<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=BIRT_View&diff=4020BIRT View2018-11-22T13:32:23Z<p>Francesco.bertuletti: /* SERVICE CATALOGUE REQUEST (SRCS) VIEW */</p>
<hr />
<div>itmSUITE® propose to a customer a set of Standard view to facilitate the reporting development.<br />
The paragraphs below report the standard view collection and explains the relation between data’s<br />
<br />
== COMPANY VIEW ==<br />
This view report some company information. The View's name is: _STD_COMPANY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Company Id<br />
|-<br />
|NAME || nvarchar (400)|| Name of the company<br />
|-<br />
|DESCRIPTION || nvarchar (400)|| Description of the company<br />
|-<br />
|STATUS || nvarchar (510)|| Company Status<br />
|-<br />
|APPLICATION_URL || nvarchar (512)|| Applicaiton url, use to set a detail link information in notification<br />
|-<br />
|CONTACTS || nvarchar (400)|| Email of Application referent<br />
|-<br />
|TIMEZONE || nvarchar (64)|| Company Time Zone<br />
|-<br />
|DURATION_FORMAT || nvarchar (510)|| Unit of measure of Timesheet declaration<br />
|-<br />
|LABOURUNIT_ID || int (4)|| id of Labor<br />
|-<br />
|LABOUR_UNIT || nvarchar (8000)|| Unit of Measure of Labor. This is the unit of measure use in Budget estimation<br />
|}<br />
<br />
== CLIENT VIEW ==<br />
This view report some company information. The View's name is: _STD_CLIENT_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|- <br />
|ID || int (4)|| Client Id<br />
|-<br />
|CODE || int (4)|| Company internal identifier<br />
|-<br />
|NAME || nvarchar (400)|| Client Name<br />
|-<br />
|PARENT_ID || int (4)|| Parent Client id<br />
|-<br />
|CLSTATUS_ID || int (4)|| Status id<br />
|-<br />
|CLIENT_STATUS || nvarchar (8000)|| Status name<br />
|-<br />
|CLTYPE_ID || int (4)|| Id of client type <br />
|-<br />
|CLIENT_TYPE || nvarchar (512)|| Client Type<br />
|-<br />
|CREATOR_ID || int (4)|| Client Creator id <br />
|-<br />
|NATION_ID || int (4)|| Country id<br />
|-<br />
|NATION || nvarchar (512)|| Country Name<br />
|-<br />
|LANGUAGE_ID || int (4)|| Language Id<br />
|-<br />
|LANGUAGE || nvarchar (512)|| Language Name<br />
|-<br />
|PAYMENTTERM_ID || int (4)|| Payment terms id<br />
|-<br />
|PAYMENTTERM || nvarchar (512)|| Payment terms<br />
|-<br />
|REMARK || nvarchar (400)|| REMARKs<br />
|-<br />
|TAX_NUMBER || nvarchar (100)|| Vat number<br />
|-<br />
|AII || bit (1)|| Flag stated that All Invoice has been Issued <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field<br />
|}<br />
<br />
== CLIENT ORGANIZATION UNIT VIEW ==<br />
This view report some company information. The View's name is: _STD_CLIENT_ORGANIZATION_UNIT_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Organization Unit Id<br />
|-<br />
|CODE || int (4)|| Organization Unit internal identifier<br />
|-<br />
|NAME || nvarchar (512)|| Organization Unit name<br />
|-<br />
|STATUS || nvarchar (510)|| Organization Unit status<br />
|-<br />
|CLIENT_ID || int (4)|| Reference to client the Organization Unit belongs to<br />
|-<br />
|PARENT_ID || int (4)|| Reference to father Organization Unit <br />
|-<br />
|PATH || nvarchar (8000)|| Chain of Organization Unit <br />
|-<br />
|CUSTOM_FIELD_1 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_2 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|CUSTOM_FIELD_3 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_4 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_5 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|CUSTOM_FIELD_6 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|ADDRESS || nvarchar (400)|| Organization Unit Address<br />
|-<br />
|POSTAL_CODE || nvarchar (200)|| Organization Unit Postal Code<br />
|-<br />
|CITY || nvarchar (200)|| Organization Unit City<br />
|-<br />
|REGION || nvarchar (200)|| Organization Unit Region<br />
|-<br />
|NATION || nvarchar (512)|| Organization Unit Nation<br />
|-<br />
|PHONE || nvarchar (200)|| Organization Unit Phone number<br />
|-<br />
|FAX || nvarchar (200)|| Organization Unit Fax number<br />
|-<br />
|MAIL || nvarchar (200)|| Organization Unit Email address<br />
|-<br />
|REMARK || nvarchar (400)|| Organization Unit Address remark<br />
|}<br />
<br />
== RESOURCE VIEW ==<br />
This view report some company information. The View's name is: _STD_RESOURCE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Resource Id<br />
|-<br />
|CODE || int (4)|| Resource internal identifier<br />
|-<br />
|LOGIN || nvarchar (400)|| Resource login<br />
|-<br />
|NAME || nvarchar (400)|| Resource name<br />
|-<br />
|SURNAME || nvarchar (400)|| Resource surname<br />
|-<br />
|FULLNAME || nvarchar (802)|| Resource surname + name<br />
|-<br />
|RESOURCE_STATUS_ID || int (4)|| Resource Status id<br />
|-<br />
|RESOURCE_STATUS || nvarchar (512)|| Resource Status name<br />
|-<br />
|CREATOR_ID || int (4)|| Resource Creator id<br />
|-<br />
|NATION_ID || int (4)|| Resource Nation id<br />
|-<br />
|NATION || nvarchar (512)|| Nation<br />
|-<br />
|CLIENT_ID || int (4)|| Id of client the resource belongs to<br />
|-<br />
|CLIENT || nvarchar (400)|| Name of client the resource belongs to<br />
|-<br />
|ORGANIZATION_UNIT_ID || int (4)|| Organization Unit id the resource belongs to<br />
|-<br />
|PATH || nvarchar (8000)|| Organization Unit path<br />
|-<br />
|SALEROLE_ID || int (4)|| Sale Role id, this information can drive sales revenue amount<br />
|-<br />
|SALES_ROLE || nvarchar (512)|| Sale Role name<br />
|-<br />
|SUPPLIER_ID || int (4)|| Id of supplier the resource belongs to<br />
|-<br />
|SUPPLIER || nvarchar (400)|| Name of supplier the resource belongs to <br />
|-<br />
|PURCHASEROLE_ID || int (4)|| Purchase Role id, this information can drive Purchase cost amount<br />
|-<br />
|PURCHASE_ROLE || nvarchar (512)|| Purchase Role name<br />
|-<br />
|BIRTH_DAY || datetime (8)|| Resource birth day<br />
|-<br />
|BIRTH_PLACE || nvarchar (400)|| Resource birth Place<br />
|-<br />
|EXTERNALCODE || nvarchar (400)|| Field used to store external resource reference <br />
|-<br />
|RESTYPE_ID || int (4)|| Id of Resource type<br />
|-<br />
|VIP_TYPE || int (4)|| Resource type name<br />
|-<br />
|CANDECLAREHOLIDAY || bit (1)|| Flag that identify if the resource can declare his own holiday<br />
|-<br />
|CANDECLAREILLNESS || bit (1)|| Flag that identify if the resource can declare his own illness <br />
|-<br />
|IS_EDIT_RESOURCE_DATA || bit (1)|| This flag enable the resource to modify his own data<br />
|-<br />
|IS_PERSONAL_VIEW_RIGHT || bit (1)|| This flag enable the resource to define personal view<br />
|-<br />
|CMS_ACCESS || bit (1)|| This flag enable the resource to access the Configuration Management System<br />
|-<br />
|USER_MAPPING_MODE || nvarchar (510)|| <br />
|-<br />
|EXT_CMDB_MODIFY || bit (1)|| <br />
|-<br />
|EXT_CMDB_VIEW || bit (1)|| <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field<br />
|}<br />
<br />
== PROJECT SERVICE VIEW ==<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Project Id<br />
|-<br />
|CODE || int (4)|| Project internal identifier<br />
|-<br />
|MAIN_TYPE_ID || int (4)|| Automatically field by system<br />
|-<br />
|MAIN_TYPE || varchar (7)|| This field can assume Project or Service value<br />
|-<br />
|GANTT_ESTIMATION_MODE || nvarchar (510)|| This field can assume Budget or Forecast value<br />
|-<br />
|NAME || nvarchar (400)|| Project Name<br />
|-<br />
|DESCRIPTION || nvarchar (400)|| Project Description<br />
|-<br />
|OBJECTIVES || nvarchar (1600)|| Project Objectives <br />
|-<br />
|COMMENT || nvarchar (1600)|| Project Comments <br />
|-<br />
|OPER_START_DATE || datetime (8)|| Internal Operational Start Date<br />
|-<br />
|OPER_END_DATE || datetime (8)|| Internal Operational Start End <br />
|-<br />
|EFFECTIVE_START || datetime (8)|| Actual Start Date<br />
|-<br />
|EFFECTIVE_END || datetime (8)|| Actual End Date <br />
|-<br />
|INITIAL_EXPECTED_START || datetime (8)|| Initial expected Start Date <br />
|-<br />
|INITIAL_EXPECTED_END || datetime (8)|| Initial expected Start Date <br />
|-<br />
|CURRENT_EXPECTED_START || datetime (8)|| Current Start Date <br />
|-<br />
|CURRENT_EXPECTED_END || datetime (8)|| Current End Date <br />
|-<br />
|CLIENT_ID || int (4)|| Id of client the resource belongs to<br />
|-<br />
|CLIENT || nvarchar (512)|| Name of client the resource belongs to <br />
|-<br />
|CREATOR_ID || int (4)|| Resource Creator id<br />
|-<br />
|CURRENCY_ID || int (4)|| Currency id<br />
|-<br />
|currency || nvarchar (512)|| Currency<br />
|-<br />
|FINALCLIENT_ID || int (4)|| Second reference on Client id<br />
|-<br />
|FINALCLIENT || nvarchar (400)||Second reference Client Name<br />
|-<br />
|PARENT_PRJ_ID || int (4)|| Parent project id<br />
|-<br />
|PRJADMSTATUS_ID || int (4)|| Project administrative status id<br />
|-<br />
|PROJECT_ADM_STATUS || nvarchar (8000)|| Project administrative<br />
|-<br />
|PRJ_CLASS_ID || int (4)|| Project Class id<br />
|-<br />
|CLASS || nvarchar (400)|| Project Class<br />
|-<br />
|PRJOPSTATUS_ID || int (4)|| Project Operative status id<br />
|-<br />
|PROJECT_STATUS || nvarchar (8000)|| Project Operative <br />
|-<br />
|PRJTYPE_ID || int (4)|| Project Type id<br />
|-<br />
|PROJECT_TYPE || nvarchar (512)|| Project Type <br />
|-<br />
|STATPRJ_ID || int (4)|| Statistical project id<br />
|-<br />
|STATISTICAL || nvarchar (512)|| Statistical project id <br />
|-<br />
|EXTERNAL_CODE || nvarchar (100)|| External reference code<br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field <br />
|}<br />
=== PROJECT SERVICE ACTIVITY VIEW ===<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|id || int (4)|| Project Activity Id<br />
|-<br />
|CODE || int (4)|| Project Activity internal identifier<br />
|-<br />
|ORDERING_NUMBER || int (4)|| Sort order<br />
|-<br />
|TASK_NAME || nvarchar (2048)|| Task name<br />
|-<br />
|DESCRIPTION || nvarchar (1000)|| Task Description<br />
|-<br />
|START_DATE || datetime (8)|| Activity start date <br />
|-<br />
|END_DATE || datetime (8)|| Activity end date <br />
|-<br />
|ACTPRIORITY_ID || int (4)|| Activity priority id<br />
|-<br />
|PRIORITY || nvarchar (512)|| Priority<br />
|-<br />
|ACTSTATUS_ID || int (4)|| Activity status id <br />
|-<br />
|STATUS || nvarchar (512)|| Activity status <br />
|-<br />
|ACTIVITY_TYPE_ID || int (4)|| Activity type id <br />
|-<br />
|ACTIVITY_TYPE || nvarchar (512)|| Activity type <br />
|-<br />
|PRJ_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|DURATION || float (8)|| Estimated duration of task <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationUser || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation date, Automatic field<br />
|}<br />
<br />
== TICKET VIEW ==<br />
This view report some company information. The View's name is: _STD_TICKET_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Project Id<br />
|-<br />
|CODE || int (4)|| Project internal identifier<br />
|-<br />
|TICKETTYPE_ID || int (4)|| Ticket type reference id<br />
|-<br />
|TICKET_TYPE || nvarchar (512)|| Ticket type name<br />
|-<br />
|PROJECT_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|SERVICE_REQUEST_ID || int (4)||Service catalogue request reference id<br />
|-<br />
|SERVICE_REQUEST || nvarchar (1024)|| Service catalogue request reference name<br />
|-<br />
|CURRENT_SERVICE_REQUEST_ID || int (4)|| Current Service catalogue request reference id<br />
|-<br />
|CURRENT_SERVICE_REQUEST || nvarchar (1024)|| Current Service catalogue request reference name <br />
|-<br />
|SHORT_DESCRIPTION || nvarchar (-1)|| Ticket short description<br />
|-<br />
|DESCRIPTION || nvarchar (-1)|| Ticket Description<br />
|-<br />
|ANALYSIS || nvarchar (-1)|| Ticket Analisys description<br />
|-<br />
|SOLUTION || nvarchar (-1)|| Ticket Solution description<br />
|-<br />
|WORKAROUND || nvarchar (-1)|| Ticket Workaound description <br />
|-<br />
|COMMENTS || nvarchar (-1)|| Ticket Comments<br />
|-<br />
|OWNER_ID || int (4)|| Ticket Owner Resource reference <br />
|-<br />
|OWNER || nvarchar (512)||Ticket Owner Resource <br />
|-<br />
|REQUESTER_ID || int (4)|| Ticket Requester reference id<br />
|-<br />
|REQUESTER || nvarchar (802)||Ticket Requester reference<br />
|-<br />
|RESOURCE_ID || int (4)|| Ticket Resource reference id<br />
|-<br />
|RESOURCE || nvarchar (802)||Ticket Resource reference<br />
|-<br />
|REQUIRED_SOLUTION_DATE || datetime (8)|| Ticket required solution date <br />
|-<br />
|FORECAST_SOLUTION_DATE || datetime (8)|| Forecast solution date of ticket<br />
|-<br />
|SOLUTIONGROUP_ID || int (4)|| Group reference id. At each group per workflow is assigned a specific role.<br />
|-<br />
|DSG1 || nvarchar (512)|| Group reference name<br />
|-<br />
|MASTER_SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DSG2 || nvarchar (512)|| Group reference name<br />
|-<br />
|THIRD_SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DSG3 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG4_ID || int (4)|| Group reference id<br />
|-<br />
|DSG4 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG5_ID || int (4)|| Group reference id<br />
|-<br />
|DSG5 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG6_ID || int (4)|| Group reference id<br />
|-<br />
|DSG6 || nvarchar (512)|| Group reference name<br />
|-<br />
|WORKFLOW_ID || int (4)|| Workflow reference id<br />
|-<br />
|WORKFLOW_DESCRIPTION || nvarchar (2048)|| Workflow description<br />
|-<br />
|WORKFLOW_TICKET_ADM_STATUS_ID || int (4)|| Workflow administrarive status id<br />
|-<br />
|WORKFLOW_TICKET_ADM_STATUS || nvarchar (512)|| Workflow administrarive status<br />
|-<br />
|WORKFLOW_TICKET_OP_STATUS_ID || int (4)|| Workflow operative status id<br />
|-<br />
|WORKFLOW_TICKET_OP_STATUS || nvarchar (512)|| Workflow operative status<br />
|-<br />
|RESOLUTION_CAUSE_ID || int (4)|| Ticket resolution cause reference id <br />
|-<br />
RESOLUTION_CAUSE || nvarchar (512)|| Ticket resolution cause reference <br />
|-<br />
|TICKET_CLOSURE_CAUSE_ID || int (4)|| Ticket closure cause reference id<br />
|-<br />
|TICKET_CLOSURE_CAUSE || nvarchar (512)|| Ticket closure cause reference <br />
|-<br />
|REQUESTED_PRIORITY_ID || int (4)|| Ticket requested priority id<br />
|-<br />
|REQUESTED_PRIORITY || nvarchar (512)|| Ticket requested priority <br />
|-<br />
|TARGET_ENVIRONMENT_ID || int (4)|| Target environment reference id <br />
|-<br />
|TARGET_ENVIRONMENT || nvarchar (512)|| Target environment reference <br />
|-<br />
|TICKET_IMPACT_ID || int (4)|| Ticket impact id<br />
|-<br />
|TICKET_IMPACT || nvarchar (512)|| Ticket impact reference <br />
|-<br />
|TICKET_URGENCY_ID || int (4)|| Ticket urgency id<br />
|-<br />
|TICKET_UREGENCY || nvarchar (512)|| Ticket urgency reference <br />
|-<br />
|TICKET_PRIORITY_ID || int (4)|| Ticket priority id, usually this is calculated field value based on Ticket Impact and Urgency<br />
|-<br />
|TICKET_PRIORITY || nvarchar (512)|| Ticket priority reference <br />
|-<br />
|TICKET_ACTIVITY_TEMPLATE_ID || int (4)|| Ticket activity id of template used to load the Ticket activity<br />
|-<br />
|TICKET_ACTIVITY_TEMPLATE || nvarchar (200)||Ticket activity template used to load the Ticket activity <br />
|-<br />
|TUPLE_TICKET_AREA_ID || int (4)|| First level of Standard Tuple. Ticket Area reference id<br />
|-<br />
|TUPLE_TICKET_AREA || nvarchar (512)|| First level of Standard Tuple. Ticket Area reference name<br />
|-<br />
|TUPLE_TICKET_CATEGORY_ID || int (4)|| Second level of Standard Tuple. Ticket Category reference id<br />
|-<br />
|TUPLE_TICKET_CATEGORY || nvarchar (512)|| Second level of Standard Tuple. Ticket Category reference name <br />
|-<br />
|TUPLE_TICKET_TOPIC_ID || int (4)|| Third level of Standard Tuple. Ticket Topic reference id <br />
|-<br />
|TUPLE_TICKET_TOPIC || nvarchar (512)|| Third level of Standard Tuple. Ticket Topic reference name <br />
|-<br />
|ESTIMATION_START || datetime (8)|| Ticket Estimation Start range date <br />
|-<br />
|ESTIMATION_END || datetime (8)|| Ticket Estimation End range date <br />
|-<br />
|ESTIMATION_DATE || datetime (8)|| Ticket Estimation cutoff date <br />
|-<br />
|ESTIMATION_MODE || int (4)|| Ticket Estimation mode<br />
|-<br />
|COST_METHOD || nvarchar (510)|| Ticket cost method, can assume a value Standard or Fixed Cost Only <br />
|-<br />
|ATTACHMENT_PRESENT || bit (1)|| Flag stated at least on document is attached to a ticket <br />
|-<br />
|ACTIVITY_ASSIGN || varchar (21)|| This field can assume a value Activity Not Assigned or Activity Assigned<br />
|-<br />
|TICKET_USER_INFO_ID || int (4)|| Ticket requester information reference id <br />
|-<br />
|CREATION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|CREATION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|CLOSE_DATE || datetime (8)|| Ticket close date<br />
|-<br />
|CLOSE_USER || nvarchar (512)|| Ticket close user <br />
|}<br />
=== TICKET ACTIVITY VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Ticket activity Id<br />
|-<br />
|CODE || int (4)|| Ticket activity internal identifier<br />
|-<br />
|TICKET_ACTIVITY_TYPE_ID || int (4)|| Ticket Activity type reference id <br />
|-<br />
|TICKET_ACTIVITY_TYPE || nvarchar (1600)|| Ticket Activity type reference name<br />
|-<br />
|TICKET_ACTIVITY_SUB_TYPE_ID || int (4)|| Ticket Activity Subtype reference id <br />
|-<br />
|TICKET_ACTIVITY_SUB_TYPE || nvarchar (1000)|| Ticket Activity Subtype reference name<br />
|-<br />
|TICKET_ACTIVITY_STATUS_ID || int (4)||Ticket Activity status reference id <br />
|-<br />
|TICKET_ACTIVITY_STATUS || nvarchar (8000)|| Ticket Activity status reference name<br />
|-<br />
|NAME || nvarchar (512)|| Ticket Activity Name<br />
|-<br />
|DESCRIPTION || nvarchar (-1)|| Ticket Activity Description<br />
|-<br />
|COMMENTS || nvarchar (-1)|| Ticket Activity Comment<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|-<br />
|ASSIGNEE || nvarchar (8000)|| Resource reference name<br />
|-<br />
|SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DURATION || float (8)|| Estimated duration of task <br />
|-<br />
|REQUIRED_START_DATE || datetime (8)|| Ticket required solution start date <br />
|-<br />
|REQUIRED_END_DATE || datetime (8)|| Ticket required solution end+ date <br />
|-<br />
|FORECASTED_START_DATE || datetime (8)|| Forecast solution start date of ticket<br />
|-<br />
|FORECASTED_END_DATE || datetime (8)|| Forecast solution end date of ticket<br />
|-<br />
|EFFECTIVE_START_DATE || datetime (8)|| Actaul solution start date of ticket<br />
|-<br />
|EFFECTIVE_END_DATE || datetime (8)|| Actual solution end date of ticket<br />
|-<br />
|PAID || bit (1)|| If true the recored Timesheet hours are taken in account into the balance column of estimation<br />
|-<br />
|ORDERING_NUMBER || int (4)|| Sort Order<br />
|-<br />
|CREATION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|CREATION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
<br />
|}<br />
=== TICKET CONFIGURATION ITEM VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_CONFIGURATION_ITEM_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Configuration Item Id<br />
|-<br />
|GUID || nvarchar (100)|| Configuration Item GUID<br />
|-<br />
|NAME || nvarchar (510)|| Configuration Item Name<br />
|-<br />
|TYPE || nvarchar (510)|| Configuration Item type<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|}<br />
<br />
=== TICKET CUSTOM FIELD VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_CUSTOM_FIELDS_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Ticket custom field reference Id<br />
|-<br />
|NAME || nvarchar (512)|| Ticket custom field reference Name<br />
|-<br />
|TYPE || nvarchar (8000)|| This field contains the type of the data inserted<br />
|-<br />
|VALUE || nvarchar (-1)|| Ticket custom field value<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|}<br />
=== TICKET ESTIMATION VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_ESTIMATION_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
<br />
<br />
=== TICKET FIELD VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_FIELD_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Field reference Id<br />
|-<br />
|NAME || nvarchar (256)|| Field reference Name<br />
|-<br />
|TICKET_FIELD_TYPE_ID || nvarchar (255)|| This field contains the type of the data inserted. Three possible values can be present <br />
* "PREDEFINED": used to define that the field is a Standard Field<br />
* "CUSTOM": used to define that the field is a Custom Field<br />
* "OBJECTIVE":automatically added by the system when the cusomer declare an Objective<br />
|}<br />
<br />
=== TICKET OCE OBJECTIVE VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_OCE_OBJECTIVE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET RELATED VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_RELATED_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET USER INFO VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_USER_INFO_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET USER NOTE VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_USER_NOTE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET WORKER VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_WORKER_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
== TIMESHEET VIEW ==<br />
This view report some company information. The View's name is: _STD_TIMESHEET_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Timesheet Id<br />
|-<br />
|CODE || int (4)|| Timesheet internal identifier<br />
|-<br />
|PRJ_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|CURRENCY_ID || int (4)|| Currency reference id <br />
|-<br />
|CURRENCY || nvarchar (512)|| Currency reference name<br />
|-<br />
|RESRC_ID || int (4)|| Resource reference id<br />
|-<br />
|RESOURCE || nvarchar (802)|| Resource reference<br />
|-<br />
|GROUP_ID || int (4)|| Group reference id<br />
|-<br />
|GROUP || nvarchar (512)|| Group reference name<br />
|-<br />
|WPLACE_ID || int (4)|| Location reference id <br />
|-<br />
|LOCATION || nvarchar (512)|| Location reference name<br />
|-<br />
|PURCHASE_ROLE_ID || int (4)|| Pruchase Role reference id <br />
|-<br />
|PURCHASE_ROLE || nvarchar (512)|| Pruchase Role reference name<br />
|-<br />
|ACTIVITY_DATE || datetime (8)|| Timesheet activity date<br />
|-<br />
|DURATION || float (8)|| Timesheet duration. This is the duration declared in a resource section<br />
|-<br />
|PM_DURATION || float (8)|| Timesheet duration. This is the duration declared in a PM section<br />
|-<br />
|MANAGER_DURATION || float (8)||Timesheet duration. This is the duration declared in a Manager section <br />
|-<br />
|ACT_DESCRIPTION || nvarchar (2000)||Timesheet Actvity description. This is the duration declared in a resource section<br />
|-<br />
|PM_ACT_DESCRIPTION || nvarchar (2000)|| Timesheet Actvity description. This is the duration declared in a PM section <br />
|-<br />
|MANAGER_ACT_DESCRIPTION || nvarchar (2000)|| Timesheet Actvity description. This is the duration declared in a Manager section <br />
|-<br />
|ACTIVITY_ID || int (4)|| Timesheet Actvity id. This is the id related to a resource section <br />
|-<br />
|PM_ACTIVITY_ID || int (4)|| Timesheet Actvity id. This is the id related to a PM section <br />
|-<br />
|MANAGER_ACTIVITY_ID || int (4)||Timesheet Actvity id. This is the id related to a Manager section <br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|-<br />
|TICKETACTIVITY_ID || int (4)|| Ticket Activity reference id <br />
|-<br />
|TICKETDESCRIPTION || nvarchar (8000)|| Ticket Activity description, copied from Ticket Activity <br />
|-<br />
|TICKETCOMMENTS || nvarchar (8000)|| Ticket Activity Comment<br />
|-<br />
|ROWRPMSTAT_ID || int (4)|| Timesheet Operational status Resource / PM section<br />
|-<br />
|ROWMSTAT_ID || int (4)|| Timesheet Operational status Manager section<br />
|-<br />
|COMMENT || nvarchar (400)|| Comment inserted by resource <br />
|-<br />
|PM_COMMENT || nvarchar (400)|| Comment inserted by PM <br />
|-<br />
|MANAGER_COMMENT || nvarchar (400)|| Comment inserted by Manager <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationUser || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation date, Automatic field<br />
|}<br />
<br />
== TUPLE VIEW ==<br />
This view report some company information. The View's name is: _STD_TUPLE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int|| Tuple Identifier<br />
|-<br />
|CODE || int|| Tuple Identifier<br />
|-<br />
|COMPANY_ID || int|| Company Identifier<br />
|-<br />
|TUPLE_NAME || varchar(256)|| Tupla Name<br />
|-<br />
|TUPLE_AREA_ID || int|| First level of Tuple, Area, Identifier<br />
|-<br />
|TUPLE_AREA || varchar(256)|| Tuple Area Name<br />
|-<br />
|TUPLE_CATEGORY_ID || int|| Second level of Tuple, Category, Identifier<br />
|-<br />
|TUPLE_CATEGORY || varchar(256)|| Tuple Category Name<br />
|-<br />
|TUPLE_TOPIC_ID || int|| Third level of Tuple, Topic, Identifier<br />
|-<br />
|TUPLE_TOPIC || varchar(256)|| Tuple Topic Name<br />
|}<br />
<br />
== SERVICE CATALOGUE REQUEST (SRCS) VIEW ==<br />
This view report some company information. The View's name is: _STD_SRCS_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|CATALOGO || nvarchar (2048)|| Identify a complete set of service catalogue requests <br />
|-<br />
|SECTION || nvarchar (512)|| Sub session of catalogue of requests <br />
|-<br />
|TOPIC_1 || nvarchar (1024)|| Level 1 of nested level of section <br />
|-<br />
|TOPIC_2 || nvarchar (1024)|| Level 2 of nested level of section <br />
|-<br />
|TOPIC_3 || nvarchar (1024)|| Level 3 of nested level of section <br />
|-<br />
|ID || int (4)|| Service request catalogue Id<br />
|-<br />
|SERVICE_REQUEST || nvarchar (1024)|| Service catalogue request reference name<br />
|-<br />
|ENABLED || bit (1)|| Flag stated if the SRCS request is enabled <br />
|-<br />
|PROJECT_ID || int (4)|| Project reference id<br />
|-<br />
|TICKET_TYPE_ID || int (4)|| Ticket type reference id <br />
|-<br />
|TRANSITION_RULE_ID || int (4)|| Transition rule activated when a new ticket is created<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|TICKET_TYPE || nvarchar (512)|| Ticket type reference name <br />
|-<br />
|TRANSITION_RULE || nvarchar (512)|| Transition rule name<br />
|-<br />
|TATPL_ID|| int || Ticket Activity Template id<br />
|-<br />
|TA_TEMPLATE|| nvarchar (100)|| Ticket Activity Template name<br />
|-<br />
|SOLUTIONGROUP || nvarchar (-1)|| Group reference name<br />
|-<br />
|MASTER_SOLUTIONGROUP || nvarchar (-1)|| Group reference name<br />
|-<br />
|OWNER || nvarchar (-1)|| Owner reference name<br />
|-<br />
|TAB_RESOURCES || nvarchar (-1)|| Tab of SRCS session used to grant a request to Resources<br />
|-<br />
|TAB_SOLUTIONGROUP || nvarchar (-1)|| Tab of SRCS session used to grant a request to Groups<br />
|-<br />
|TAB_ORGANIZATIONUNIT || nvarchar (-1)|| Tab of SRCS session used to grant a request to Organization Unit<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=BIRT_View&diff=4019BIRT View2018-10-30T14:17:25Z<p>Francesco.bertuletti: /* SERVICE CATALOGUE REQUEST (SRCS) VIEW */</p>
<hr />
<div>itmSUITE® propose to a customer a set of Standard view to facilitate the reporting development.<br />
The paragraphs below report the standard view collection and explains the relation between data’s<br />
<br />
== COMPANY VIEW ==<br />
This view report some company information. The View's name is: _STD_COMPANY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Company Id<br />
|-<br />
|NAME || nvarchar (400)|| Name of the company<br />
|-<br />
|DESCRIPTION || nvarchar (400)|| Description of the company<br />
|-<br />
|STATUS || nvarchar (510)|| Company Status<br />
|-<br />
|APPLICATION_URL || nvarchar (512)|| Applicaiton url, use to set a detail link information in notification<br />
|-<br />
|CONTACTS || nvarchar (400)|| Email of Application referent<br />
|-<br />
|TIMEZONE || nvarchar (64)|| Company Time Zone<br />
|-<br />
|DURATION_FORMAT || nvarchar (510)|| Unit of measure of Timesheet declaration<br />
|-<br />
|LABOURUNIT_ID || int (4)|| id of Labor<br />
|-<br />
|LABOUR_UNIT || nvarchar (8000)|| Unit of Measure of Labor. This is the unit of measure use in Budget estimation<br />
|}<br />
<br />
== CLIENT VIEW ==<br />
This view report some company information. The View's name is: _STD_CLIENT_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|- <br />
|ID || int (4)|| Client Id<br />
|-<br />
|CODE || int (4)|| Company internal identifier<br />
|-<br />
|NAME || nvarchar (400)|| Client Name<br />
|-<br />
|PARENT_ID || int (4)|| Parent Client id<br />
|-<br />
|CLSTATUS_ID || int (4)|| Status id<br />
|-<br />
|CLIENT_STATUS || nvarchar (8000)|| Status name<br />
|-<br />
|CLTYPE_ID || int (4)|| Id of client type <br />
|-<br />
|CLIENT_TYPE || nvarchar (512)|| Client Type<br />
|-<br />
|CREATOR_ID || int (4)|| Client Creator id <br />
|-<br />
|NATION_ID || int (4)|| Country id<br />
|-<br />
|NATION || nvarchar (512)|| Country Name<br />
|-<br />
|LANGUAGE_ID || int (4)|| Language Id<br />
|-<br />
|LANGUAGE || nvarchar (512)|| Language Name<br />
|-<br />
|PAYMENTTERM_ID || int (4)|| Payment terms id<br />
|-<br />
|PAYMENTTERM || nvarchar (512)|| Payment terms<br />
|-<br />
|REMARK || nvarchar (400)|| REMARKs<br />
|-<br />
|TAX_NUMBER || nvarchar (100)|| Vat number<br />
|-<br />
|AII || bit (1)|| Flag stated that All Invoice has been Issued <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field<br />
|}<br />
<br />
== CLIENT ORGANIZATION UNIT VIEW ==<br />
This view report some company information. The View's name is: _STD_CLIENT_ORGANIZATION_UNIT_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Organization Unit Id<br />
|-<br />
|CODE || int (4)|| Organization Unit internal identifier<br />
|-<br />
|NAME || nvarchar (512)|| Organization Unit name<br />
|-<br />
|STATUS || nvarchar (510)|| Organization Unit status<br />
|-<br />
|CLIENT_ID || int (4)|| Reference to client the Organization Unit belongs to<br />
|-<br />
|PARENT_ID || int (4)|| Reference to father Organization Unit <br />
|-<br />
|PATH || nvarchar (8000)|| Chain of Organization Unit <br />
|-<br />
|CUSTOM_FIELD_1 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_2 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|CUSTOM_FIELD_3 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_4 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_5 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|CUSTOM_FIELD_6 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|ADDRESS || nvarchar (400)|| Organization Unit Address<br />
|-<br />
|POSTAL_CODE || nvarchar (200)|| Organization Unit Postal Code<br />
|-<br />
|CITY || nvarchar (200)|| Organization Unit City<br />
|-<br />
|REGION || nvarchar (200)|| Organization Unit Region<br />
|-<br />
|NATION || nvarchar (512)|| Organization Unit Nation<br />
|-<br />
|PHONE || nvarchar (200)|| Organization Unit Phone number<br />
|-<br />
|FAX || nvarchar (200)|| Organization Unit Fax number<br />
|-<br />
|MAIL || nvarchar (200)|| Organization Unit Email address<br />
|-<br />
|REMARK || nvarchar (400)|| Organization Unit Address remark<br />
|}<br />
<br />
== RESOURCE VIEW ==<br />
This view report some company information. The View's name is: _STD_RESOURCE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Resource Id<br />
|-<br />
|CODE || int (4)|| Resource internal identifier<br />
|-<br />
|LOGIN || nvarchar (400)|| Resource login<br />
|-<br />
|NAME || nvarchar (400)|| Resource name<br />
|-<br />
|SURNAME || nvarchar (400)|| Resource surname<br />
|-<br />
|FULLNAME || nvarchar (802)|| Resource surname + name<br />
|-<br />
|RESOURCE_STATUS_ID || int (4)|| Resource Status id<br />
|-<br />
|RESOURCE_STATUS || nvarchar (512)|| Resource Status name<br />
|-<br />
|CREATOR_ID || int (4)|| Resource Creator id<br />
|-<br />
|NATION_ID || int (4)|| Resource Nation id<br />
|-<br />
|NATION || nvarchar (512)|| Nation<br />
|-<br />
|CLIENT_ID || int (4)|| Id of client the resource belongs to<br />
|-<br />
|CLIENT || nvarchar (400)|| Name of client the resource belongs to<br />
|-<br />
|ORGANIZATION_UNIT_ID || int (4)|| Organization Unit id the resource belongs to<br />
|-<br />
|PATH || nvarchar (8000)|| Organization Unit path<br />
|-<br />
|SALEROLE_ID || int (4)|| Sale Role id, this information can drive sales revenue amount<br />
|-<br />
|SALES_ROLE || nvarchar (512)|| Sale Role name<br />
|-<br />
|SUPPLIER_ID || int (4)|| Id of supplier the resource belongs to<br />
|-<br />
|SUPPLIER || nvarchar (400)|| Name of supplier the resource belongs to <br />
|-<br />
|PURCHASEROLE_ID || int (4)|| Purchase Role id, this information can drive Purchase cost amount<br />
|-<br />
|PURCHASE_ROLE || nvarchar (512)|| Purchase Role name<br />
|-<br />
|BIRTH_DAY || datetime (8)|| Resource birth day<br />
|-<br />
|BIRTH_PLACE || nvarchar (400)|| Resource birth Place<br />
|-<br />
|EXTERNALCODE || nvarchar (400)|| Field used to store external resource reference <br />
|-<br />
|RESTYPE_ID || int (4)|| Id of Resource type<br />
|-<br />
|VIP_TYPE || int (4)|| Resource type name<br />
|-<br />
|CANDECLAREHOLIDAY || bit (1)|| Flag that identify if the resource can declare his own holiday<br />
|-<br />
|CANDECLAREILLNESS || bit (1)|| Flag that identify if the resource can declare his own illness <br />
|-<br />
|IS_EDIT_RESOURCE_DATA || bit (1)|| This flag enable the resource to modify his own data<br />
|-<br />
|IS_PERSONAL_VIEW_RIGHT || bit (1)|| This flag enable the resource to define personal view<br />
|-<br />
|CMS_ACCESS || bit (1)|| This flag enable the resource to access the Configuration Management System<br />
|-<br />
|USER_MAPPING_MODE || nvarchar (510)|| <br />
|-<br />
|EXT_CMDB_MODIFY || bit (1)|| <br />
|-<br />
|EXT_CMDB_VIEW || bit (1)|| <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field<br />
|}<br />
<br />
== PROJECT SERVICE VIEW ==<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Project Id<br />
|-<br />
|CODE || int (4)|| Project internal identifier<br />
|-<br />
|MAIN_TYPE_ID || int (4)|| Automatically field by system<br />
|-<br />
|MAIN_TYPE || varchar (7)|| This field can assume Project or Service value<br />
|-<br />
|GANTT_ESTIMATION_MODE || nvarchar (510)|| This field can assume Budget or Forecast value<br />
|-<br />
|NAME || nvarchar (400)|| Project Name<br />
|-<br />
|DESCRIPTION || nvarchar (400)|| Project Description<br />
|-<br />
|OBJECTIVES || nvarchar (1600)|| Project Objectives <br />
|-<br />
|COMMENT || nvarchar (1600)|| Project Comments <br />
|-<br />
|OPER_START_DATE || datetime (8)|| Internal Operational Start Date<br />
|-<br />
|OPER_END_DATE || datetime (8)|| Internal Operational Start End <br />
|-<br />
|EFFECTIVE_START || datetime (8)|| Actual Start Date<br />
|-<br />
|EFFECTIVE_END || datetime (8)|| Actual End Date <br />
|-<br />
|INITIAL_EXPECTED_START || datetime (8)|| Initial expected Start Date <br />
|-<br />
|INITIAL_EXPECTED_END || datetime (8)|| Initial expected Start Date <br />
|-<br />
|CURRENT_EXPECTED_START || datetime (8)|| Current Start Date <br />
|-<br />
|CURRENT_EXPECTED_END || datetime (8)|| Current End Date <br />
|-<br />
|CLIENT_ID || int (4)|| Id of client the resource belongs to<br />
|-<br />
|CLIENT || nvarchar (512)|| Name of client the resource belongs to <br />
|-<br />
|CREATOR_ID || int (4)|| Resource Creator id<br />
|-<br />
|CURRENCY_ID || int (4)|| Currency id<br />
|-<br />
|currency || nvarchar (512)|| Currency<br />
|-<br />
|FINALCLIENT_ID || int (4)|| Second reference on Client id<br />
|-<br />
|FINALCLIENT || nvarchar (400)||Second reference Client Name<br />
|-<br />
|PARENT_PRJ_ID || int (4)|| Parent project id<br />
|-<br />
|PRJADMSTATUS_ID || int (4)|| Project administrative status id<br />
|-<br />
|PROJECT_ADM_STATUS || nvarchar (8000)|| Project administrative<br />
|-<br />
|PRJ_CLASS_ID || int (4)|| Project Class id<br />
|-<br />
|CLASS || nvarchar (400)|| Project Class<br />
|-<br />
|PRJOPSTATUS_ID || int (4)|| Project Operative status id<br />
|-<br />
|PROJECT_STATUS || nvarchar (8000)|| Project Operative <br />
|-<br />
|PRJTYPE_ID || int (4)|| Project Type id<br />
|-<br />
|PROJECT_TYPE || nvarchar (512)|| Project Type <br />
|-<br />
|STATPRJ_ID || int (4)|| Statistical project id<br />
|-<br />
|STATISTICAL || nvarchar (512)|| Statistical project id <br />
|-<br />
|EXTERNAL_CODE || nvarchar (100)|| External reference code<br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field <br />
|}<br />
=== PROJECT SERVICE ACTIVITY VIEW ===<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|id || int (4)|| Project Activity Id<br />
|-<br />
|CODE || int (4)|| Project Activity internal identifier<br />
|-<br />
|ORDERING_NUMBER || int (4)|| Sort order<br />
|-<br />
|TASK_NAME || nvarchar (2048)|| Task name<br />
|-<br />
|DESCRIPTION || nvarchar (1000)|| Task Description<br />
|-<br />
|START_DATE || datetime (8)|| Activity start date <br />
|-<br />
|END_DATE || datetime (8)|| Activity end date <br />
|-<br />
|ACTPRIORITY_ID || int (4)|| Activity priority id<br />
|-<br />
|PRIORITY || nvarchar (512)|| Priority<br />
|-<br />
|ACTSTATUS_ID || int (4)|| Activity status id <br />
|-<br />
|STATUS || nvarchar (512)|| Activity status <br />
|-<br />
|ACTIVITY_TYPE_ID || int (4)|| Activity type id <br />
|-<br />
|ACTIVITY_TYPE || nvarchar (512)|| Activity type <br />
|-<br />
|PRJ_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|DURATION || float (8)|| Estimated duration of task <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationUser || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation date, Automatic field<br />
|}<br />
<br />
== TICKET VIEW ==<br />
This view report some company information. The View's name is: _STD_TICKET_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Project Id<br />
|-<br />
|CODE || int (4)|| Project internal identifier<br />
|-<br />
|TICKETTYPE_ID || int (4)|| Ticket type reference id<br />
|-<br />
|TICKET_TYPE || nvarchar (512)|| Ticket type name<br />
|-<br />
|PROJECT_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|SERVICE_REQUEST_ID || int (4)||Service catalogue request reference id<br />
|-<br />
|SERVICE_REQUEST || nvarchar (1024)|| Service catalogue request reference name<br />
|-<br />
|CURRENT_SERVICE_REQUEST_ID || int (4)|| Current Service catalogue request reference id<br />
|-<br />
|CURRENT_SERVICE_REQUEST || nvarchar (1024)|| Current Service catalogue request reference name <br />
|-<br />
|SHORT_DESCRIPTION || nvarchar (-1)|| Ticket short description<br />
|-<br />
|DESCRIPTION || nvarchar (-1)|| Ticket Description<br />
|-<br />
|ANALYSIS || nvarchar (-1)|| Ticket Analisys description<br />
|-<br />
|SOLUTION || nvarchar (-1)|| Ticket Solution description<br />
|-<br />
|WORKAROUND || nvarchar (-1)|| Ticket Workaound description <br />
|-<br />
|COMMENTS || nvarchar (-1)|| Ticket Comments<br />
|-<br />
|OWNER_ID || int (4)|| Ticket Owner Resource reference <br />
|-<br />
|OWNER || nvarchar (512)||Ticket Owner Resource <br />
|-<br />
|REQUESTER_ID || int (4)|| Ticket Requester reference id<br />
|-<br />
|REQUESTER || nvarchar (802)||Ticket Requester reference<br />
|-<br />
|RESOURCE_ID || int (4)|| Ticket Resource reference id<br />
|-<br />
|RESOURCE || nvarchar (802)||Ticket Resource reference<br />
|-<br />
|REQUIRED_SOLUTION_DATE || datetime (8)|| Ticket required solution date <br />
|-<br />
|FORECAST_SOLUTION_DATE || datetime (8)|| Forecast solution date of ticket<br />
|-<br />
|SOLUTIONGROUP_ID || int (4)|| Group reference id. At each group per workflow is assigned a specific role.<br />
|-<br />
|DSG1 || nvarchar (512)|| Group reference name<br />
|-<br />
|MASTER_SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DSG2 || nvarchar (512)|| Group reference name<br />
|-<br />
|THIRD_SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DSG3 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG4_ID || int (4)|| Group reference id<br />
|-<br />
|DSG4 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG5_ID || int (4)|| Group reference id<br />
|-<br />
|DSG5 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG6_ID || int (4)|| Group reference id<br />
|-<br />
|DSG6 || nvarchar (512)|| Group reference name<br />
|-<br />
|WORKFLOW_ID || int (4)|| Workflow reference id<br />
|-<br />
|WORKFLOW_DESCRIPTION || nvarchar (2048)|| Workflow description<br />
|-<br />
|WORKFLOW_TICKET_ADM_STATUS_ID || int (4)|| Workflow administrarive status id<br />
|-<br />
|WORKFLOW_TICKET_ADM_STATUS || nvarchar (512)|| Workflow administrarive status<br />
|-<br />
|WORKFLOW_TICKET_OP_STATUS_ID || int (4)|| Workflow operative status id<br />
|-<br />
|WORKFLOW_TICKET_OP_STATUS || nvarchar (512)|| Workflow operative status<br />
|-<br />
|RESOLUTION_CAUSE_ID || int (4)|| Ticket resolution cause reference id <br />
|-<br />
RESOLUTION_CAUSE || nvarchar (512)|| Ticket resolution cause reference <br />
|-<br />
|TICKET_CLOSURE_CAUSE_ID || int (4)|| Ticket closure cause reference id<br />
|-<br />
|TICKET_CLOSURE_CAUSE || nvarchar (512)|| Ticket closure cause reference <br />
|-<br />
|REQUESTED_PRIORITY_ID || int (4)|| Ticket requested priority id<br />
|-<br />
|REQUESTED_PRIORITY || nvarchar (512)|| Ticket requested priority <br />
|-<br />
|TARGET_ENVIRONMENT_ID || int (4)|| Target environment reference id <br />
|-<br />
|TARGET_ENVIRONMENT || nvarchar (512)|| Target environment reference <br />
|-<br />
|TICKET_IMPACT_ID || int (4)|| Ticket impact id<br />
|-<br />
|TICKET_IMPACT || nvarchar (512)|| Ticket impact reference <br />
|-<br />
|TICKET_URGENCY_ID || int (4)|| Ticket urgency id<br />
|-<br />
|TICKET_UREGENCY || nvarchar (512)|| Ticket urgency reference <br />
|-<br />
|TICKET_PRIORITY_ID || int (4)|| Ticket priority id, usually this is calculated field value based on Ticket Impact and Urgency<br />
|-<br />
|TICKET_PRIORITY || nvarchar (512)|| Ticket priority reference <br />
|-<br />
|TICKET_ACTIVITY_TEMPLATE_ID || int (4)|| Ticket activity id of template used to load the Ticket activity<br />
|-<br />
|TICKET_ACTIVITY_TEMPLATE || nvarchar (200)||Ticket activity template used to load the Ticket activity <br />
|-<br />
|TUPLE_TICKET_AREA_ID || int (4)|| First level of Standard Tuple. Ticket Area reference id<br />
|-<br />
|TUPLE_TICKET_AREA || nvarchar (512)|| First level of Standard Tuple. Ticket Area reference name<br />
|-<br />
|TUPLE_TICKET_CATEGORY_ID || int (4)|| Second level of Standard Tuple. Ticket Category reference id<br />
|-<br />
|TUPLE_TICKET_CATEGORY || nvarchar (512)|| Second level of Standard Tuple. Ticket Category reference name <br />
|-<br />
|TUPLE_TICKET_TOPIC_ID || int (4)|| Third level of Standard Tuple. Ticket Topic reference id <br />
|-<br />
|TUPLE_TICKET_TOPIC || nvarchar (512)|| Third level of Standard Tuple. Ticket Topic reference name <br />
|-<br />
|ESTIMATION_START || datetime (8)|| Ticket Estimation Start range date <br />
|-<br />
|ESTIMATION_END || datetime (8)|| Ticket Estimation End range date <br />
|-<br />
|ESTIMATION_DATE || datetime (8)|| Ticket Estimation cutoff date <br />
|-<br />
|ESTIMATION_MODE || int (4)|| Ticket Estimation mode<br />
|-<br />
|COST_METHOD || nvarchar (510)|| Ticket cost method, can assume a value Standard or Fixed Cost Only <br />
|-<br />
|ATTACHMENT_PRESENT || bit (1)|| Flag stated at least on document is attached to a ticket <br />
|-<br />
|ACTIVITY_ASSIGN || varchar (21)|| This field can assume a value Activity Not Assigned or Activity Assigned<br />
|-<br />
|TICKET_USER_INFO_ID || int (4)|| Ticket requester information reference id <br />
|-<br />
|CREATION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|CREATION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|CLOSE_DATE || datetime (8)|| Ticket close date<br />
|-<br />
|CLOSE_USER || nvarchar (512)|| Ticket close user <br />
|}<br />
=== TICKET ACTIVITY VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Ticket activity Id<br />
|-<br />
|CODE || int (4)|| Ticket activity internal identifier<br />
|-<br />
|TICKET_ACTIVITY_TYPE_ID || int (4)|| Ticket Activity type reference id <br />
|-<br />
|TICKET_ACTIVITY_TYPE || nvarchar (1600)|| Ticket Activity type reference name<br />
|-<br />
|TICKET_ACTIVITY_SUB_TYPE_ID || int (4)|| Ticket Activity Subtype reference id <br />
|-<br />
|TICKET_ACTIVITY_SUB_TYPE || nvarchar (1000)|| Ticket Activity Subtype reference name<br />
|-<br />
|TICKET_ACTIVITY_STATUS_ID || int (4)||Ticket Activity status reference id <br />
|-<br />
|TICKET_ACTIVITY_STATUS || nvarchar (8000)|| Ticket Activity status reference name<br />
|-<br />
|NAME || nvarchar (512)|| Ticket Activity Name<br />
|-<br />
|DESCRIPTION || nvarchar (-1)|| Ticket Activity Description<br />
|-<br />
|COMMENTS || nvarchar (-1)|| Ticket Activity Comment<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|-<br />
|ASSIGNEE || nvarchar (8000)|| Resource reference name<br />
|-<br />
|SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DURATION || float (8)|| Estimated duration of task <br />
|-<br />
|REQUIRED_START_DATE || datetime (8)|| Ticket required solution start date <br />
|-<br />
|REQUIRED_END_DATE || datetime (8)|| Ticket required solution end+ date <br />
|-<br />
|FORECASTED_START_DATE || datetime (8)|| Forecast solution start date of ticket<br />
|-<br />
|FORECASTED_END_DATE || datetime (8)|| Forecast solution end date of ticket<br />
|-<br />
|EFFECTIVE_START_DATE || datetime (8)|| Actaul solution start date of ticket<br />
|-<br />
|EFFECTIVE_END_DATE || datetime (8)|| Actual solution end date of ticket<br />
|-<br />
|PAID || bit (1)|| If true the recored Timesheet hours are taken in account into the balance column of estimation<br />
|-<br />
|ORDERING_NUMBER || int (4)|| Sort Order<br />
|-<br />
|CREATION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|CREATION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
<br />
|}<br />
=== TICKET CONFIGURATION ITEM VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_CONFIGURATION_ITEM_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Configuration Item Id<br />
|-<br />
|GUID || nvarchar (100)|| Configuration Item GUID<br />
|-<br />
|NAME || nvarchar (510)|| Configuration Item Name<br />
|-<br />
|TYPE || nvarchar (510)|| Configuration Item type<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|}<br />
<br />
=== TICKET CUSTOM FIELD VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_CUSTOM_FIELDS_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Ticket custom field reference Id<br />
|-<br />
|NAME || nvarchar (512)|| Ticket custom field reference Name<br />
|-<br />
|TYPE || nvarchar (8000)|| This field contains the type of the data inserted<br />
|-<br />
|VALUE || nvarchar (-1)|| Ticket custom field value<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|}<br />
=== TICKET ESTIMATION VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_ESTIMATION_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
<br />
<br />
=== TICKET FIELD VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_FIELD_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Field reference Id<br />
|-<br />
|NAME || nvarchar (256)|| Field reference Name<br />
|-<br />
|TICKET_FIELD_TYPE_ID || nvarchar (255)|| This field contains the type of the data inserted. Three possible values can be present <br />
* "PREDEFINED": used to define that the field is a Standard Field<br />
* "CUSTOM": used to define that the field is a Custom Field<br />
* "OBJECTIVE":automatically added by the system when the cusomer declare an Objective<br />
|}<br />
<br />
=== TICKET OCE OBJECTIVE VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_OCE_OBJECTIVE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET RELATED VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_RELATED_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET USER INFO VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_USER_INFO_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET USER NOTE VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_USER_NOTE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET WORKER VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_WORKER_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
== TIMESHEET VIEW ==<br />
This view report some company information. The View's name is: _STD_TIMESHEET_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Timesheet Id<br />
|-<br />
|CODE || int (4)|| Timesheet internal identifier<br />
|-<br />
|PRJ_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|CURRENCY_ID || int (4)|| Currency reference id <br />
|-<br />
|CURRENCY || nvarchar (512)|| Currency reference name<br />
|-<br />
|RESRC_ID || int (4)|| Resource reference id<br />
|-<br />
|RESOURCE || nvarchar (802)|| Resource reference<br />
|-<br />
|GROUP_ID || int (4)|| Group reference id<br />
|-<br />
|GROUP || nvarchar (512)|| Group reference name<br />
|-<br />
|WPLACE_ID || int (4)|| Location reference id <br />
|-<br />
|LOCATION || nvarchar (512)|| Location reference name<br />
|-<br />
|PURCHASE_ROLE_ID || int (4)|| Pruchase Role reference id <br />
|-<br />
|PURCHASE_ROLE || nvarchar (512)|| Pruchase Role reference name<br />
|-<br />
|ACTIVITY_DATE || datetime (8)|| Timesheet activity date<br />
|-<br />
|DURATION || float (8)|| Timesheet duration. This is the duration declared in a resource section<br />
|-<br />
|PM_DURATION || float (8)|| Timesheet duration. This is the duration declared in a PM section<br />
|-<br />
|MANAGER_DURATION || float (8)||Timesheet duration. This is the duration declared in a Manager section <br />
|-<br />
|ACT_DESCRIPTION || nvarchar (2000)||Timesheet Actvity description. This is the duration declared in a resource section<br />
|-<br />
|PM_ACT_DESCRIPTION || nvarchar (2000)|| Timesheet Actvity description. This is the duration declared in a PM section <br />
|-<br />
|MANAGER_ACT_DESCRIPTION || nvarchar (2000)|| Timesheet Actvity description. This is the duration declared in a Manager section <br />
|-<br />
|ACTIVITY_ID || int (4)|| Timesheet Actvity id. This is the id related to a resource section <br />
|-<br />
|PM_ACTIVITY_ID || int (4)|| Timesheet Actvity id. This is the id related to a PM section <br />
|-<br />
|MANAGER_ACTIVITY_ID || int (4)||Timesheet Actvity id. This is the id related to a Manager section <br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|-<br />
|TICKETACTIVITY_ID || int (4)|| Ticket Activity reference id <br />
|-<br />
|TICKETDESCRIPTION || nvarchar (8000)|| Ticket Activity description, copied from Ticket Activity <br />
|-<br />
|TICKETCOMMENTS || nvarchar (8000)|| Ticket Activity Comment<br />
|-<br />
|ROWRPMSTAT_ID || int (4)|| Timesheet Operational status Resource / PM section<br />
|-<br />
|ROWMSTAT_ID || int (4)|| Timesheet Operational status Manager section<br />
|-<br />
|COMMENT || nvarchar (400)|| Comment inserted by resource <br />
|-<br />
|PM_COMMENT || nvarchar (400)|| Comment inserted by PM <br />
|-<br />
|MANAGER_COMMENT || nvarchar (400)|| Comment inserted by Manager <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationUser || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation date, Automatic field<br />
|}<br />
<br />
== TUPLE VIEW ==<br />
This view report some company information. The View's name is: _STD_TUPLE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int|| Tuple Identifier<br />
|-<br />
|CODE || int|| Tuple Identifier<br />
|-<br />
|COMPANY_ID || int|| Company Identifier<br />
|-<br />
|TUPLE_NAME || varchar(256)|| Tupla Name<br />
|-<br />
|TUPLE_AREA_ID || int|| First level of Tuple, Area, Identifier<br />
|-<br />
|TUPLE_AREA || varchar(256)|| Tuple Area Name<br />
|-<br />
|TUPLE_CATEGORY_ID || int|| Second level of Tuple, Category, Identifier<br />
|-<br />
|TUPLE_CATEGORY || varchar(256)|| Tuple Category Name<br />
|-<br />
|TUPLE_TOPIC_ID || int|| Third level of Tuple, Topic, Identifier<br />
|-<br />
|TUPLE_TOPIC || varchar(256)|| Tuple Topic Name<br />
|}<br />
<br />
== SERVICE CATALOGUE REQUEST (SRCS) VIEW ==<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|CATALOGO || nvarchar (2048)|| Identify a complete set of service catalogue requests <br />
|-<br />
|SECTION || nvarchar (512)|| Sub session of catalogue of requests <br />
|-<br />
|TOPIC_1 || nvarchar (1024)|| Level 1 of nested level of section <br />
|-<br />
|TOPIC_2 || nvarchar (1024)|| Level 2 of nested level of section <br />
|-<br />
|TOPIC_3 || nvarchar (1024)|| Level 3 of nested level of section <br />
|-<br />
|ID || int (4)|| Service request catalogue Id<br />
|-<br />
|SERVICE_REQUEST || nvarchar (1024)|| Service catalogue request reference name<br />
|-<br />
|ENABLED || bit (1)|| Flag stated if the SRCS request is enabled <br />
|-<br />
|PROJECT_ID || int (4)|| Project reference id<br />
|-<br />
|TICKET_TYPE_ID || int (4)|| Ticket type reference id <br />
|-<br />
|TRANSITION_RULE_ID || int (4)|| Transition rule activated when a new ticket is created<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|TICKET_TYPE || nvarchar (512)|| Ticket type reference name <br />
|-<br />
|TRANSITION_RULE || nvarchar (512)|| Transition rule name<br />
|-<br />
|TATPL_ID|| int || Ticket Activity Template id<br />
|-<br />
|TA_TEMPLATE|| nvarchar (100)|| Ticket Activity Template name<br />
|-<br />
|SOLUTIONGROUP || nvarchar (-1)|| Group reference name<br />
|-<br />
|MASTER_SOLUTIONGROUP || nvarchar (-1)|| Group reference name<br />
|-<br />
|OWNER || nvarchar (-1)|| Owner reference name<br />
|-<br />
|TAB_RESOURCES || nvarchar (-1)|| Tab of SRCS session used to grant a request to Resources<br />
|-<br />
|TAB_SOLUTIONGROUP || nvarchar (-1)|| Tab of SRCS session used to grant a request to Groups<br />
|-<br />
|TAB_ORGANIZATIONUNIT || nvarchar (-1)|| Tab of SRCS session used to grant a request to Organization Unit<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=BIRT_View&diff=4018BIRT View2018-10-30T14:16:36Z<p>Francesco.bertuletti: /* SERVICE CATALOGUE REQUEST (SRCS)VIEW */</p>
<hr />
<div>itmSUITE® propose to a customer a set of Standard view to facilitate the reporting development.<br />
The paragraphs below report the standard view collection and explains the relation between data’s<br />
<br />
== COMPANY VIEW ==<br />
This view report some company information. The View's name is: _STD_COMPANY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Company Id<br />
|-<br />
|NAME || nvarchar (400)|| Name of the company<br />
|-<br />
|DESCRIPTION || nvarchar (400)|| Description of the company<br />
|-<br />
|STATUS || nvarchar (510)|| Company Status<br />
|-<br />
|APPLICATION_URL || nvarchar (512)|| Applicaiton url, use to set a detail link information in notification<br />
|-<br />
|CONTACTS || nvarchar (400)|| Email of Application referent<br />
|-<br />
|TIMEZONE || nvarchar (64)|| Company Time Zone<br />
|-<br />
|DURATION_FORMAT || nvarchar (510)|| Unit of measure of Timesheet declaration<br />
|-<br />
|LABOURUNIT_ID || int (4)|| id of Labor<br />
|-<br />
|LABOUR_UNIT || nvarchar (8000)|| Unit of Measure of Labor. This is the unit of measure use in Budget estimation<br />
|}<br />
<br />
== CLIENT VIEW ==<br />
This view report some company information. The View's name is: _STD_CLIENT_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|- <br />
|ID || int (4)|| Client Id<br />
|-<br />
|CODE || int (4)|| Company internal identifier<br />
|-<br />
|NAME || nvarchar (400)|| Client Name<br />
|-<br />
|PARENT_ID || int (4)|| Parent Client id<br />
|-<br />
|CLSTATUS_ID || int (4)|| Status id<br />
|-<br />
|CLIENT_STATUS || nvarchar (8000)|| Status name<br />
|-<br />
|CLTYPE_ID || int (4)|| Id of client type <br />
|-<br />
|CLIENT_TYPE || nvarchar (512)|| Client Type<br />
|-<br />
|CREATOR_ID || int (4)|| Client Creator id <br />
|-<br />
|NATION_ID || int (4)|| Country id<br />
|-<br />
|NATION || nvarchar (512)|| Country Name<br />
|-<br />
|LANGUAGE_ID || int (4)|| Language Id<br />
|-<br />
|LANGUAGE || nvarchar (512)|| Language Name<br />
|-<br />
|PAYMENTTERM_ID || int (4)|| Payment terms id<br />
|-<br />
|PAYMENTTERM || nvarchar (512)|| Payment terms<br />
|-<br />
|REMARK || nvarchar (400)|| REMARKs<br />
|-<br />
|TAX_NUMBER || nvarchar (100)|| Vat number<br />
|-<br />
|AII || bit (1)|| Flag stated that All Invoice has been Issued <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field<br />
|}<br />
<br />
== CLIENT ORGANIZATION UNIT VIEW ==<br />
This view report some company information. The View's name is: _STD_CLIENT_ORGANIZATION_UNIT_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Organization Unit Id<br />
|-<br />
|CODE || int (4)|| Organization Unit internal identifier<br />
|-<br />
|NAME || nvarchar (512)|| Organization Unit name<br />
|-<br />
|STATUS || nvarchar (510)|| Organization Unit status<br />
|-<br />
|CLIENT_ID || int (4)|| Reference to client the Organization Unit belongs to<br />
|-<br />
|PARENT_ID || int (4)|| Reference to father Organization Unit <br />
|-<br />
|PATH || nvarchar (8000)|| Chain of Organization Unit <br />
|-<br />
|CUSTOM_FIELD_1 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_2 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|CUSTOM_FIELD_3 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_4 || nvarchar (2048)|| Custom field available to store metadata<br />
|-<br />
|CUSTOM_FIELD_5 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|CUSTOM_FIELD_6 || nvarchar (2048)|| Custom field available to store metadata <br />
|-<br />
|ADDRESS || nvarchar (400)|| Organization Unit Address<br />
|-<br />
|POSTAL_CODE || nvarchar (200)|| Organization Unit Postal Code<br />
|-<br />
|CITY || nvarchar (200)|| Organization Unit City<br />
|-<br />
|REGION || nvarchar (200)|| Organization Unit Region<br />
|-<br />
|NATION || nvarchar (512)|| Organization Unit Nation<br />
|-<br />
|PHONE || nvarchar (200)|| Organization Unit Phone number<br />
|-<br />
|FAX || nvarchar (200)|| Organization Unit Fax number<br />
|-<br />
|MAIL || nvarchar (200)|| Organization Unit Email address<br />
|-<br />
|REMARK || nvarchar (400)|| Organization Unit Address remark<br />
|}<br />
<br />
== RESOURCE VIEW ==<br />
This view report some company information. The View's name is: _STD_RESOURCE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Resource Id<br />
|-<br />
|CODE || int (4)|| Resource internal identifier<br />
|-<br />
|LOGIN || nvarchar (400)|| Resource login<br />
|-<br />
|NAME || nvarchar (400)|| Resource name<br />
|-<br />
|SURNAME || nvarchar (400)|| Resource surname<br />
|-<br />
|FULLNAME || nvarchar (802)|| Resource surname + name<br />
|-<br />
|RESOURCE_STATUS_ID || int (4)|| Resource Status id<br />
|-<br />
|RESOURCE_STATUS || nvarchar (512)|| Resource Status name<br />
|-<br />
|CREATOR_ID || int (4)|| Resource Creator id<br />
|-<br />
|NATION_ID || int (4)|| Resource Nation id<br />
|-<br />
|NATION || nvarchar (512)|| Nation<br />
|-<br />
|CLIENT_ID || int (4)|| Id of client the resource belongs to<br />
|-<br />
|CLIENT || nvarchar (400)|| Name of client the resource belongs to<br />
|-<br />
|ORGANIZATION_UNIT_ID || int (4)|| Organization Unit id the resource belongs to<br />
|-<br />
|PATH || nvarchar (8000)|| Organization Unit path<br />
|-<br />
|SALEROLE_ID || int (4)|| Sale Role id, this information can drive sales revenue amount<br />
|-<br />
|SALES_ROLE || nvarchar (512)|| Sale Role name<br />
|-<br />
|SUPPLIER_ID || int (4)|| Id of supplier the resource belongs to<br />
|-<br />
|SUPPLIER || nvarchar (400)|| Name of supplier the resource belongs to <br />
|-<br />
|PURCHASEROLE_ID || int (4)|| Purchase Role id, this information can drive Purchase cost amount<br />
|-<br />
|PURCHASE_ROLE || nvarchar (512)|| Purchase Role name<br />
|-<br />
|BIRTH_DAY || datetime (8)|| Resource birth day<br />
|-<br />
|BIRTH_PLACE || nvarchar (400)|| Resource birth Place<br />
|-<br />
|EXTERNALCODE || nvarchar (400)|| Field used to store external resource reference <br />
|-<br />
|RESTYPE_ID || int (4)|| Id of Resource type<br />
|-<br />
|VIP_TYPE || int (4)|| Resource type name<br />
|-<br />
|CANDECLAREHOLIDAY || bit (1)|| Flag that identify if the resource can declare his own holiday<br />
|-<br />
|CANDECLAREILLNESS || bit (1)|| Flag that identify if the resource can declare his own illness <br />
|-<br />
|IS_EDIT_RESOURCE_DATA || bit (1)|| This flag enable the resource to modify his own data<br />
|-<br />
|IS_PERSONAL_VIEW_RIGHT || bit (1)|| This flag enable the resource to define personal view<br />
|-<br />
|CMS_ACCESS || bit (1)|| This flag enable the resource to access the Configuration Management System<br />
|-<br />
|USER_MAPPING_MODE || nvarchar (510)|| <br />
|-<br />
|EXT_CMDB_MODIFY || bit (1)|| <br />
|-<br />
|EXT_CMDB_VIEW || bit (1)|| <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field<br />
|}<br />
<br />
== PROJECT SERVICE VIEW ==<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Project Id<br />
|-<br />
|CODE || int (4)|| Project internal identifier<br />
|-<br />
|MAIN_TYPE_ID || int (4)|| Automatically field by system<br />
|-<br />
|MAIN_TYPE || varchar (7)|| This field can assume Project or Service value<br />
|-<br />
|GANTT_ESTIMATION_MODE || nvarchar (510)|| This field can assume Budget or Forecast value<br />
|-<br />
|NAME || nvarchar (400)|| Project Name<br />
|-<br />
|DESCRIPTION || nvarchar (400)|| Project Description<br />
|-<br />
|OBJECTIVES || nvarchar (1600)|| Project Objectives <br />
|-<br />
|COMMENT || nvarchar (1600)|| Project Comments <br />
|-<br />
|OPER_START_DATE || datetime (8)|| Internal Operational Start Date<br />
|-<br />
|OPER_END_DATE || datetime (8)|| Internal Operational Start End <br />
|-<br />
|EFFECTIVE_START || datetime (8)|| Actual Start Date<br />
|-<br />
|EFFECTIVE_END || datetime (8)|| Actual End Date <br />
|-<br />
|INITIAL_EXPECTED_START || datetime (8)|| Initial expected Start Date <br />
|-<br />
|INITIAL_EXPECTED_END || datetime (8)|| Initial expected Start Date <br />
|-<br />
|CURRENT_EXPECTED_START || datetime (8)|| Current Start Date <br />
|-<br />
|CURRENT_EXPECTED_END || datetime (8)|| Current End Date <br />
|-<br />
|CLIENT_ID || int (4)|| Id of client the resource belongs to<br />
|-<br />
|CLIENT || nvarchar (512)|| Name of client the resource belongs to <br />
|-<br />
|CREATOR_ID || int (4)|| Resource Creator id<br />
|-<br />
|CURRENCY_ID || int (4)|| Currency id<br />
|-<br />
|currency || nvarchar (512)|| Currency<br />
|-<br />
|FINALCLIENT_ID || int (4)|| Second reference on Client id<br />
|-<br />
|FINALCLIENT || nvarchar (400)||Second reference Client Name<br />
|-<br />
|PARENT_PRJ_ID || int (4)|| Parent project id<br />
|-<br />
|PRJADMSTATUS_ID || int (4)|| Project administrative status id<br />
|-<br />
|PROJECT_ADM_STATUS || nvarchar (8000)|| Project administrative<br />
|-<br />
|PRJ_CLASS_ID || int (4)|| Project Class id<br />
|-<br />
|CLASS || nvarchar (400)|| Project Class<br />
|-<br />
|PRJOPSTATUS_ID || int (4)|| Project Operative status id<br />
|-<br />
|PROJECT_STATUS || nvarchar (8000)|| Project Operative <br />
|-<br />
|PRJTYPE_ID || int (4)|| Project Type id<br />
|-<br />
|PROJECT_TYPE || nvarchar (512)|| Project Type <br />
|-<br />
|STATPRJ_ID || int (4)|| Statistical project id<br />
|-<br />
|STATISTICAL || nvarchar (512)|| Statistical project id <br />
|-<br />
|EXTERNAL_CODE || nvarchar (100)|| External reference code<br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationuser || nvarchar (512)|| Record creation user, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation user, Automatic field <br />
|}<br />
=== PROJECT SERVICE ACTIVITY VIEW ===<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|id || int (4)|| Project Activity Id<br />
|-<br />
|CODE || int (4)|| Project Activity internal identifier<br />
|-<br />
|ORDERING_NUMBER || int (4)|| Sort order<br />
|-<br />
|TASK_NAME || nvarchar (2048)|| Task name<br />
|-<br />
|DESCRIPTION || nvarchar (1000)|| Task Description<br />
|-<br />
|START_DATE || datetime (8)|| Activity start date <br />
|-<br />
|END_DATE || datetime (8)|| Activity end date <br />
|-<br />
|ACTPRIORITY_ID || int (4)|| Activity priority id<br />
|-<br />
|PRIORITY || nvarchar (512)|| Priority<br />
|-<br />
|ACTSTATUS_ID || int (4)|| Activity status id <br />
|-<br />
|STATUS || nvarchar (512)|| Activity status <br />
|-<br />
|ACTIVITY_TYPE_ID || int (4)|| Activity type id <br />
|-<br />
|ACTIVITY_TYPE || nvarchar (512)|| Activity type <br />
|-<br />
|PRJ_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|DURATION || float (8)|| Estimated duration of task <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationUser || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation date, Automatic field<br />
|}<br />
<br />
== TICKET VIEW ==<br />
This view report some company information. The View's name is: _STD_TICKET_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Project Id<br />
|-<br />
|CODE || int (4)|| Project internal identifier<br />
|-<br />
|TICKETTYPE_ID || int (4)|| Ticket type reference id<br />
|-<br />
|TICKET_TYPE || nvarchar (512)|| Ticket type name<br />
|-<br />
|PROJECT_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|SERVICE_REQUEST_ID || int (4)||Service catalogue request reference id<br />
|-<br />
|SERVICE_REQUEST || nvarchar (1024)|| Service catalogue request reference name<br />
|-<br />
|CURRENT_SERVICE_REQUEST_ID || int (4)|| Current Service catalogue request reference id<br />
|-<br />
|CURRENT_SERVICE_REQUEST || nvarchar (1024)|| Current Service catalogue request reference name <br />
|-<br />
|SHORT_DESCRIPTION || nvarchar (-1)|| Ticket short description<br />
|-<br />
|DESCRIPTION || nvarchar (-1)|| Ticket Description<br />
|-<br />
|ANALYSIS || nvarchar (-1)|| Ticket Analisys description<br />
|-<br />
|SOLUTION || nvarchar (-1)|| Ticket Solution description<br />
|-<br />
|WORKAROUND || nvarchar (-1)|| Ticket Workaound description <br />
|-<br />
|COMMENTS || nvarchar (-1)|| Ticket Comments<br />
|-<br />
|OWNER_ID || int (4)|| Ticket Owner Resource reference <br />
|-<br />
|OWNER || nvarchar (512)||Ticket Owner Resource <br />
|-<br />
|REQUESTER_ID || int (4)|| Ticket Requester reference id<br />
|-<br />
|REQUESTER || nvarchar (802)||Ticket Requester reference<br />
|-<br />
|RESOURCE_ID || int (4)|| Ticket Resource reference id<br />
|-<br />
|RESOURCE || nvarchar (802)||Ticket Resource reference<br />
|-<br />
|REQUIRED_SOLUTION_DATE || datetime (8)|| Ticket required solution date <br />
|-<br />
|FORECAST_SOLUTION_DATE || datetime (8)|| Forecast solution date of ticket<br />
|-<br />
|SOLUTIONGROUP_ID || int (4)|| Group reference id. At each group per workflow is assigned a specific role.<br />
|-<br />
|DSG1 || nvarchar (512)|| Group reference name<br />
|-<br />
|MASTER_SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DSG2 || nvarchar (512)|| Group reference name<br />
|-<br />
|THIRD_SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DSG3 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG4_ID || int (4)|| Group reference id<br />
|-<br />
|DSG4 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG5_ID || int (4)|| Group reference id<br />
|-<br />
|DSG5 || nvarchar (512)|| Group reference name<br />
|-<br />
|DSG6_ID || int (4)|| Group reference id<br />
|-<br />
|DSG6 || nvarchar (512)|| Group reference name<br />
|-<br />
|WORKFLOW_ID || int (4)|| Workflow reference id<br />
|-<br />
|WORKFLOW_DESCRIPTION || nvarchar (2048)|| Workflow description<br />
|-<br />
|WORKFLOW_TICKET_ADM_STATUS_ID || int (4)|| Workflow administrarive status id<br />
|-<br />
|WORKFLOW_TICKET_ADM_STATUS || nvarchar (512)|| Workflow administrarive status<br />
|-<br />
|WORKFLOW_TICKET_OP_STATUS_ID || int (4)|| Workflow operative status id<br />
|-<br />
|WORKFLOW_TICKET_OP_STATUS || nvarchar (512)|| Workflow operative status<br />
|-<br />
|RESOLUTION_CAUSE_ID || int (4)|| Ticket resolution cause reference id <br />
|-<br />
RESOLUTION_CAUSE || nvarchar (512)|| Ticket resolution cause reference <br />
|-<br />
|TICKET_CLOSURE_CAUSE_ID || int (4)|| Ticket closure cause reference id<br />
|-<br />
|TICKET_CLOSURE_CAUSE || nvarchar (512)|| Ticket closure cause reference <br />
|-<br />
|REQUESTED_PRIORITY_ID || int (4)|| Ticket requested priority id<br />
|-<br />
|REQUESTED_PRIORITY || nvarchar (512)|| Ticket requested priority <br />
|-<br />
|TARGET_ENVIRONMENT_ID || int (4)|| Target environment reference id <br />
|-<br />
|TARGET_ENVIRONMENT || nvarchar (512)|| Target environment reference <br />
|-<br />
|TICKET_IMPACT_ID || int (4)|| Ticket impact id<br />
|-<br />
|TICKET_IMPACT || nvarchar (512)|| Ticket impact reference <br />
|-<br />
|TICKET_URGENCY_ID || int (4)|| Ticket urgency id<br />
|-<br />
|TICKET_UREGENCY || nvarchar (512)|| Ticket urgency reference <br />
|-<br />
|TICKET_PRIORITY_ID || int (4)|| Ticket priority id, usually this is calculated field value based on Ticket Impact and Urgency<br />
|-<br />
|TICKET_PRIORITY || nvarchar (512)|| Ticket priority reference <br />
|-<br />
|TICKET_ACTIVITY_TEMPLATE_ID || int (4)|| Ticket activity id of template used to load the Ticket activity<br />
|-<br />
|TICKET_ACTIVITY_TEMPLATE || nvarchar (200)||Ticket activity template used to load the Ticket activity <br />
|-<br />
|TUPLE_TICKET_AREA_ID || int (4)|| First level of Standard Tuple. Ticket Area reference id<br />
|-<br />
|TUPLE_TICKET_AREA || nvarchar (512)|| First level of Standard Tuple. Ticket Area reference name<br />
|-<br />
|TUPLE_TICKET_CATEGORY_ID || int (4)|| Second level of Standard Tuple. Ticket Category reference id<br />
|-<br />
|TUPLE_TICKET_CATEGORY || nvarchar (512)|| Second level of Standard Tuple. Ticket Category reference name <br />
|-<br />
|TUPLE_TICKET_TOPIC_ID || int (4)|| Third level of Standard Tuple. Ticket Topic reference id <br />
|-<br />
|TUPLE_TICKET_TOPIC || nvarchar (512)|| Third level of Standard Tuple. Ticket Topic reference name <br />
|-<br />
|ESTIMATION_START || datetime (8)|| Ticket Estimation Start range date <br />
|-<br />
|ESTIMATION_END || datetime (8)|| Ticket Estimation End range date <br />
|-<br />
|ESTIMATION_DATE || datetime (8)|| Ticket Estimation cutoff date <br />
|-<br />
|ESTIMATION_MODE || int (4)|| Ticket Estimation mode<br />
|-<br />
|COST_METHOD || nvarchar (510)|| Ticket cost method, can assume a value Standard or Fixed Cost Only <br />
|-<br />
|ATTACHMENT_PRESENT || bit (1)|| Flag stated at least on document is attached to a ticket <br />
|-<br />
|ACTIVITY_ASSIGN || varchar (21)|| This field can assume a value Activity Not Assigned or Activity Assigned<br />
|-<br />
|TICKET_USER_INFO_ID || int (4)|| Ticket requester information reference id <br />
|-<br />
|CREATION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|CREATION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|CLOSE_DATE || datetime (8)|| Ticket close date<br />
|-<br />
|CLOSE_USER || nvarchar (512)|| Ticket close user <br />
|}<br />
=== TICKET ACTIVITY VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Ticket activity Id<br />
|-<br />
|CODE || int (4)|| Ticket activity internal identifier<br />
|-<br />
|TICKET_ACTIVITY_TYPE_ID || int (4)|| Ticket Activity type reference id <br />
|-<br />
|TICKET_ACTIVITY_TYPE || nvarchar (1600)|| Ticket Activity type reference name<br />
|-<br />
|TICKET_ACTIVITY_SUB_TYPE_ID || int (4)|| Ticket Activity Subtype reference id <br />
|-<br />
|TICKET_ACTIVITY_SUB_TYPE || nvarchar (1000)|| Ticket Activity Subtype reference name<br />
|-<br />
|TICKET_ACTIVITY_STATUS_ID || int (4)||Ticket Activity status reference id <br />
|-<br />
|TICKET_ACTIVITY_STATUS || nvarchar (8000)|| Ticket Activity status reference name<br />
|-<br />
|NAME || nvarchar (512)|| Ticket Activity Name<br />
|-<br />
|DESCRIPTION || nvarchar (-1)|| Ticket Activity Description<br />
|-<br />
|COMMENTS || nvarchar (-1)|| Ticket Activity Comment<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|-<br />
|ASSIGNEE || nvarchar (8000)|| Resource reference name<br />
|-<br />
|SOLUTIONGROUP_ID || int (4)|| Group reference id<br />
|-<br />
|DURATION || float (8)|| Estimated duration of task <br />
|-<br />
|REQUIRED_START_DATE || datetime (8)|| Ticket required solution start date <br />
|-<br />
|REQUIRED_END_DATE || datetime (8)|| Ticket required solution end+ date <br />
|-<br />
|FORECASTED_START_DATE || datetime (8)|| Forecast solution start date of ticket<br />
|-<br />
|FORECASTED_END_DATE || datetime (8)|| Forecast solution end date of ticket<br />
|-<br />
|EFFECTIVE_START_DATE || datetime (8)|| Actaul solution start date of ticket<br />
|-<br />
|EFFECTIVE_END_DATE || datetime (8)|| Actual solution end date of ticket<br />
|-<br />
|PAID || bit (1)|| If true the recored Timesheet hours are taken in account into the balance column of estimation<br />
|-<br />
|ORDERING_NUMBER || int (4)|| Sort Order<br />
|-<br />
|CREATION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|CREATION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_DATE || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|REVISION_USER || nvarchar (512)|| Record creation date, Automatic field<br />
<br />
|}<br />
=== TICKET CONFIGURATION ITEM VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_CONFIGURATION_ITEM_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Configuration Item Id<br />
|-<br />
|GUID || nvarchar (100)|| Configuration Item GUID<br />
|-<br />
|NAME || nvarchar (510)|| Configuration Item Name<br />
|-<br />
|TYPE || nvarchar (510)|| Configuration Item type<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|}<br />
<br />
=== TICKET CUSTOM FIELD VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_CUSTOM_FIELDS_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Ticket custom field reference Id<br />
|-<br />
|NAME || nvarchar (512)|| Ticket custom field reference Name<br />
|-<br />
|TYPE || nvarchar (8000)|| This field contains the type of the data inserted<br />
|-<br />
|VALUE || nvarchar (-1)|| Ticket custom field value<br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|}<br />
=== TICKET ESTIMATION VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_ESTIMATION_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
<br />
<br />
=== TICKET FIELD VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_FIELD_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int (4)|| Field reference Id<br />
|-<br />
|NAME || nvarchar (256)|| Field reference Name<br />
|-<br />
|TICKET_FIELD_TYPE_ID || nvarchar (255)|| This field contains the type of the data inserted. Three possible values can be present <br />
* "PREDEFINED": used to define that the field is a Standard Field<br />
* "CUSTOM": used to define that the field is a Custom Field<br />
* "OBJECTIVE":automatically added by the system when the cusomer declare an Objective<br />
|}<br />
<br />
=== TICKET OCE OBJECTIVE VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_OCE_OBJECTIVE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET RELATED VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_RELATED_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET USER INFO VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_USER_INFO_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET USER NOTE VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_USER_NOTE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
=== TICKET WORKER VIEW ===<br />
This view report some company information. The View's name is: _STD_TICKET_WORKER_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
<br />
|}<br />
== TIMESHEET VIEW ==<br />
This view report some company information. The View's name is: _STD_TIMESHEET_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|COMPANY_ID || int (4)|| Company Id<br />
|-<br />
|ID || int (4)|| Timesheet Id<br />
|-<br />
|CODE || int (4)|| Timesheet internal identifier<br />
|-<br />
|PRJ_ID || int (4)|| Project reference id<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|CURRENCY_ID || int (4)|| Currency reference id <br />
|-<br />
|CURRENCY || nvarchar (512)|| Currency reference name<br />
|-<br />
|RESRC_ID || int (4)|| Resource reference id<br />
|-<br />
|RESOURCE || nvarchar (802)|| Resource reference<br />
|-<br />
|GROUP_ID || int (4)|| Group reference id<br />
|-<br />
|GROUP || nvarchar (512)|| Group reference name<br />
|-<br />
|WPLACE_ID || int (4)|| Location reference id <br />
|-<br />
|LOCATION || nvarchar (512)|| Location reference name<br />
|-<br />
|PURCHASE_ROLE_ID || int (4)|| Pruchase Role reference id <br />
|-<br />
|PURCHASE_ROLE || nvarchar (512)|| Pruchase Role reference name<br />
|-<br />
|ACTIVITY_DATE || datetime (8)|| Timesheet activity date<br />
|-<br />
|DURATION || float (8)|| Timesheet duration. This is the duration declared in a resource section<br />
|-<br />
|PM_DURATION || float (8)|| Timesheet duration. This is the duration declared in a PM section<br />
|-<br />
|MANAGER_DURATION || float (8)||Timesheet duration. This is the duration declared in a Manager section <br />
|-<br />
|ACT_DESCRIPTION || nvarchar (2000)||Timesheet Actvity description. This is the duration declared in a resource section<br />
|-<br />
|PM_ACT_DESCRIPTION || nvarchar (2000)|| Timesheet Actvity description. This is the duration declared in a PM section <br />
|-<br />
|MANAGER_ACT_DESCRIPTION || nvarchar (2000)|| Timesheet Actvity description. This is the duration declared in a Manager section <br />
|-<br />
|ACTIVITY_ID || int (4)|| Timesheet Actvity id. This is the id related to a resource section <br />
|-<br />
|PM_ACTIVITY_ID || int (4)|| Timesheet Actvity id. This is the id related to a PM section <br />
|-<br />
|MANAGER_ACTIVITY_ID || int (4)||Timesheet Actvity id. This is the id related to a Manager section <br />
|-<br />
|TICKET_ID || int (4)|| Ticket reference id<br />
|-<br />
|TICKETACTIVITY_ID || int (4)|| Ticket Activity reference id <br />
|-<br />
|TICKETDESCRIPTION || nvarchar (8000)|| Ticket Activity description, copied from Ticket Activity <br />
|-<br />
|TICKETCOMMENTS || nvarchar (8000)|| Ticket Activity Comment<br />
|-<br />
|ROWRPMSTAT_ID || int (4)|| Timesheet Operational status Resource / PM section<br />
|-<br />
|ROWMSTAT_ID || int (4)|| Timesheet Operational status Manager section<br />
|-<br />
|COMMENT || nvarchar (400)|| Comment inserted by resource <br />
|-<br />
|PM_COMMENT || nvarchar (400)|| Comment inserted by PM <br />
|-<br />
|MANAGER_COMMENT || nvarchar (400)|| Comment inserted by Manager <br />
|-<br />
|creationDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|creationUser || nvarchar (512)|| Record creation date, Automatic field<br />
|-<br />
|revisionDate || datetime (8)|| Record creation date, Automatic field<br />
|-<br />
|revisionUser || nvarchar (512)|| Record creation date, Automatic field<br />
|}<br />
<br />
== TUPLE VIEW ==<br />
This view report some company information. The View's name is: _STD_TUPLE_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|ID || int|| Tuple Identifier<br />
|-<br />
|CODE || int|| Tuple Identifier<br />
|-<br />
|COMPANY_ID || int|| Company Identifier<br />
|-<br />
|TUPLE_NAME || varchar(256)|| Tupla Name<br />
|-<br />
|TUPLE_AREA_ID || int|| First level of Tuple, Area, Identifier<br />
|-<br />
|TUPLE_AREA || varchar(256)|| Tuple Area Name<br />
|-<br />
|TUPLE_CATEGORY_ID || int|| Second level of Tuple, Category, Identifier<br />
|-<br />
|TUPLE_CATEGORY || varchar(256)|| Tuple Category Name<br />
|-<br />
|TUPLE_TOPIC_ID || int|| Third level of Tuple, Topic, Identifier<br />
|-<br />
|TUPLE_TOPIC || varchar(256)|| Tuple Topic Name<br />
|}<br />
<br />
== SERVICE CATALOGUE REQUEST (SRCS) VIEW ==<br />
This view report some company information. The View's name is: _STD_PROJECT_SERVICE_ACTIVITY_VIEW<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Field Name !! Field Type !! Description<br />
|-<br />
|CATALOGO || nvarchar (2048)|| Identify a complete set of service catalogue requests <br />
|-<br />
|SECTION || nvarchar (512)|| Sub session of catalogue of requests <br />
|-<br />
|TOPIC_1 || nvarchar (1024)|| Level 1 of nested level of section <br />
|-<br />
|TOPIC_2 || nvarchar (1024)|| Level 2 of nested level of section <br />
|-<br />
|TOPIC_3 || nvarchar (1024)|| Level 3 of nested level of section <br />
|-<br />
|ID || int (4)|| Service request catalogue Id<br />
|-<br />
|SERVICE_REQUEST || nvarchar (1024)|| Service catalogue request reference name<br />
|-<br />
|ENABLED || bit (1)|| Flag stated if the SRCS request is enabled <br />
|-<br />
|PROJECT_ID || int (4)|| Project reference id<br />
|-<br />
|TICKET_TYPE_ID || int (4)|| Ticket type reference id <br />
|-<br />
|TRANSITION_RULE_ID || int (4)|| Transition rule activated when a new ticket is created<br />
|-<br />
|PROJECT || nvarchar (400)|| Project Name<br />
|-<br />
|TICKET_TYPE || nvarchar (512)|| Ticket type reference name <br />
|-<br />
|TRANSITION_RULE || nvarchar (512)|| Transition rule name<br />
|-<br />
|TATPL_ID|| int || Ticket Activity Template id<br />
|-<br />
|TA_TEMPLATE|| int || Ticket Activity Template name<br />
|-<br />
|SOLUTIONGROUP || nvarchar (-1)|| Group reference name<br />
|-<br />
|MASTER_SOLUTIONGROUP || nvarchar (-1)|| Group reference name<br />
|-<br />
|OWNER || nvarchar (-1)|| Owner reference name<br />
|-<br />
|TAB_RESOURCES || nvarchar (-1)|| Tab of SRCS session used to grant a request to Resources<br />
|-<br />
|TAB_SOLUTIONGROUP || nvarchar (-1)|| Tab of SRCS session used to grant a request to Groups<br />
|-<br />
|TAB_ORGANIZATIONUNIT || nvarchar (-1)|| Tab of SRCS session used to grant a request to Organization Unit<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Standard_Function&diff=4017Standard Function2018-10-23T13:48:37Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® propose to a customer a set of Standard function to facilitate the reporting development.<br />
These functions are defined at data base level.<br />
<br />
The paragraphs below report the standard function collection.<br />
<br />
The information reported are shown in the following table:<br />
{| class="wikitable"<br />
! Function Name!! Description<br />
|-<br />
|getSRCSValue || This function return information about SRCS record<br />
|-<br />
|getTCFValue || This function return information about Ticket Custom field record<br />
|}<br />
<br />
== getSRCSValue ==<br />
<br />
Purpose of this function is given to Customer a simple way to view the information connected to SRCS record.<br />
<br />
=== Defnition === <br />
[dbo].[getSRCSValue](@ticketFieldId int, @srcId int, @type int = 0) returns nvarchar(max)<br />
<br />
The function expects three parameters<br />
<br />
{| class="wikitable"<br />
! Parameter Name !!Type!! Description<br />
|-<br />
| ticketFieldId || int || This is the Ticket field id value. The list of id is visible in __STD_TICKET_FIELD View <br />
|-<br />
| srcId || int || This is the SRCS record id<br />
|-<br />
| type || int || Set 0 if you want to return as result of the function the a string value; 1 id we want to return the ID of the result. E.g: if the ticketFieldId = 18, Solution Group, when the type is set to 0 the function return the Solution Group name, when is set to 1 it return the Solution group ID<br />
|}<br />
<br />
and return a string value.<br />
<br />
If for a specific ticketFieldId the function return blank, send an email to the itmSUITE® Support to check if the specific field management is implemented<br />
<br />
<br />
<br />
== getTCFValue ==<br />
Purpose of this function is given to Customer a simple way to view the information connected to Custom field valorized in a Ticket record.<br />
<br />
=== Defnition === <br />
[dbo].[getTCFValue](@custiomFieldId int, @ticketId int) returns nvarchar(max)<br />
<br />
The function expects three parameters:<br />
<br />
{| class="wikitable"<br />
! Parameter Name !!Type!! Description<br />
|-<br />
| custiomFieldId || int || This is the Custom field id value. The list of id is visible in __STD_TICKET_FIELD_VIEW <br />
|-<br />
| ticketId || int || This is the id of Ticket. Ticket id is visible using the __STD_TICKET_VIEW View <br />
|}<br />
<br />
If for a specific ticketFieldId the function return blank, send an email to the itmSUITE® Support to check if the specific field management is implemented</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4012Filters management2018-06-21T12:15:27Z<p>Francesco.bertuletti: /* How To Create complex filter */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / Ticket Types / Operational Statuses</u><br />
* <u>Ticket Types / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Types</u> || '''''Ticket Type''''' || Primary || multiselected filter for ''Workflow'' Ticket Types<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
|-<br />
|<u>Groups</u> || '''''Ticket Dynamic Group/Role''''' || Secondary || This section enable the user to filter per<br />
* Group<br />
* Role on ticket<br />
For each group is possible to enable the "Group Sub option" to simplify the group selection. <br />
Ticket role filter management is based on resource role on ticket (e.g. Ticket where the logged user is Creator or Owner or Ticket Workr,ect.) The roles selection list is devided in two sections. Ticket where the logged user is ... and Ticket Without ... <br />
This sections works with an AND clause; each item in each section works with an OR clause.<br />
|-<br />
|<u>Priority</u> || '''''Ticket Priority''''' || Secondary ||This section enable the user to filter the ticket based on Ticket Priority and its component (ticket impact and ticket priority)<br />
|-<br />
|<u>Requester</u> || '''''Requesters''''' || Secondary ||This section enable the user to filter based on ''requester'' information / ''[[GLOSSARY|Client]]'' or position in the ''[[GLOSSARY | Organization Unit]]''<br />
|-<br />
|<u>Generic </u> || '''''Generic information''''' || Secondary ||This section enable the user to filter base on different feature like ''Target Enviroment'',''Service Request'',''Service'',''Product'', ''Ticket activity template''and ''Tuple'' elements<br />
|-<br />
|<u>Causes </u> || '''''Ticket Transition''''' || Secondary || This section enable the user to filter based on ''Ticket closure clause'' and ''Ticket Resolution clause''<br />
|-<br />
|<u>Configuration Item </u> || '''''Confguration Item''''' || Secondary || multiselected filter for ''Configuration Item'' name.<br />
|-<br />
|<u>Custon field </u> || '''''Custom field''''' || Secondary || multiselected filter for ''Custom Fields'' defined for each ''Ticket type'' selected.<br />
|-<br />
|<u>Text Search </u> || '''''Text''''' || Secondary ||This section enable the user to select one or more Text field and specify a "Search String" value''<br />
<br />
|}<br />
<br />
==== How To Create complex filter ====<br />
<br />
Complex filter will be created as a combination of Ticket parameter selection. For example:<br />
<br />
Filter1 : Extract all the Incident ticket where I'm Owner or I'm Ticket Worker, is implented:<br />
* Primary section: Ticket Types : Select "Incident"<br />
* Secondary section: Group : Select two elements:<br />
# Ticket where the logged user is Owner<br />
# Ticket where the logged user is Ticket Worker<br />
<br />
<br />
Filter2 : Extract all the Incident, Service request ticket without Owner, is implented:<br />
* Primary section: Ticket Types : Select two elements:<br />
# "Incident"<br />
# "Request Fulfilment"<br />
* Secondary section: Group : Select Ticket without Owner<br />
<br />
<br />
The administrator has to manage carefully the flexibility the tool give him because he/she can select a conflictual choice, so the filter doesn't return any data.<br />
<br />
In Filter ''view'' differently from ''Personal'' view has the possibility to define <u>QL Expression </u> (Query Language). This way to filter ticket is delivered only to the Administrator due to the technical knowledge necessary to create then.</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4011Filters management2018-06-21T10:50:54Z<p>Francesco.bertuletti: /* How To Create complex filter */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / Ticket Types / Operational Statuses</u><br />
* <u>Ticket Types / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Types</u> || '''''Ticket Type''''' || Primary || multiselected filter for ''Workflow'' Ticket Types<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
|-<br />
|<u>Groups</u> || '''''Ticket Dynamic Group/Role''''' || Secondary || This section enable the user to filter per<br />
* Group<br />
* Role on ticket<br />
For each group is possible to enable the "Group Sub option" to simplify the group selection. <br />
Ticket role filter management is based on resource role on ticket (e.g. Ticket where the logged user is Creator or Owner or Ticket Workr,ect.) The roles selection list is devided in two sections. Ticket where the logged user is ... and Ticket Without ... <br />
This sections works with an AND clause; each item in each section works with an OR clause.<br />
|-<br />
|<u>Priority</u> || '''''Ticket Priority''''' || Secondary ||This section enable the user to filter the ticket based on Ticket Priority and its component (ticket impact and ticket priority)<br />
|-<br />
|<u>Requester</u> || '''''Requesters''''' || Secondary ||This section enable the user to filter based on ''requester'' information / ''[[GLOSSARY|Client]]'' or position in the ''[[GLOSSARY | Organization Unit]]''<br />
|-<br />
|<u>Generic </u> || '''''Generic information''''' || Secondary ||This section enable the user to filter base on different feature like ''Target Enviroment'',''Service Request'',''Service'',''Product'', ''Ticket activity template''and ''Tuple'' elements<br />
|-<br />
|<u>Causes </u> || '''''Ticket Transition''''' || Secondary || This section enable the user to filter based on ''Ticket closure clause'' and ''Ticket Resolution clause''<br />
|-<br />
|<u>Configuration Item </u> || '''''Confguration Item''''' || Secondary || multiselected filter for ''Configuration Item'' name.<br />
|-<br />
|<u>Custon field </u> || '''''Custom field''''' || Secondary || multiselected filter for ''Custom Fields'' defined for each ''Ticket type'' selected.<br />
|-<br />
|<u>Text Search </u> || '''''Text''''' || Secondary ||This section enable the user to select one or more Text field and specify a "Search String" value''<br />
<br />
|}<br />
<br />
==== How To Create complex filter ====<br />
<br />
Complex filter will be created as a combination of Ticket parameter selection. For example:<br />
<br />
Filter1 : Extract all the Incident ticket where I'm Owner or I'm Ticket Worker, is implented:<br />
* Primary section: Ticket Types : Select "Incident"<br />
* Secondary section: Group : Select two elements:<br />
# Ticket where the logged user is Owner<br />
# Ticket where the logged user is Ticket Worker<br />
<br />
<br />
Filter2 : Extract all the Incident, Service request ticket without Owner, is implented:<br />
* Primary section: Ticket Types : Select two elements:<br />
# "Incident"<br />
# "Request Fulfilment"<br />
* Secondary section: Group : Select Ticket without Owner<br />
<br />
<br />
The administrator has to manage carefully the flexibity the tool give him because he/she can select a conflictual choise, so the filter doesn't return any data.</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4010Filters management2018-06-21T10:33:58Z<p>Francesco.bertuletti: </p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / Ticket Types / Operational Statuses</u><br />
* <u>Ticket Types / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Types</u> || '''''Ticket Type''''' || Primary || multiselected filter for ''Workflow'' Ticket Types<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
|-<br />
|<u>Groups</u> || '''''Ticket Dynamic Group/Role''''' || Secondary || This section enable the user to filter per<br />
* Group<br />
* Role on ticket<br />
For each group is possible to enable the "Group Sub option" to simplify the group selection. <br />
Ticket role filter management is based on resource role on ticket (e.g. Ticket where the logged user is Creator or Owner or Ticket Workr,ect.) The roles selection list is devided in two sections. Ticket where the logged user is ... and Ticket Without ... <br />
This sections works with an AND clause; each item in each section works with an OR clause.<br />
|-<br />
|<u>Priority</u> || '''''Ticket Priority''''' || Secondary ||This section enable the user to filter the ticket based on Ticket Priority and its component (ticket impact and ticket priority)<br />
|-<br />
|<u>Requester</u> || '''''Requesters''''' || Secondary ||This section enable the user to filter based on ''requester'' information / ''[[GLOSSARY|Client]]'' or position in the ''[[GLOSSARY | Organization Unit]]''<br />
|-<br />
|<u>Generic </u> || '''''Generic information''''' || Secondary ||This section enable the user to filter base on different feature like ''Target Enviroment'',''Service Request'',''Service'',''Product'', ''Ticket activity template''and ''Tuple'' elements<br />
|-<br />
|<u>Causes </u> || '''''Ticket Transition''''' || Secondary || This section enable the user to filter based on ''Ticket closure clause'' and ''Ticket Resolution clause''<br />
|-<br />
|<u>Configuration Item </u> || '''''Confguration Item''''' || Secondary || multiselected filter for ''Configuration Item'' name.<br />
|-<br />
|<u>Custon field </u> || '''''Custom field''''' || Secondary || multiselected filter for ''Custom Fields'' defined for each ''Ticket type'' selected.<br />
|-<br />
|<u>Text Search </u> || '''''Text''''' || Secondary ||This section enable the user to select one or more Text field and specify a "Search String" value''<br />
<br />
|}<br />
<br />
==== How To Create complex filter ====<br />
<br />
Complex filter will be created as a combination of Ticket parameter selection. For example:<br />
<br />
Filter1 : Extract all the Incident ticket where I'm Owner or I'm Ticket Worker, is implented:<br />
* Primary section: Ticket Types : Select "Incident"<br />
* Secondary section: Group : Select two elements:<br />
# Ticket where the logged user is Owner<br />
# Ticket where the logged user is Ticket Worker</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4009Filters management2018-06-21T10:27:12Z<p>Francesco.bertuletti: /* Primary and Secondary Section */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / Ticket Types / Operational Statuses</u><br />
* <u>Ticket Types / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Types</u> || '''''Ticket Type''''' || Primary || multiselected filter for ''Workflow'' Ticket Types<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
|-<br />
|<u>Groups</u> || '''''Ticket Dynamic Group/Role''''' || Secondary || This section enable the user to filter per<br />
* Group<br />
* Role on ticket<br />
For each group is possible to enable the "Group Sub option" to simplify the group selection. <br />
Ticket role filter management is based on resource role on ticket (e.g. Ticket where the logged user is Creator or Owner or Ticket Workr,ect.) The roles selection list is devided in two sections. Ticket where the logged user is ... and Ticket Without ... <br />
This sections works with an AND clause; each item in each section works with an OR clause.<br />
|-<br />
|<u>Priority</u> || '''''Ticket Priority''''' || Secondary ||This section enable the user to filter the ticket based on Ticket Priority and its component (ticket impact and ticket priority)<br />
|-<br />
|<u>Requester</u> || '''''Requesters''''' || Secondary ||This section enable the user to filter based on ''requester'' information / ''[[GLOSSARY|Client]]'' or position in the ''[[GLOSSARY | Organization Unit]]''<br />
|-<br />
|<u>Generic </u> || '''''Generic information''''' || Secondary ||This section enable the user to filter base on different feature like ''Target Enviroment'',''Service Request'',''Service'',''Product'', ''Ticket activity template''and ''Tuple'' elements<br />
|-<br />
|<u>Causes </u> || '''''Ticket Transition''''' || Secondary || This section enable the user to filter based on ''Ticket closure clause'' and ''Ticket Resolution clause''<br />
|-<br />
|<u>Configuration Item </u> || '''''Confguration Item''''' || Secondary || multiselected filter for ''Configuration Item'' name.<br />
|-<br />
|<u>Custon field </u> || '''''Custom field''''' || Secondary || multiselected filter for ''Custom Fields'' defined for each ''Ticket type'' selected.<br />
|-<br />
|<u>Text Search </u> || '''''Text''''' || Secondary ||This section enable the user to select one or more Text field and specify a "Search String" value''<br />
<br />
<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4008Filters management2018-06-21T10:22:19Z<p>Francesco.bertuletti: /* Primary and Secondary Section */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / Ticket Types / Operational Statuses</u><br />
* <u>Ticket Types / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Types</u> || '''''Ticket Type''''' || Primary || multiselected filter for ''Workflow'' Ticket Types<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
|-<br />
|<u>Groups</u> || '''''Ticket Dynamic Group/Role''''' || Secondary || This section enable the user to filter per<br />
* Group<br />
* Role on ticket<br />
For each group is possible to enable the "Group Sub option" to simplify the group selection. <br />
Ticket role filter management is based on resource role on ticket (e.g. Ticket where the logged user is Creator or Owner or Ticket Workr,ect.) <br />
|-<br />
|<u>Priority</u> || '''''Ticket Priority''''' || Secondary ||This section enable the user to filter the ticket based on Ticket Priority and its component (ticket impact and ticket priority)<br />
|-<br />
|<u>Requester</u> || '''''Requesters''''' || Secondary ||This section enable the user to filter based on ''requester'' information / ''[[GLOSSARY|Client]]'' or position in the ''[[GLOSSARY | Organization Unit]]''<br />
|-<br />
|<u>Generic </u> || '''''Generic information''''' || Secondary ||This section enable the user to filter base on different feature like ''Target Enviroment'',''Service Request'',''Service'',''Product'', ''Ticket activity template''and ''Tuple'' elements<br />
|-<br />
|<u>Causes </u> || '''''Ticket Transition''''' || Secondary || This section enable the user to filter based on ''Ticket closure clause'' and ''Ticket Resolution clause''<br />
|-<br />
|<u>Configuration Item </u> || '''''Confguration Item''''' || Secondary || multiselected filter for ''Configuration Item'' name.<br />
|-<br />
|<u>Custon field </u> || '''''Custom field''''' || Secondary || multiselected filter for ''Custom Fields'' defined for each ''Ticket type'' selected.<br />
|-<br />
|<u>Text Search </u> || '''''Text''''' || Secondary ||This section enable the user to select one or more Text field and specify a "Search String" value''<br />
<br />
<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4007Filters management2018-06-21T10:16:56Z<p>Francesco.bertuletti: /* Primary and Secondary Section */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / Ticket Types / Operational Statuses</u><br />
* <u>Ticket Types / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Types</u> || '''''Ticket Type''''' || Primary || multiselected filter for ''Workflow'' Ticket Types<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
|-<br />
|<u>Groups</u> || '''''Ticket Dynamic Groups''''' || Secondary || Multiselection ''Group'' of filter. For each group is possible to enable the "Group Sub option" to simplify the group selection. <br />
|-<br />
|<u>Priority</u> || '''''Ticket Priority''''' || Secondary ||This section enable the user to filter the ticket based on Ticket Priority and its component (ticket impact and ticket priority)<br />
|-<br />
|<u>Requester</u> || '''''Requesters''''' || Secondary ||This section enable the user to filter based on ''requester'' information / ''[[GLOSSARY|Client]]'' or position in the ''[[GLOSSARY | Organization Unit]]''<br />
|-<br />
|<u>Generic </u> || '''''Generic information''''' || Secondary ||This section enable the user to filter base on different feature like ''Target Enviroment'',''Service Request'',''Service'',''Product'', ''Ticket activity template''and ''Tuple'' elements<br />
|-<br />
|<u>Causes </u> || '''''Ticket Transition''''' || Secondary || This section enable the user to filter based on ''Ticket closure clause'' and ''Ticket Resolution clause''<br />
|-<br />
|<u>Configuration Item </u> || '''''Confguration Item''''' || Secondary || multiselected filter for ''Configuration Item'' name.<br />
|-<br />
|<u>Custon field </u> || '''''Custom field''''' || Secondary || multiselected filter for ''Custom Fields'' defined for each ''Ticket type'' selected.<br />
|-<br />
|<u>Text Search </u> || '''''Text''''' || Secondary ||This section enable the user to select one or more Text field and specify a "Search String" value''<br />
<br />
<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4006Filters management2018-06-21T09:56:24Z<p>Francesco.bertuletti: /* Primary and Secondary Section */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / Ticket Types / Operational Statuses</u><br />
* <u>Ticket Types / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Types</u> || '''''Ticket Type''''' || Primary || multiselected filter for ''Workflow'' Ticket Types<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4005Filters management2018-06-21T09:53:25Z<p>Francesco.bertuletti: /* Global Settings */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / Ticket Types / Operational Statuses</u><br />
* <u>Ticket Types / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4004Filters management2018-06-21T09:52:33Z<p>Francesco.bertuletti: /* Global Settings */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / ''[[GLOSSARY|Ticket type]]''s / Operational Statuses</u><br />
* <u>''[[GLOSSARY|Ticket type]]''s / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4003Filters management2018-06-21T09:51:55Z<p>Francesco.bertuletti: /* Global Settings */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / ''[[GLOSSARY|Ticket Type]]''s / Operational Statuses</u><br />
* <u>''[[GLOSSARY|Ticket Type]]''s / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Filters_management&diff=4002Filters management2018-06-21T09:51:13Z<p>Francesco.bertuletti: /* Global Settings */</p>
<hr />
<div>The itmSUITE® provides a complete filter management system that implements items (ticket, timesheet, etc...) searching according to several filtering rules.<br />
In itmSUITE® three filter types can be defined:<br />
* '''Global filters''': are permanent filters configured by company admin and accessible to a group of users of the same company.<br />
* '''Personal filters''': are permanent filters configured by user and accessible only to him/her.<br />
* '''Temporary filters''': are temporary filters configured by user and accessible to him/her in current session.<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
! Entity !! Global filter !! Personal filter !! Temporary filter<br />
|-<br />
|''Action'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Asset'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Billing Calendar'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Forced View'' || '''X''' || ||<br />
<br />
|-<br />
|''Invoice'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Message'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Milestone'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''News'' || || || '''X'''<br />
<br />
|-<br />
|''Personal View'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Activity'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Project Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Purchase Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Sale Contract'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Service Template'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Supplier'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Resource Planning'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Ticket Activity'' || '''X''' || '''X''' || '''X'''<br />
<br />
|-<br />
|''Timesheet'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''User'' || || '''X''' || '''X'''<br />
<br />
|-<br />
|''Workflow'' || || '''X''' || '''X'''<br />
<br />
|}<br />
<br />
<br />
==== Filters Configuration ====<br />
<br />
In some entities list (i.e., ticket views) it is possible to configure a personal filter by '''Filters''' button or to remove it by '''Drop Filter''' button:<br />
<br />
[[File:Filter button.JPG|centre|thumb|900x900px|Filter Management buttons]]<br />
<br />
The filter management form contains following common sections:<br />
* Personal Filter Manager<br />
* Global Settings<br />
* Main Section<br />
* Primay and Secondary Section<br />
<br />
and specific block sections for every entity views.<br />
<br />
<br />
<br />
<br />
===== Personal Filter Manager =====<br />
<br />
Section to create, delete or update personal filters. It is enabled by clicking on '''Personal Filter Manager''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Action</u> || Radio button ||<br />
* "Save As New": creates a new personal filter with name inserted in text field<br />
* "Save As": saves current personal filter selected by <u>Filter</u> field with name inserted in text field <br />
* "Update Existing": saves current personal filter selected by <u>Filter</u> field without select<br />
<br />
|-<br />
|<u>Default</u> || Check box || defines the current personal filter selected by <u>Filter</u> as default in view<br />
<br />
|-<br />
|'''Save''' || Button || saves personal filter defined in <u>Action</u> field<br />
<br />
|-<br />
|'''Delete''' || Button || deletes current filter selected by <u>Filter</u> field<br />
<br />
|}<br />
<br />
===== Global Settings =====<br />
<br />
Section to manage primary filter blocks. It is enabled by clicking on '''Global Settings''' button.<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Primary Blocks Settings</u> || Check box || hides primary filter blocks (i.e., <u>Project Block</u>, <u>Ticket Type Block</u>, <u>Ticket Statuses Block</u> for ''ticket'' filter) that are checked<br />
<br />
|-<br />
|<u>Primay Block Hierarchy</u> || Radio button || the following choises are possible: <br />
* <u>No Hierarchy</u><br />
* <u>Project and Services / ''[[GLOSSARY|Ticket Types]]'' / Operational Statuses</u><br />
* <u>''[[GLOSSARY|Ticket Types]]'' / Project and Services / Operational Statuses</u> <br />
|-<br />
|'''Save''' || Button || saves '''''Global Settings''''' configuration<br />
|}<br />
<br />
===== Main Section =====<br />
<br />
Section to configure main filter settings (paging, refreshing, etc...).<br />
<br />
{| class="wikitable"<br />
! Field !! Type !! Description<br />
<br />
|-<br />
|<u>Per Page</u> || List box || defines items number ("10", "20", "50", "100", "Show All") that can be visible in a single view page<br />
<br />
|-<br />
|<u>Ticket Code Range</u> || Text field || list of ticket codes (separated by a space char) that user can visualize<br />
<br />
|-<br />
|<u>Refresh Frequency</u> || List box || defines the temporal frequency ("30 sec", "1 min", "2 min", "3 min", "5 min") with which items view is refreshed. The "0 sec(off)" value disables this functionality.<br />
<br />
|-<br />
|<u>Disable Smart Loading</u> || Check box || if unchecked it enables block filter fields loading according to the visibility that logged user can have on some itmSUITE® items<br />
<br />
|-<br />
|<u>Disable Cascade Refresh</u> || Check box || if unchecked it enables cascade options refresh for all filter blocks. If checked it enables asynchronous refreshing by '''Refresh''' button (to refresh selected filter block) or by '''Refresh All''' button (to update all visible filter blocks)<br />
<br />
|-<br />
|<u>Ticket Creation Dates Options</u> || Radio button || creation date filtering:<br />
* From - To: shows items according to setted creation date range<br />
* Quick Date Option: shows items according to setted current or last N (N setted in <u>Units</u> field) days, months, years.<br />
|}<br />
<br />
<br />
===== Primary and Secondary Section =====<br />
<br />
In these sections, every block filter can be hidden/visibile by a check box.<br />
In '''''Primary Section''''' block filter fields are always loaded when users opens the '''''Filter''''' menu.<br />
In '''''Secondary Section''''' only checked block filter fields are asynchronously loaded.<br />
<br />
{| class="wikitable"<br />
! Filter!! Block !! Section !! Description<br />
<br />
|-<br />
|<u>Project(s)</u> || '''''Projects and Services''''' || Primary || multiselected filter for ''project''and ''Service'' name<br />
<br />
|-<br />
|<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status<br />
<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Service_Management&diff=3965Service Management2018-06-14T10:51:56Z<p>Francesco.bertuletti: /* Service Management */</p>
<hr />
<div>== Service Management ==<br />
SM - Service Management is one of the core modules of itmSUITE®. In itmSUITE® a ''Service'' is linked on a different modules and function to realize a complete management of the ''Service''. The table below shown the main relationship:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Service definition || This entity is the ''instance'' of the Business or Technical service in the system<br />
|-<br />
| Process definition || The interaction between ''Service'' and ''Customer'' is supported by ''[[Glossary|Worflow]]''.<br />
|-<br />
| Cost & Benefit analysis || To support the service activity ''resources'' are a key component. The system tracks costs & revenue.<br />
|-<br />
| Service Catalogue || This entity ,is supported by ''[[Glossary|SRCS]]'', enable the user to activate the process.<br />
|}<br />
<br />
=== Service Defintion ===</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Service_Management&diff=3964Service Management2018-06-14T10:48:41Z<p>Francesco.bertuletti: Created page with "== Service Management == SM - Service Management is one of the core modules of itmSUITE®. In itmSUITE® a ''Service'' is linked on a different modules and function to realize..."</p>
<hr />
<div>== Service Management ==<br />
SM - Service Management is one of the core modules of itmSUITE®. In itmSUITE® a ''Service'' is linked on a different modules and function to realize a complete management of the ''Service''. The table below shown the main relationship:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Service definition || This entity is the ''instance'' of the Business or Technical service in the system<br />
|-<br />
| Process definition || The interaction between ''Service'' and ''Customer'' is supported by ''[[Glossary|Worflow]]''.<br />
|-<br />
| Cost & Benefit analysis || To support the service activity ''resources'' are a key component. The system tracks costs & revenue.<br />
|-<br />
| Service Catalogue || This entity ,is supported by ''[[Glossary|SRCS]]'', enable the user to activate the process.<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Message_system&diff=3963Message system2018-06-14T09:52:47Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE PMSM can be configured to interact with external mailboxes (sending and receiving mail).<br />
<br />
=== Company Configuration ===<br />
In General\Company\Company Info is possible to configure:<br />
<br />
* Transfer Protocol: an SMTP address to allow PMSM to send mail<br />
* Store Protocol: one or more mailboxes to be checked by PMSM<br />
<br />
<br />
[[File:Message Schema.jpg|centre|thumb|500x500px|itmSUITE Message System]]<br />
<br />
=== Message Function ===<br />
This funtion enable the user to:<br />
#<b>Add</b> new message<br />
#<b>Replay</b> to a message<br />
#<b>Forward</b> a message<br />
<br />
The most important feature developped in this function is the ability to select the mail ''receiver'' based on the role he/she play on the entity. So when the mail is sent from a:<br />
{| class="wikitable"<br />
! Entity!! Receiver<br />
|-<br />
| Ticket || Ticket Request, Ticket Owner, Solution Groups Member or Manager, Ticket Worker, Service Owner<br />
|-<br />
| Sale Contract || Sale Contract creator, Project Manager, All active record<br />
|-<br />
| Project/Service || Project/Service creator, Project Manager, Project/Service Manager<br />
|}<br />
In any case is still possible to send massage to specific mail inserting the mail address in "Other recipient" field.</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Message_system&diff=3962Message system2018-06-14T09:51:20Z<p>Francesco.bertuletti: /* Message Function */</p>
<hr />
<div>itmSUITE PMSM can be configured to interact with external mailboxes (sending and receiving mail).<br />
<br />
=== Company Configuration ===<br />
In General\Company\Company Info is possible to configure:<br />
<br />
* Transfer Protocol: an SMTP address to allow PMSM to send mail<br />
* Store Protocol: one or more mailboxes to be checked by PMSM<br />
<br />
<br />
[[File:Message Schema.jpg|centre|thumb|500x500px|itmSUITE Message System]]<br />
<br />
=== Message Function ===<br />
This funtion enable the user to:<br />
#<b>Add</b> new message<br />
#<b>Replay</b> to a message<br />
#<b>Forward</b> a message<br />
<br />
The most important feature developped in this function is the ability to select the mail ''receiver'' based on the role he/she play on the entity. So when the mail is sent from a:<br />
{| class="wikitable"<br />
! Entity!! Receiver<br />
|-<br />
| "Ticket" || Ticket Request, Ticket Owner, Solution Groups Member or Manager, Ticket Worker, Service Owner<br />
|-<br />
| "Sale Contract" || Sale Contract creator, Project Manager, All active record<br />
|-<br />
| "Service" || Project/Service creator, Project Manager, Project/Service Manager<br />
|}<br />
In any case is still possible to send massage to specific mail inserting the mail address in "Other recipient" field.</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Message_system&diff=3961Message system2018-06-14T09:39:58Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE PMSM can be configured to interact with external mailboxes (sending and receiving mail).<br />
<br />
=== Company Configuration ===<br />
In General\Company\Company Info is possible to configure:<br />
<br />
* Transfer Protocol: an SMTP address to allow PMSM to send mail<br />
* Store Protocol: one or more mailboxes to be checked by PMSM<br />
<br />
<br />
[[File:Message Schema.jpg|centre|thumb|500x500px|itmSUITE Message System]]<br />
<br />
=== Message Function ===<br />
This funtion enable the user to:<br />
#<b>Add</b> new message<br />
#<b>Replay</b> to a message<br />
#<b>Forward</b> a message</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Client_Management&diff=3960Client Management2018-06-14T09:36:39Z<p>Francesco.bertuletti: </p>
<hr />
<div>== Client ==<br />
All the functions present enable an application manager to set:<br />
# Client Master data<br />
# Sales Contract<br />
<br />
== Client Master Data ==<br />
The client management functions are available in <b>''/Clients Management/Clients/Clients''</b><br />
<br />
This function enable the itmSUITE® ''Manager'' to <b>Add</b>, <b>Copy</b> or <b>Delete</b> a ''Client''.<br />
<br />
=== Add a new Client ===<br />
<br />
The Client form present five tabs:<br />
# General <br />
# Addresses<br />
# Contacts<br />
# Bank Accounts<br />
# Organization Units<br />
<br />
here below the list of fields present into the ''Client'' session.<br />
<br />
{| class="wikitable"<br />
! General tab fields!! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Client name<br />
|-<br />
| "Client group" || This Field enable to set the Client father if exists<br />
|-<br />
| "AII" || All Invoice Issued. Is a mandatory field to set before ''Closing'' or ''Deleting'' a ''Client''<br />
|-<br />
| "Status" || This field identify the ''client' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Provisory || Initial status of Client enable the ''Manager'' to set all the properties<br />
|-<br />
| Billable || Status to set if the Client will be ''invoiced''<br />
|-<br />
| Inactive || Status to set if the Client Invoicing process has to be suspended<br />
|-<br />
| Cancelled || Status to set if the Client is no more operational<br />
|}<br />
|-<br />
| "Type" || This is an attribute of the ''client''. The master data for this field are present in <b>''/General/Company/Client Type''</b>.<br />
|-<br />
| "Country" || This is an attribute of the ''client''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Language" || This is an attribute of the ''client''. The master data for this field are present in <b>''/General/Company/Languages''</b>.<br />
|-<br />
| "Tax Number" || This Field enable to set the Client Tax Number information<br />
|-<br />
| "Payment terms" || This Field enable to set the Payment terms. The master data for this field are present in <b>''/General/Company/Payment terms''</b>. <br />
|-<br />
| "Notes" || This Field enable specify some note of client.<br />
|}<br />
<br />
For each ''[[Glossary|client]]'' is possible to set different <u>''Address''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the client's city<br />
|-<br />
| "Postal code" || Used to indicate the client's postal code<br />
|-<br />
| "District" || Used to indicate the client's province<br />
|-<br />
| "Region" || Used to indicate the client's region<br />
|-<br />
| "Phone" || Used to indicate the client's phone number. This should be specific by client address type, "Headquarters", "Order"<br />
|-<br />
| "Type" || This is an attribute of the ''client''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "Mobile" || Used to indicate the client's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the client's fax number. <br />
|-<br />
| "Email" || Used to indicate the client's Email information. <br />
|-<br />
| "Note" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''client''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be copied in the ''[[Glossary|Ticket]]'' user information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''[[Glossary|client]]'' is possible to set different <u>''Contacts''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Contact tab fields!! Description<br />
|-<br />
| "Name" || Contact name<br />
|-<br />
| "Surname" || Contact surname<br />
|-<br />
| "Role" || Role played by the contact at ''[[Glossary|client]]'‘ side<br />
|-<br />
| "Notes" || Contact generic information<br />
|-<br />
| "Contact Type" || This is an attribute of the contact. The master data for this field are present in <b>''/General/Company/Contact Type''</b>.<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "Address City" || Used to indicate the client's city<br />
|-<br />
| "Address Postal code" || Used to indicate the client's postal code<br />
|-<br />
| "Address Region" || Used to indicate the client's region<br />
|-<br />
| "Address Phone" || Used to indicate the client's phone number. This should be specific by client address type, "Headquarters", "Order"<br />
|-<br />
| "Address Type" || This is an attribute of the ''client'' the master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "Address Fax" || Used to indicate the client's fax number. <br />
|-<br />
| "Address Email" || Used to indicate the client's Email information. <br />
|-<br />
| "Country" || This is an attribute of the ''client'' the master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Invoice" || if flagged this contact will be used by the billing process<br />
|-<br />
| "Default" || if flagged this contact will be proposed as default contact.<br />
|}<br />
<br />
For each ''[[Glossary|client]]'' is possible to set different <u>''Bank Accounts''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Bank Account tab fields!! Description<br />
|-<br />
| "Bank Name" || Bank name<br />
|-<br />
| "Account Number" || Account number<br />
|-<br />
| "Agency" || Name of the bank agency the account is opened<br />
|-<br />
| "CIN" || Set here the first 5 digit of IBAN account<br />
|-<br />
| "ABI" || Set here the ABI code<br />
|-<br />
| "CAB" || Set here the CAB code<br />
|-<br />
| "Notes" || Contact generic information<br />
|-<br />
| "Contact Type" || This is an attribute of the contact. The master data for this field are present in <b>''/General/Company/Contact Type''</b>.<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "Address City" || Used to indicate the client's city<br />
|-<br />
| "Address Postal code" || Used to indicate the client's postal code<br />
|-<br />
| "Address Region" || Used to indicate the client's region<br />
|-<br />
| "Address Phone" || Used to indicate the client's phone number. This should be specific by client address type, "Headquarters", "Order"<br />
|-<br />
| "Address Fax" || Used to indicate the client's fax number. <br />
|-<br />
| "Address Email" || Used to indicate the client's Email information. <br />
|-<br />
| "Address Notes" || Contact generic information<br />
|-<br />
| "Country" || This is an attribute of the ''client'' the master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this bank account will be proposed as default.<br />
|}<br />
<br />
For each ''[[Glossary|client]]'' is possibile to the ''[[Glossary|Organization Unit]]'' Structure. For more detail how to manage this information refer to: ''[[OU_Management|Organization Unit]]''<br />
<br />
=== Copy a Client ===<br />
To create a new client as a copy of an existing, is necessary to select a ''Client'' using the check box present near the client and select the <b>COPY</b> button.<br />
<br />
The new ''Client'' is named like "Client Name_copy" and is created in status ''Provisory''.<br />
<br />
The itmSUITE® ''Manager'', can then modify the record and complete the information.<br />
<br />
=== Delete a Client ===<br />
The client deletion is a logical operation. Before delete the client the Manager has to declare that All the Invoice has been Issue (AII)and set the status to Inactive or Cancelled<br />
<br />
<br />
== Sales Contract ==<br />
<br />
The Sales Contract Management functions are available in <b>''/Clients Management/Sale Contract/Sale Contracts''</b><br />
<br />
This function enables the itmSUITE® Manager to <b>Add</b>, <b>Delete</b> a Sale Contract.<br />
<br />
itmSUITE® provide main types of contract:<br />
# Fixed Price contract<br />
# Time & Material<br />
<br />
The differences between them is the management of contract values. Fixed Price contract", expects a contract fixed amount and a billing schedule to allocate the amount on an income plan;<br />
"Time & Material", expects to specify the Sales role tariff.<br />
<br />
Both contracts can be associate to a '[[Glossary|Project]]'' or a '[[Glossary|Service]]''. Fixed Price can be defined as Stand Alone contract and invoiced directly to a client.<br />
<br />
Time Material contract can be differentiated by the Expanses Management:<br />
# Documented<br />
# Fixed<br />
# None<br />
<br />
Sale contract form presents six tabs:<br />
<br />
# General<br />
# Role tariff<br />
# Billing Schedule<br />
# Documents<br />
# Project references<br />
# Messages<br />
<br />
<br />
Sale contract <u>''General''</u> tab contains the main contract information. The list of fields is shown in the following table:<br />
<br />
{| class="wikitable"<br />
! General tab fields!! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''client' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Provisory || Initial status of Sale Contract enable the ''Manager'' to set all the properties<br />
|-<br />
| Operational ||in this status the contract is fully available for the system<br />
|-<br />
| Suspended || Status to set to suspend the contract to invoice process.<br />
|-<br />
| Cancelled || Contract will be no more used by system. If there is a '[[Glossary|Project]]'' or a '[[Glossary|Service]]'' in status different from closed a warning message will be shown.<br />
|-<br />
| Closed || Contract will be no more used by system. Managers can set this status only if the AII flag is selected.<br />
|}<br />
|-<br />
| "Code" || Internal contract number. Non editable.<br />
|-<br />
| "Contract Date" || This field record the date the contract has been signed.<br />
|-<br />
| "Term Start Date" || This field record the Initial contract validity date<br />
|-<br />
| "Term End Date" || This field record the End contract validity date<br />
|-<br />
| "Name" || This field record contract name<br />
|-<br />
| "Description" || This field record contract description<br />
|-<br />
| "Client" || This field set the client the sale contract belongs too.<br />
|-<br />
| "Internal contract referent" || Company internal sale contract referent<br />
|-<br />
| "Client contract referent" || Client sales referent<br />
|-<br />
| "Bank Name" || This field set the bank information related to the sale contract. By default, itmSUITE® valorised it with the default Client bank account information. <br />
|-<br />
| "Payment Terms" || This field set the payment terms related to the sale contract. By default, itmSUITE® valorised it with the Client payment terms information. <br />
|-<br />
| "Currency" || This field set currency information<br />
|-<br />
| "Expenses Type" || This field identify the ''Contract' expenses management type. Values are:<br />
{| class="wikitable"<br />
! Expenses type!! Description<br />
|-<br />
| "Documented" || if selected the resource can record in ''[[Glossary|Timesheet]]'' the travel expenses. Sales contract enable the ''Manager'' to set a maximum amount of expense for each travel expense.<br />
|-<br />
| "Fixed" ||if selected a "per Day" forfait value can be invoiced to client.<br />
|-<br />
| "None" || if selected the contract doesn't allow to insert expenses.<br />
|}<br />
|-<br />
| "Fixed Expenses per Day"|| This field can be valorised when the "Fixed" Expensed Type is selected<br />
|-<br />
| "KM Tariff" || The following list of fields can be valorised when the "Documented" Expensed Type is selected. Set the default tariff for a KM declared on ''[[Glossary|Timesheet]]'' record<br />
|-<br />
| "KM Tariff Max"|| Used to check the maximum value that can be declared on ''[[Glossary|Timesheet]]'' record<br />
|-<br />
| "Travel Expenses Max"|| Used to check the maximum value that can be invoiced by contract <br />
|-<br />
| "Hotel Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Dinner Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Lunch Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Fixed Price for Services"|| if flagged the "Total Services Fixed Amount" field become available.<br />
|-<br />
| "Use Billing Schedule"|| Automatically flagged when "Fixed Price for Services" is selected<br />
|-<br />
| "Billing Rule"|| Not Editable when "Use Billing schedule" is selected enable the ''Manager'' to choose the billing policy between:<br />
{| class="wikitable"<br />
! Billing Rule!! Description<br />
|-<br />
| "Definied Month Day" || If selected itmSUITE® ask to set the day of the Month in "Billing day"<br />
|-<br />
| "First Day of Month" || If selected itmSUITE® set the first Day of the month as Invoice date<br />
|-<br />
| "Last Day of Month" || If selected itmSUITE® set the last Day of the month as Invoice date<br />
|}<br />
|-<br />
| "Billing Rule Description"|| General description<br />
|-<br />
| "VAT Percentage"|| insert the percentage Number. This will percentage will be used for the Billing process<br />
|-<br />
| "AII"|| All Invoice Issued. This flag should be settled if we want to close the contract<br />
|-<br />
| "Allow Extra work"|| Only if flagged an extra work tariff can be charge to client<br />
|-<br />
| "Stand Alone"|| if flagged the sale contract can be invoice also if not associated to '[[Glossary|Project]]'' or a '[[Glossary|Service]]''<br />
|}<br />
<br />
For each ''[[Glossary|Sale Contract]]'' is possible to set different <u>''Role Tariff''</u>. Role Tariff is linked to a Resource that perform ''[[Glossary|Timesheet]]'' via the Resource "Sale Role" field.<br />
<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Role Tariff tab fields!! Description<br />
|-<br />
| "Sale Role" || Bank name<br />
|-<br />
| "Daily Tariff" || Daily Tariff amount<br />
|-<br />
| "Allow Extrawork" || if flagged, itmSUITE®, take in account for the bill calculation also the Extrawork tariffs and amount. Extrawork should be authorized at ''[[Glossary|Company]]'' level<br />
{| class="wikitable"<br />
! Extra work !! Description<br />
|-<br />
| "Maximal Extrawork amount allowed" || Maximum value reachable per contract<br />
|-<br />
| "Use percents for extrawork" || If selected itmSUITE® consider the "Extrawork tariff" value as percentage<br />
|-<br />
| "Extrawork tariff" || Amount or percentage based on "Use percents for extrawork" selection<br />
|}<br />
<br />
|}<br />
<br />
For each Sale Contract is possible to set different ''[[Glossary|Billing Schedule]]''. ''Billing Schedule'' is necessary for Standalone and Fixed Price contract.<br />
<br />
The session enables the user to Add, Delete or Print the list of address.<br />
<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Billing Schedule tab fields!! Description<br />
|-<br />
| "Total Services Fixed Amount" || Value of the Sales Contract<br />
|-<br />
| "Total Amount" || Value of the Billing Schedule records<br />
|-<br />
| "Delta" || Difference between "Total Amount" and "Total Services Fixed Amount"<br />
|-<br />
| Billing Schedule || Grid section with a Summary information of ''[[Glossary | Billing Schedule]]''<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Billing Schedule!! Description<br />
|-<br />
| "Description" || Billing schedule description<br />
|-<br />
| "Invoice Description" || Billing schedule description reported into the invoice<br />
|-<br />
| "Date" || Billing schedule date.<br />
|-<br />
| "Amount" || Billing schedule Amount.<br />
|-<br />
| "Billed Flag" || Valorised from the ‘'[[Glossary|Billing]]'' process. If checked the billing schedule has been invoiced<br />
|-<br />
| "Depends on Delivery" || Valorised automatically if the billability of this schedule depends by a project / service ''[[Glossary|Delivery]]''<br />
<br />
The Delivery list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Delivery information!! Description<br />
|-<br />
| "Project code" || Project / Service code the Delivery belongs too.<br />
|-<br />
| "Project Name" || Project / Service Name the Delivery belongs too.<br />
|-<br />
| "Name" || Delivery Name.<br />
|-<br />
| "Expected Delivery" || Scheduled Date of Delivery.<br />
|-<br />
| "Actual Delivery" || Actual Date of Delivery. This date certify that the delivery has been performed.<br />
|}<br />
<br />
|}<br />
<br />
|}<br />
<br />
For each Sale Contract is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identify the area of the document. The Topic follow the document taxonomy<br />
|-<br />
| "Type" || Identify the type of document. The Type follow the document taxonomy.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database, default option, or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || Only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
<u> Project References tab </u> shown all the ''project''/''Service'' where the ''sale contract'' is used. <br />
<br />
<u>Messages</u> tab can be used to send / store at sale contract level all the important message. For further detail about message system refer to ''[[Message system]]''</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Supplier_Management&diff=3959Supplier Management2018-06-14T09:31:18Z<p>Francesco.bertuletti: </p>
<hr />
<div>== Supplier ==<br />
All the functions present enable an application manager to set:<br />
# Supplier Master data<br />
# Purchase Contract<br />
<br />
== Supplier Master Data ==<br />
The Supplier management functions are available in <b>''/Supplier Management/Suppliers/Suppliers''</b><br />
<br />
This function enable the itmSUITE® ''Manager'' to <b>Add</b>, <b>Copy</b> or <b>Delete</b> a ''Supplier''.<br />
<br />
=== Add a new Supplier ===<br />
<br />
The Supplier form present five tabs:<br />
# General <br />
# Addresses<br />
# Contacts<br />
# Bank Accounts<br />
<br />
here below the list of fields present into the ''Supplier'' session.<br />
<br />
{| class="wikitable"<br />
! General tab fields!! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Supplier name<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Provisory || Initial status of Supplier enable the ''Manager'' to set all the properties<br />
|-<br />
| Billable || Status to set if the Supplier will be ''invoiced''<br />
|-<br />
| Inactive || Status to set if the Supplier Invoicing process has to be suspended<br />
|-<br />
| Cancelled || Status to set if the Supplier is no more operational<br />
|}<br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Language" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Languages''</b>.<br />
|-<br />
| "Tax Number" || This Field enable to set the Supplier Tax Number information<br />
|-<br />
| "Payment terms" || This Field enable to set the Payment terms. The master data for this field are present in <b>''/General/Company/Payment terms''</b>. <br />
|}<br />
<br />
For each ''[[Glossary|supplier]]'' is possible to set different <u>''Address''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Note" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''[[Glossary|supplier]]'' is possible to set different <u>''Contacts''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Contact tab fields!! Description<br />
|-<br />
| "Name" || Contact name<br />
|-<br />
| "Surname" || Contact surname<br />
|-<br />
| "Role" || Role played by the contact at ''[[Glossary|supplier]]'‘ side<br />
|-<br />
| "Notes" || Contact generic information<br />
|-<br />
| "Contact Type" || This is an attribute of the contact. The master data for this field are present in <b>''/General/Company/Contact Type''</b>.<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "Address City" || Used to indicate the supplier's city<br />
|-<br />
| "Address Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "Address Region" || Used to indicate the supplier's region<br />
|-<br />
| "Address Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Address Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Address Type" || This is an attribute of the ''supplier'' the master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Address Notes" || Address contact generic information. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier'' the master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this contact will be proposed as default contact.<br />
|}<br />
<br />
For each ''[[Glossary|supplier]]'' is possible to set different <u>''Bank Accounts''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Bank Account tab fields!! Description<br />
|-<br />
| "Bank Name" || Bank name<br />
|-<br />
| "Account Number" || Account number<br />
|-<br />
| "Agency" || Name of the bank agency the account is opened<br />
|-<br />
| "CIN" || Set here the first 5 digit of IBAN account<br />
|-<br />
| "ABI" || Set here the ABI code<br />
|-<br />
| "CAB" || Set here the CAB code<br />
|-<br />
| "Notes" || Contact generic information<br />
|-<br />
| "Contact Type" || This is an attribute of the contact. The master data for this field are present in <b>''/General/Company/Contact Type''</b>.<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "Address City" || Used to indicate the supplier's city<br />
|-<br />
| "Address Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "Address Region" || Used to indicate the supplier's region<br />
|-<br />
| "Address Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Address Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Address Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Address Notes" || Contact generic information<br />
|-<br />
| "Country" || This is an attribute of the ''supplier'' the master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this bank account will be proposed as default.<br />
|}<br />
<br />
=== Copy a Supplier ===<br />
To create a new supplier as a copy of an existing, is necessary to select a ''Supplier'' using the check box present near the supplier and select the <b>COPY</b> button.<br />
<br />
The new ''supplier'' is named like "Supplier Name_copy" and is created in status ''Provisory''.<br />
<br />
The itmSUITE® ''Manager'', can then modify the record and complete the information.<br />
<br />
=== Delete a Supplier ===<br />
The supplier deletion is a logical operation. <br />
<br />
== Purchase Contract ==<br />
<br />
The Purchase Contract Management functions are available in <b>''/Supplier Management/Purchase Contracts/Purchase Contracts''</b><br />
<br />
This function enables the itmSUITE® Manager to <b>Add</b>, <b>Delete</b> a Purchase Contract.<br />
<br />
itmSUITE® provide Time & Material Types of contract, with the possibility to manage the different type of manage Expenses.<br />
<br />
"Time & Material", contract expects to specify the Purchase role tariff. Purchase contract must be associate to a '[[Glossary|Project]]'' or a '[[Glossary|Service]]''. <br />
<br />
Time Material contract can be differentiated by the Expanses Management:<br />
<br />
<br />
Purchase contract form presents five tabs:<br />
<br />
# General<br />
# Roles<br />
# Resources<br />
# Documents<br />
# Project references<br />
<br />
<br />
Purchase contract <u>''General''</u> tab contains the main contract information. The list of fields is shown in the following table:<br />
<br />
{| class="wikitable"<br />
! General tab fields!! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Provisory || Initial status of Purchase Contract enable the ''Manager'' to set all the properties<br />
|-<br />
| Operational ||in this status the contract is fully available for the system<br />
|-<br />
| Cancelled || Contract will be no more used by system. If there is a '[[Glossary|Project]]'' or a '[[Glossary|Service]]'' in status different from closed a warning message will be shown.<br />
|-<br />
| Closed || Contract will be no more used by system. Managers can set this status only if the AII flag is selected.<br />
|}<br />
|-<br />
| "Code" || Internal contract number. Non editable.<br />
|-<br />
| "Contract Date" || This field record the date the contract has been signed.<br />
|-<br />
| "Term Start Date" || This field record the Initial contract validity date<br />
|-<br />
| "Term End Date" || This field record the End contract validity date<br />
|-<br />
| "Name" || This field record contract name<br />
|-<br />
| "Description" || This field record contract description<br />
|-<br />
| "Supplier" || This field set the supplier the purchase contract belongs too.<br />
|-<br />
| "Supplier Contract code" || This field set a cross reference with the supplier organization<br />
|-<br />
| "Supplier contract referent" || Supplier referent<br />
|-<br />
| "Bank Name" || This field set the bank information related to the purchase contract. By default, itmSUITE® valorised it with the default Supplier bank account information. <br />
|-<br />
| "Payment Terms" || This field set the payment terms related to the purchase contract. By default, itmSUITE® valorised it with the supplier payment terms information. <br />
|-<br />
| "Currency" || This field set currency information<br />
|-<br />
| "Expenses Type" || This field identify the ''Contract' expenses management type. Values are:<br />
{| class="wikitable"<br />
! Expenses type!! Description<br />
|-<br />
| "Documented" || if selected the resource can record in ''[[Glossary|Timesheet]]'' the travel expenses. Purchase contract enable the ''Manager'' to set a maximum amount of expense for each travel expense.<br />
|-<br />
| "Fixed" ||if selected a "per Day" forfait value can be invoiced to client.<br />
|-<br />
| "None" || if selected the contract doesn't allow to insert expenses.<br />
|}<br />
|-<br />
| "Fixed Expenses per Day"|| This field can be valorised when the "Fixed" Expensed Type is selected<br />
|-<br />
| "KM Tariff" || The following list of fields can be valorised when the "Documented" Expensed Type is selected. Set the default tariff for a KM declared on ''[[Glossary|Timesheet]]'' record<br />
|-<br />
| "KM Tariff Max"|| Used to check the maximum value that can be declared on ''[[Glossary|Timesheet]]'' record<br />
|-<br />
| "Travel Expenses Max"|| Used to check the maximum value that can be invoiced by contract <br />
|-<br />
| "Hotel Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Dinner Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Lunch Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Allow Extra work"|| Only if flagged an extra work tariff can be charge to the organization<br />
|}<br />
<br />
For each ''[[Glossary|Purchase Contract]]'' is possible to set different <u>''Roles Tariff''</u>. Role Tariff is linked to a Resource that perform ''[[Glossary|Timesheet]]'' via the Resource "Purchase Role" field.<br />
<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Role Tariff tab fields!! Description<br />
|-<br />
| "Role" || Purchase role name<br />
|-<br />
| "Daily Tariff" || Daily Tariff amount<br />
|-<br />
| "Fixed Expenses Amount" || Forfait expense Amount<br />
|}<br />
<br />
For each Purchase Contract is possible to set different ''[[Glossary|Resources]]''. ''Resources" can play multiple roles, so each ''[[Glossary|timesheet]]'' can be charged in differnt way.<br />
<br />
The session enables the user to Add, Delete or Print the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Resources tab fields!! Description<br />
|-<br />
| "Resources" || Select the record that belongs to the Supplier<br />
|-<br />
| "Contribution %" || Set the percentage of additional contribution to be invoice to the Supplier as Security Tax.<br />
|-<br />
| Roles || Grid section with a Summary information of ''[[Glossary | Purchase Role]]''<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Role!! Description<br />
|-<br />
| "Role" || Purchase Role description<br />
|-<br />
| "Abbreviation" || Purchase role code<br />
|-<br />
| "Cost per Day" || Tariff associate to the purchase role<br />
|-<br />
| "Fixed Expenses Amount" || Forfait expense Amount.<br />
|-<br />
| "Default Flag" || if valorised this tariff will be shown as default on Timesheet registration<br />
|-<br />
| "Use for Budget Flag" || if valorised this purchase tariff will be used to evaluate the budget effort in project / service estimation and in Ticket Estimation<br />
|}<br />
<br />
|}<br />
<br />
For each Purchase Contract is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identify the area of the document. The Topic follow the document taxonomy<br />
|-<br />
| "Type" || Identify the type of document. The Type follow the document taxonomy.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database, default option, or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || Only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
<u> Project References tab </u> shown all the ''project''/''Service'' where the ''purchase contract'' is used.</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Supplier_Management&diff=3958Supplier Management2018-06-14T09:16:14Z<p>Francesco.bertuletti: </p>
<hr />
<div>== Supplier ==<br />
All the functions present enable an application manager to set:<br />
# Supplier Master data<br />
# Purchase Contract<br />
<br />
== Supplier Master Data ==<br />
The Supplier management functions are available in <b>''/Supplier Management/Suppliers/Suppliers''</b><br />
<br />
This function enable the itmSUITE® ''Manager'' to <b>Add</b>, <b>Copy</b> or <b>Delete</b> a ''Supplier''.<br />
<br />
=== Add a new Supplier ===<br />
<br />
The Supplier form present five tabs:<br />
# General <br />
# Addresses<br />
# Contacts<br />
# Bank Accounts<br />
<br />
here below the list of fields present into the ''Supplier'' session.<br />
<br />
{| class="wikitable"<br />
! General tab fields!! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Supplier name<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Provisory || Initial status of Supplier enable the ''Manager'' to set all the properties<br />
|-<br />
| Billable || Status to set if the Supplier will be ''invoiced''<br />
|-<br />
| Inactive || Status to set if the Supplier Invoicing process has to be suspended<br />
|-<br />
| Cancelled || Status to set if the Supplier is no more operational<br />
|}<br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Language" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Languages''</b>.<br />
|-<br />
| "Tax Number" || This Field enable to set the Supplier Tax Number information<br />
|-<br />
| "Payment terms" || This Field enable to set the Payment terms. The master data for this field are present in <b>''/General/Company/Payment terms''</b>. <br />
|}<br />
<br />
For each ''[[Glossary|supplier]]'' is possible to set different <u>''Address''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Note" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''[[Glossary|supplier]]'' is possible to set different <u>''Contacts''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Contact tab fields!! Description<br />
|-<br />
| "Name" || Contact name<br />
|-<br />
| "Surname" || Contact surname<br />
|-<br />
| "Role" || Role played by the contact at ''[[Glossary|supplier]]'‘ side<br />
|-<br />
| "Notes" || Contact generic information<br />
|-<br />
| "Contact Type" || This is an attribute of the contact. The master data for this field are present in <b>''/General/Company/Contact Type''</b>.<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "Address City" || Used to indicate the supplier's city<br />
|-<br />
| "Address Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "Address Region" || Used to indicate the supplier's region<br />
|-<br />
| "Address Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Address Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Address Type" || This is an attribute of the ''supplier'' the master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Address Notes" || Address contact generic information. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier'' the master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this contact will be proposed as default contact.<br />
|}<br />
<br />
For each ''[[Glossary|supplier]]'' is possible to set different <u>''Bank Accounts''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Bank Account tab fields!! Description<br />
|-<br />
| "Bank Name" || Bank name<br />
|-<br />
| "Account Number" || Account number<br />
|-<br />
| "Agency" || Name of the bank agency the account is opened<br />
|-<br />
| "CIN" || Set here the first 5 digit of IBAN account<br />
|-<br />
| "ABI" || Set here the ABI code<br />
|-<br />
| "CAB" || Set here the CAB code<br />
|-<br />
| "Notes" || Contact generic information<br />
|-<br />
| "Contact Type" || This is an attribute of the contact. The master data for this field are present in <b>''/General/Company/Contact Type''</b>.<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "Address City" || Used to indicate the supplier's city<br />
|-<br />
| "Address Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "Address Region" || Used to indicate the supplier's region<br />
|-<br />
| "Address Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Address Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Address Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Address Notes" || Contact generic information<br />
|-<br />
| "Country" || This is an attribute of the ''supplier'' the master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this bank account will be proposed as default.<br />
|}<br />
<br />
=== Copy a Supplier ===<br />
To create a new supplier as a copy of an existing, is necessary to select a ''Supplier'' using the check box present near the supplier and select the <b>COPY</b> button.<br />
<br />
The new ''supplier'' is named like "Supplier Name_copy" and is created in status ''Provisory''.<br />
<br />
The itmSUITE® ''Manager'', can then modify the record and complete the information.<br />
<br />
=== Delete a Supplier ===<br />
The supplier deletion is a logical operation. <br />
<br />
== Purchase Contract ==<br />
<br />
The Purchase Contract Management functions are available in <b>''/Supplier Management/Purchase Contracts/Purchase Contracts''</b><br />
<br />
This function enables the itmSUITE® Manager to <b>Add</b>, <b>Delete</b> a Purchase Contract.<br />
<br />
itmSUITE® provide Time & Material Types of contract, with the possibility to manage the different type of manage Expenses.<br />
<br />
"Time & Material", contract expects to specify the Purchase role tariff. Purchase contract must be associate to a '[[Glossary|Project]]'' or a '[[Glossary|Service]]''. <br />
<br />
Time Material contract can be differentiated by the Expanses Management:<br />
<br />
<br />
Purchase contract form presents five tabs:<br />
<br />
# General<br />
# Roles<br />
# Resources<br />
# Documents<br />
# Project references<br />
<br />
<br />
Purchase contract <u>''General''</u> tab contains the main contract information. The list of fields is shown in the following table:<br />
<br />
{| class="wikitable"<br />
! General tab fields!! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Provisory || Initial status of Purchase Contract enable the ''Manager'' to set all the properties<br />
|-<br />
| Operational ||in this status the contract is fully available for the system<br />
|-<br />
| Cancelled || Contract will be no more used by system. If there is a '[[Glossary|Project]]'' or a '[[Glossary|Service]]'' in status different from closed a warning message will be shown.<br />
|-<br />
| Closed || Contract will be no more used by system. Managers can set this status only if the AII flag is selected.<br />
|}<br />
|-<br />
| "Code" || Internal contract number. Non editable.<br />
|-<br />
| "Contract Date" || This field record the date the contract has been signed.<br />
|-<br />
| "Term Start Date" || This field record the Initial contract validity date<br />
|-<br />
| "Term End Date" || This field record the End contract validity date<br />
|-<br />
| "Name" || This field record contract name<br />
|-<br />
| "Description" || This field record contract description<br />
|-<br />
| "Supplier" || This field set the supplier the purchase contract belongs too.<br />
|-<br />
| "Supplier Contract code" || This field set a cross reference with the supplier organization<br />
|-<br />
| "Supplier contract referent" || Supplier referent<br />
|-<br />
| "Bank Name" || This field set the bank information related to the purchase contract. By default, itmSUITE® valorised it with the default Supplier bank account information. <br />
|-<br />
| "Payment Terms" || This field set the payment terms related to the purchase contract. By default, itmSUITE® valorised it with the supplier payment terms information. <br />
|-<br />
| "Currency" || This field set currency information<br />
|-<br />
| "Expenses Type" || This field identify the ''Contract' expenses management type. Values are:<br />
{| class="wikitable"<br />
! Expenses type!! Description<br />
|-<br />
| "Documented" || if selected the resource can record in ''[[Glossary|Timesheet]]'' the travel expenses. Purchase contract enable the ''Manager'' to set a maximum amount of expense for each travel expense.<br />
|-<br />
| "Fixed" ||if selected a "per Day" forfait value can be invoiced to client.<br />
|-<br />
| "None" || if selected the contract doesn't allow to insert expenses.<br />
|}<br />
|-<br />
| "Fixed Expenses per Day"|| This field can be valorised when the "Fixed" Expensed Type is selected<br />
|-<br />
| "KM Tariff" || The following list of fields can be valorised when the "Documented" Expensed Type is selected. Set the default tariff for a KM declared on ''[[Glossary|Timesheet]]'' record<br />
|-<br />
| "KM Tariff Max"|| Used to check the maximum value that can be declared on ''[[Glossary|Timesheet]]'' record<br />
|-<br />
| "Travel Expenses Max"|| Used to check the maximum value that can be invoiced by contract <br />
|-<br />
| "Hotel Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Dinner Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Lunch Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Allow Extra work"|| Only if flagged an extra work tariff can be charge to the organization<br />
|}<br />
<br />
For each ''[[Glossary|Purchase Contract]]'' is possible to set different <u>''Roles Tariff''</u>. Role Tariff is linked to a Resource that perform ''[[Glossary|Timesheet]]'' via the Resource "Purchase Role" field.<br />
<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Role Tariff tab fields!! Description<br />
|-<br />
| "Role" || Purchase role name<br />
|-<br />
| "Daily Tariff" || Daily Tariff amount<br />
|-<br />
| "Fixed Expenses Amount" || Forfait expense Amount<br />
|}<br />
<br />
For each Purchase Contract is possible to set different ''[[Glossary|Resources]]''. ''Resources" can play multiple roles, so each ''[[Glossary|timesheet]]'' can be charged in differnt way.<br />
<br />
The session enables the user to Add, Delete or Print the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Resources tab fields!! Description<br />
|-<br />
| "Resources" || Select the record that belongs to the Supplier<br />
|-<br />
| "Contribution %" || Set the percentage of additional contribution to be invoice to the Supplier as Security Tax.<br />
|-<br />
| Roles || Grid section with a Summary information of ''[[Glossary | Purchase Role]]''<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Role!! Description<br />
|-<br />
| "Role" || Purchase Role description<br />
|-<br />
| "Abbreviation" || Purchase role code<br />
|-<br />
| "Cost per Day" || Tariff associate to the purchase role<br />
|-<br />
| "Fixed Expenses Amount" || Forfait expense Amount.<br />
|-<br />
| "Default Flag" || if valorised this tariff will be shown as default on Timesheet registration<br />
|-<br />
| "Use for Budget Flag" || if valorised this purchase tariff will be used to evaluate the budget effort in project / service estimation and in Ticket Estimation<br />
|}<br />
<br />
|}<br />
<br />
For each Purchase Contract is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identify the area of the document. The Topic follow the document taxonomy<br />
|-<br />
| "Type" || Identify the type of document. The Type follow the document taxonomy.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database, default option, or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || Only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
<u> Purchase References tab </u> shown for each ''Purchase contract'' all the ''project'' where it is used.</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Supplier_Management&diff=3957Supplier Management2018-06-14T09:15:19Z<p>Francesco.bertuletti: </p>
<hr />
<div>== Supplier ==<br />
All the functions present enable an application manager to set:<br />
# Supplier Master data<br />
# Purchase Contract<br />
<br />
== Supplier Master Data ==<br />
The Supplier management functions are available in <b>''/Supplier Management/Suppliers/Suppliers''</b><br />
<br />
This function enable the itmSUITE® ''Manager'' to <b>Add</b>, <b>Copy</b> or <b>Delete</b> a ''Supplier''.<br />
<br />
=== Add a new Supplier ===<br />
<br />
The Supplier form present five tabs:<br />
# General <br />
# Addresses<br />
# Contacts<br />
# Bank Accounts<br />
<br />
here below the list of fields present into the ''Supplier'' session.<br />
<br />
{| class="wikitable"<br />
! General tab fields!! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Supplier name<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Provisory || Initial status of Supplier enable the ''Manager'' to set all the properties<br />
|-<br />
| Billable || Status to set if the Supplier will be ''invoiced''<br />
|-<br />
| Inactive || Status to set if the Supplier Invoicing process has to be suspended<br />
|-<br />
| Cancelled || Status to set if the Supplier is no more operational<br />
|}<br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Language" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Languages''</b>.<br />
|-<br />
| "Tax Number" || This Field enable to set the Supplier Tax Number information<br />
|-<br />
| "Payment terms" || This Field enable to set the Payment terms. The master data for this field are present in <b>''/General/Company/Payment terms''</b>. <br />
|}<br />
<br />
For each ''[[Glossary|supplier]]'' is possible to set different <u>''Address''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Note" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''[[Glossary|supplier]]'' is possible to set different <u>''Contacts''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Contact tab fields!! Description<br />
|-<br />
| "Name" || Contact name<br />
|-<br />
| "Surname" || Contact surname<br />
|-<br />
| "Role" || Role played by the contact at ''[[Glossary|supplier]]'‘ side<br />
|-<br />
| "Notes" || Contact generic information<br />
|-<br />
| "Contact Type" || This is an attribute of the contact. The master data for this field are present in <b>''/General/Company/Contact Type''</b>.<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "Address City" || Used to indicate the supplier's city<br />
|-<br />
| "Address Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "Address Region" || Used to indicate the supplier's region<br />
|-<br />
| "Address Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Address Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Address Type" || This is an attribute of the ''supplier'' the master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Address Notes" || Address contact generic information. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier'' the master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this contact will be proposed as default contact.<br />
|}<br />
<br />
For each ''[[Glossary|supplier]]'' is possible to set different <u>''Bank Accounts''</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Bank Account tab fields!! Description<br />
|-<br />
| "Bank Name" || Bank name<br />
|-<br />
| "Account Number" || Account number<br />
|-<br />
| "Agency" || Name of the bank agency the account is opened<br />
|-<br />
| "CIN" || Set here the first 5 digit of IBAN account<br />
|-<br />
| "ABI" || Set here the ABI code<br />
|-<br />
| "CAB" || Set here the CAB code<br />
|-<br />
| "Notes" || Contact generic information<br />
|-<br />
| "Contact Type" || This is an attribute of the contact. The master data for this field are present in <b>''/General/Company/Contact Type''</b>.<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "Address City" || Used to indicate the supplier's city<br />
|-<br />
| "Address Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "Address Region" || Used to indicate the supplier's region<br />
|-<br />
| "Address Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Address Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Address Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Address Notes" || Contact generic information<br />
|-<br />
| "Country" || This is an attribute of the ''supplier'' the master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Default" || if flagged this bank account will be proposed as default.<br />
|}<br />
<br />
=== Copy a Supplier ===<br />
To create a new supplier as a copy of an existing, is necessary to select a ''Supplier'' using the check box present near the supplier and select the <b>COPY</b> button.<br />
<br />
The new ''supplier'' is named like "Supplier Name_copy" and is created in status ''Provisory''.<br />
<br />
The itmSUITE® ''Manager'', can then modify the record and complete the information.<br />
<br />
=== Delete a Supplier ===<br />
The supplier deletion is a logical operation. <br />
<br />
== Purchase Contract ==<br />
<br />
The Purchase Contract Management functions are available in <b>''/Supplier Management/Purchase Contracts/Purchase Contracts''</b><br />
<br />
This function enables the itmSUITE® Manager to <b>Add</b>, <b>Delete</b> a Purchase Contract.<br />
<br />
itmSUITE® provide Time & Material Types of contract, with the possibility to manage the different type of manage Expenses.<br />
<br />
"Time & Material", contract expects to specify the Purchase role tariff. Purchase contract must be associate to a '[[Glossary|Project]]'' or a '[[Glossary|Service]]''. <br />
<br />
Time Material contract can be differentiated by the Expanses Management:<br />
<br />
<br />
Purchase contract form presents five tabs:<br />
<br />
# General<br />
# Roles<br />
# Resources<br />
# Documents<br />
# Project references<br />
<br />
<br />
Purchase contract <u>''General''</u> tab contains the main contract information. The list of fields is shown in the following table:<br />
<br />
{| class="wikitable"<br />
! General tab fields!! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Provisory || Initial status of Purchase Contract enable the ''Manager'' to set all the properties<br />
|-<br />
| Operational ||in this status the contract is fully available for the system<br />
|-<br />
| Cancelled || Contract will be no more used by system. If there is a '[[Glossary|Project]]'' or a '[[Glossary|Service]]'' in status different from closed a warning message will be shown.<br />
|-<br />
| Closed || Contract will be no more used by system. Managers can set this status only if the AII flag is selected.<br />
|}<br />
|-<br />
| "Code" || Internal contract number. Non editable.<br />
|-<br />
| "Contract Date" || This field record the date the contract has been signed.<br />
|-<br />
| "Term Start Date" || This field record the Initial contract validity date<br />
|-<br />
| "Term End Date" || This field record the End contract validity date<br />
|-<br />
| "Name" || This field record contract name<br />
|-<br />
| "Description" || This field record contract description<br />
|-<br />
| "Supplier" || This field set the supplier the purchase contract belongs too.<br />
|-<br />
| "Supplier Contract code" || This field set a cross reference with the supplier organization<br />
|-<br />
| "Supplier contract referent" || Supplier referent<br />
|-<br />
| "Bank Name" || This field set the bank information related to the purchase contract. By default, itmSUITE® valorised it with the default Supplier bank account information. <br />
|-<br />
| "Payment Terms" || This field set the payment terms related to the purchase contract. By default, itmSUITE® valorised it with the supplier payment terms information. <br />
|-<br />
| "Currency" || This field set currency information<br />
|-<br />
| "Expenses Type" || This field identify the ''Contract' expenses management type. Values are:<br />
{| class="wikitable"<br />
! Expenses type!! Description<br />
|-<br />
| "Documented" || if selected the resource can record in ''[[Glossary|Timesheet]]'' the travel expenses. Purchase contract enable the ''Manager'' to set a maximum amount of expense for each travel expense.<br />
|-<br />
| "Fixed" ||if selected a "per Day" forfait value can be invoiced to client.<br />
|-<br />
| "None" || if selected the contract doesn't allow to insert expenses.<br />
|}<br />
|-<br />
| "Fixed Expenses per Day"|| This field can be valorised when the "Fixed" Expensed Type is selected<br />
|-<br />
| "KM Tariff" || The following list of fields can be valorised when the "Documented" Expensed Type is selected. Set the default tariff for a KM declared on ''[[Glossary|Timesheet]]'' record<br />
|-<br />
| "KM Tariff Max"|| Used to check the maximum value that can be declared on ''[[Glossary|Timesheet]]'' record<br />
|-<br />
| "Travel Expenses Max"|| Used to check the maximum value that can be invoiced by contract <br />
|-<br />
| "Hotel Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Dinner Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Lunch Expenses Max"|| Used to check the maximum value that can be invoiced by contract<br />
|-<br />
| "Allow Extra work"|| Only if flagged an extra work tariff can be charge to the organization<br />
|}<br />
<br />
For each ''[[Glossary|Purchase Contract]]'' is possible to set different <u>''Roles Tariff''</u>. Role Tariff is linked to a Resource that perform ''[[Glossary|Timesheet]]'' via the Resource "Purchase Role" field.<br />
<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print the list</b> of address.<br />
<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Role Tariff tab fields!! Description<br />
|-<br />
| "Role" || Purchase role name<br />
|-<br />
| "Daily Tariff" || Daily Tariff amount<br />
|-<br />
| "Fixed Expenses Amount" || Forfait expense Amount<br />
|}<br />
<br />
For each Purchase Contract is possible to set different ''[[Glossary|Resources]]''. ''Resources" can play multiple roles, so each ''[[Glossary|timesheet]]'' can be charged in differnt way.<br />
<br />
The session enables the user to Add, Delete or Print the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Resources tab fields!! Description<br />
|-<br />
| "Resources" || Select the record that belongs to the Supplier<br />
|-<br />
| "Contribution %" || Set the percentage of additional contribution to be invoice to the Supplier as Security Tax.<br />
|-<br />
| Roles || Grid section with a Summary information of ''[[Glossary | Purchase Role]]''<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Role!! Description<br />
|-<br />
| "Role" || Purchase Role description<br />
|-<br />
| "Abbreviation" || Purchase role code<br />
|-<br />
| "Cost per Day" || Tariff associate to the purchase role<br />
|-<br />
| "Fixed Expenses Amount" || Forfait expense Amount.<br />
|-<br />
| "Default Flag" || if valorised this tariff will be shown as default on Timesheet registration<br />
|-<br />
| "Use for Budget Flag" || if valorised this purchase tariff will be used to evaluate the budget effort in project / service estimation and in Ticket Estimation<br />
|}<br />
<br />
|}<br />
<br />
For each Purchase Contract is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identify the area of the document. The Topic follow the document taxonomy<br />
|-<br />
| "Type" || Identify the type of document. The Type follow the document taxonomy.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database, default option, or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || Only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
<u> Purchase References tab </u> shown for each Purchase contract all the ''project'' where it is used.</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3954Resources and Groups2018-06-13T16:22:25Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary | Resource]]'' is linked to a ''[[Glossary | User]]'' and can belongs to a different Groups.<br />
''[[Glossary | Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ Project configuration steps - Resources |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ Creating Service Catalog Management (SRCS)|SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ Domain authentication and SSO| User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enables the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identify the area of the document. The Topic follow the document taxonomy<br />
|-<br />
| "Type" || Identify the type of document. The Type follow the document taxonomy.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database, default option, or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || Only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a group means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Tab General view || Resource can view General Tab of Resource session<br />
|-<br />
| Tab General update || Resource can update General Tab of Resource session<br />
|-<br />
| Tab Address view || Resource can view Address Tab of Resource session<br />
|-<br />
| Tab Address update|| Resource can update Address Tab of Resource session<br />
|-<br />
| Tab Document view|| Resource can view Document Tab of Resource session<br />
|-<br />
| Tab Document update|| Resource can update Document Tab of Resource session<br />
|-<br />
| Tab Configuration Item view|| Resource can view Configuration item Tab of Resource session<br />
|-<br />
| Tab Configuration Item update|| Resource can update Configuration item Tab of Resource session<br />
|-<br />
| Tab Project/Service view|| Resource can view Project/Service Tab of Resource session<br />
|-<br />
| Tab Project/Service update|| Resource can update Project/Service Tab of Resource session<br />
|-<br />
| Tab Service Request view|| Resource can view Service Request Tab of Resource session<br />
|-<br />
| Tab Service Request update|| Resource can update Service Request Tab of Resource session<br />
|-<br />
| Tab Group view|| Resource can view Group Tab of Resource session<br />
|-<br />
| Tab Group update|| Resource can update Group Tab of Resource session<br />
|-<br />
| Tab Privileges view|| Resource can view Privileges Tab of Resource session<br />
|-<br />
| Tab Privileges update|| Resource can update Privileges Tab of Resource session<br />
|-<br />
| Tab Cost Items view|| Resource can view Cost Items Tab of Resource session<br />
|-<br />
| Tab Cost Items update|| Resource can update Cost Items Tab of Resource session<br />
|}<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges are managed for entity. The list of available entity is:<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Price lists view || Resource can view Price List definition<br />
|-<br />
| Price lists update ||Resource can update Price List definition<br />
|-<br />
| View Price items for projects/services ||Resource can view Price Items Project / Service definition<br />
|-<br />
| Update Price items for projects/services||Resource can update Price Items Project / Service definition<br />
|-<br />
| View Cost items for resources||Resource can view Cost Items definition<br />
|-<br />
| Update Cost items for resources||Resource can update Cost Items definition<br />
|}<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recorded the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distribute it to a ''resource'' , groups as well to all the resources that belongs to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]'' or ''[[Timesheet Management]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ Workflow Engine Configuration|Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ Workflow Engine Configuration|Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resources for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaration.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enables the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configures the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Cancelled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enabled to define a group of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between ''resource'' and ''group''.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two categories of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges can be set for the following entity:<br />
# Resources, with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists, with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refer to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refer to itself<br />
|}<br />
<br />
[[Glossary| ASM]] Privileges, show the [[Glossary | Configuration Item]] Structure present into the itmSUITE® CMS Module. For each folder/sub folder the ''Administrator'' can assign the following privileges:<br />
<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Read || Resource Member of group can view the ''configuration item'' present into the folder and read the information.<br />
|-<br />
| Update || Resource Member of group can view the ''configuration item'' present into the folder and update the information.<br />
|-<br />
| Read Own || Resource Member of group can view the ''configuration item'' present into the folder and read the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
|-<br />
| Update Own || Resource Member of group can view the ''configuration item'' present into the folder and update the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
<br />
|}<br />
It is possible also grant the group to:<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Exploration model grant || Resource Member of group can run the Exploration Model function<br />
|-<br />
| Meta Data grant || Resource Member of group can manage the Metadata function<br />
|}<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
The Workflow management has been enriched with the possibility to profile ''Group'' as [[Glossary |Role]] in a Workflow.<br />
With this feature Resource present on a Group can be granted to:<br />
* Access a ticket<br />
* Manage a ticket<br />
For further detail see [[Workflow Engine Configuration |Workflow Management]] in a Workflow.<br />
<br />
=== Add Group to Workflow ===<br />
Group is a a key component in ''Workflow Management''.<br />
Mainly the Group can act as Profile,say static [[Glossary |role]], or assume dynamic [[Glossary |role]], so per ''ticket''.<br />
<br />
For further detail see [[Workflow Engine Configuration |Workflow Management]] in a Workflow.<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
[[Glossary |SRCS]] is the service catalogue request. itmSUITE® can grant the visibility of a single request to:<br />
#Requester(s)<br />
#Group(s)<br />
#Organization Unit(s)<br />
<br />
For further detail see [[Creating Service Catalog Management (SRCS)|SRCS Management]] in a Workflow.<br />
<br />
=== Profile a Timesheet declaration ===<br />
This feature enable the resource to specify the Group he/she was working during the ''Timesheet'' registration. This feature is a simple way to categorized ''Timesheet'' based on the Business Role assumed by the Resource.<br />
<br />
For further detail see ''[[ Timesheet Management |Timesheet Management]]''<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3948Resources and Groups2018-06-13T16:02:03Z<p>Francesco.bertuletti: /* Timesheet declaration */</p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary | Resource]]'' is linked to a ''[[Glossary | User]]'' and can belongs to a different Groups.<br />
''[[Glossary | Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ Project configuration steps - Resources |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ Creating Service Catalog Management (SRCS)|SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ Domain authentication and SSO| User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enables the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identify the area of the document. The Topic follow the document taxonomy<br />
|-<br />
| "Type" || Identify the type of document. The Type follow the document taxonomy.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database, default option, or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || Only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a group means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Tab General view || Resource can view General Tab of Resource session<br />
|-<br />
| Tab General update || Resource can update General Tab of Resource session<br />
|-<br />
| Tab Address view || Resource can view Address Tab of Resource session<br />
|-<br />
| Tab Address update|| Resource can update Address Tab of Resource session<br />
|-<br />
| Tab Document view|| Resource can view Document Tab of Resource session<br />
|-<br />
| Tab Document update|| Resource can update Document Tab of Resource session<br />
|-<br />
| Tab Configuration Item view|| Resource can view Configuration item Tab of Resource session<br />
|-<br />
| Tab Configuration Item update|| Resource can update Configuration item Tab of Resource session<br />
|-<br />
| Tab Project/Service view|| Resource can view Project/Service Tab of Resource session<br />
|-<br />
| Tab Project/Service update|| Resource can update Project/Service Tab of Resource session<br />
|-<br />
| Tab Service Request view|| Resource can view Service Request Tab of Resource session<br />
|-<br />
| Tab Service Request update|| Resource can update Service Request Tab of Resource session<br />
|-<br />
| Tab Group view|| Resource can view Group Tab of Resource session<br />
|-<br />
| Tab Group update|| Resource can update Group Tab of Resource session<br />
|-<br />
| Tab Privileges view|| Resource can view Privileges Tab of Resource session<br />
|-<br />
| Tab Privileges update|| Resource can update Privileges Tab of Resource session<br />
|-<br />
| Tab Cost Items view|| Resource can view Cost Items Tab of Resource session<br />
|-<br />
| Tab Cost Items update|| Resource can update Cost Items Tab of Resource session<br />
|}<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges are managed for entity. The list of available entity is:<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Price lists view || Resource can view Price List definition<br />
|-<br />
| Price lists update ||Resource can update Price List definition<br />
|-<br />
| View Price items for projects/services ||Resource can view Price Items Project / Service definition<br />
|-<br />
| Update Price items for projects/services||Resource can update Price Items Project / Service definition<br />
|-<br />
| View Cost items for resources||Resource can view Cost Items definition<br />
|-<br />
| Update Cost items for resources||Resource can update Cost Items definition<br />
|}<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recorded the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distribute it to a ''resource'' , groups as well to all the resources that belongs to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]'' or ''[[Timesheet Management]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ Workflow Engine Configuration|Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ Workflow Engine Configuration|Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resources for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaration.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enables the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configures the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Cancelled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enabled to define a group of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between ''resource'' and ''group''.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two categories of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges can be set for the following entity:<br />
# Resources, with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists, with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refer to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refer to itself<br />
|}<br />
<br />
[[Glossary| ASM]] Privileges, show the [[Glossary | Configuration Item]] Structure present into the itmSUITE® CMS Module. For each folder/sub folder the ''Administrator'' can assign the following privileges:<br />
<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Read || Resource Member of group can view the ''configuration item'' present into the folder and read the information.<br />
|-<br />
| Update || Resource Member of group can view the ''configuration item'' present into the folder and update the information.<br />
|-<br />
| Read Own || Resource Member of group can view the ''configuration item'' present into the folder and read the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
|-<br />
| Update Own || Resource Member of group can view the ''configuration item'' present into the folder and update the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
<br />
|}<br />
It is possible also grant the group to:<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Exploration model grant || Resource Member of group can run the Exploration Model function<br />
|-<br />
| Meta Data grant || Resource Member of group can manage the Metadata function<br />
|}<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
The Workflow management has been enriched with the possibility to profile ''Group'' as [[Glossary |Role]] in a Workflow.<br />
With this feature Resource present on a Group can be granted to:<br />
* Access a ticket<br />
* Manage a ticket<br />
For further detail see [[Workflow Engine Configuration |Workflow Management]] in a Workflow.<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3947Resources and Groups2018-06-13T16:00:22Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary | Resource]]'' is linked to a ''[[Glossary | User]]'' and can belongs to a different Groups.<br />
''[[Glossary | Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ Project configuration steps - Resources |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ Creating Service Catalog Management (SRCS)|SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ Domain authentication and SSO| User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enables the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identify the area of the document. The Topic follow the document taxonomy<br />
|-<br />
| "Type" || Identify the type of document. The Type follow the document taxonomy.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database, default option, or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || Only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a group means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Tab General view || Resource can view General Tab of Resource session<br />
|-<br />
| Tab General update || Resource can update General Tab of Resource session<br />
|-<br />
| Tab Address view || Resource can view Address Tab of Resource session<br />
|-<br />
| Tab Address update|| Resource can update Address Tab of Resource session<br />
|-<br />
| Tab Document view|| Resource can view Document Tab of Resource session<br />
|-<br />
| Tab Document update|| Resource can update Document Tab of Resource session<br />
|-<br />
| Tab Configuration Item view|| Resource can view Configuration item Tab of Resource session<br />
|-<br />
| Tab Configuration Item update|| Resource can update Configuration item Tab of Resource session<br />
|-<br />
| Tab Project/Service view|| Resource can view Project/Service Tab of Resource session<br />
|-<br />
| Tab Project/Service update|| Resource can update Project/Service Tab of Resource session<br />
|-<br />
| Tab Service Request view|| Resource can view Service Request Tab of Resource session<br />
|-<br />
| Tab Service Request update|| Resource can update Service Request Tab of Resource session<br />
|-<br />
| Tab Group view|| Resource can view Group Tab of Resource session<br />
|-<br />
| Tab Group update|| Resource can update Group Tab of Resource session<br />
|-<br />
| Tab Privileges view|| Resource can view Privileges Tab of Resource session<br />
|-<br />
| Tab Privileges update|| Resource can update Privileges Tab of Resource session<br />
|-<br />
| Tab Cost Items view|| Resource can view Cost Items Tab of Resource session<br />
|-<br />
| Tab Cost Items update|| Resource can update Cost Items Tab of Resource session<br />
|}<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges are managed for entity. The list of available entity is:<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Price lists view || Resource can view Price List definition<br />
|-<br />
| Price lists update ||Resource can update Price List definition<br />
|-<br />
| View Price items for projects/services ||Resource can view Price Items Project / Service definition<br />
|-<br />
| Update Price items for projects/services||Resource can update Price Items Project / Service definition<br />
|-<br />
| View Cost items for resources||Resource can view Cost Items definition<br />
|-<br />
| Update Cost items for resources||Resource can update Cost Items definition<br />
|}<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recorded the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distribute it to a ''resource'' , groups as well to all the resources that belongs to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ Workflow Engine Configuration|Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ Workflow Engine Configuration|Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resources for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaration.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enables the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configures the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Cancelled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enabled to define a group of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between ''resource'' and ''group''.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two categories of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges can be set for the following entity:<br />
# Resources, with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists, with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refer to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refer to itself<br />
|}<br />
<br />
[[Glossary| ASM]] Privileges, show the [[Glossary | Configuration Item]] Structure present into the itmSUITE® CMS Module. For each folder/sub folder the ''Administrator'' can assign the following privileges:<br />
<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Read || Resource Member of group can view the ''configuration item'' present into the folder and read the information.<br />
|-<br />
| Update || Resource Member of group can view the ''configuration item'' present into the folder and update the information.<br />
|-<br />
| Read Own || Resource Member of group can view the ''configuration item'' present into the folder and read the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
|-<br />
| Update Own || Resource Member of group can view the ''configuration item'' present into the folder and update the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
<br />
|}<br />
It is possible also grant the group to:<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Exploration model grant || Resource Member of group can run the Exploration Model function<br />
|-<br />
| Meta Data grant || Resource Member of group can manage the Metadata function<br />
|}<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
The Workflow management has been enriched with the possibility to profile ''Group'' as [[Glossary |Role]] in a Workflow.<br />
With this feature Resource present on a Group can be granted to:<br />
* Access a ticket<br />
* Manage a ticket<br />
For further detail see [[Workflow Engine Configuration |Workflow Management]] in a Workflow.<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3946Resources and Groups2018-06-13T15:54:26Z<p>Francesco.bertuletti: /* Add Group as Profile in a Workflow */</p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary | Resource]]'' is linked to a ''[[Glossary | User]]'' and can belongs to a different Groups.<br />
''[[Glossary | Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enables the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identify the area of the document. The Topic follow the document taxonomy<br />
|-<br />
| "Type" || Identify the type of document. The Type follow the document taxonomy.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database, default option, or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || Only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a group means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Tab General view || Resource can view General Tab of Resource session<br />
|-<br />
| Tab General update || Resource can update General Tab of Resource session<br />
|-<br />
| Tab Address view || Resource can view Address Tab of Resource session<br />
|-<br />
| Tab Address update|| Resource can update Address Tab of Resource session<br />
|-<br />
| Tab Document view|| Resource can view Document Tab of Resource session<br />
|-<br />
| Tab Document update|| Resource can update Document Tab of Resource session<br />
|-<br />
| Tab Configuration Item view|| Resource can view Configuration item Tab of Resource session<br />
|-<br />
| Tab Configuration Item update|| Resource can update Configuration item Tab of Resource session<br />
|-<br />
| Tab Project/Service view|| Resource can view Project/Service Tab of Resource session<br />
|-<br />
| Tab Project/Service update|| Resource can update Project/Service Tab of Resource session<br />
|-<br />
| Tab Service Request view|| Resource can view Service Request Tab of Resource session<br />
|-<br />
| Tab Service Request update|| Resource can update Service Request Tab of Resource session<br />
|-<br />
| Tab Group view|| Resource can view Group Tab of Resource session<br />
|-<br />
| Tab Group update|| Resource can update Group Tab of Resource session<br />
|-<br />
| Tab Privileges view|| Resource can view Privileges Tab of Resource session<br />
|-<br />
| Tab Privileges update|| Resource can update Privileges Tab of Resource session<br />
|-<br />
| Tab Cost Items view|| Resource can view Cost Items Tab of Resource session<br />
|-<br />
| Tab Cost Items update|| Resource can update Cost Items Tab of Resource session<br />
|}<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges are managed for entity. The list of available entity is:<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Price lists view || Resource can view Price List definition<br />
|-<br />
| Price lists update ||Resource can update Price List definition<br />
|-<br />
| View Price items for projects/services ||Resource can view Price Items Project / Service definition<br />
|-<br />
| Update Price items for projects/services||Resource can update Price Items Project / Service definition<br />
|-<br />
| View Cost items for resources||Resource can view Cost Items definition<br />
|-<br />
| Update Cost items for resources||Resource can update Cost Items definition<br />
|}<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recorded the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distribute it to a ''resource'' , groups as well to all the resources that belongs to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resources for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaration.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enables the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configures the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Cancelled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enabled to define a group of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between ''resource'' and ''group''.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two categories of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges can be set for the following entity:<br />
# Resources, with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists, with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refer to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refer to itself<br />
|}<br />
<br />
[[Glossary| ASM]] Privileges, show the [[Glossary | Configuration Item]] Structure present into the itmSUITE® CMS Module. For each folder/sub folder the ''Administrator'' can assign the following privileges:<br />
<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Read || Resource Member of group can view the ''configuration item'' present into the folder and read the information.<br />
|-<br />
| Update || Resource Member of group can view the ''configuration item'' present into the folder and update the information.<br />
|-<br />
| Read Own || Resource Member of group can view the ''configuration item'' present into the folder and read the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
|-<br />
| Update Own || Resource Member of group can view the ''configuration item'' present into the folder and update the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
<br />
|}<br />
It is possible also grant the group to:<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Exploration model grant || Resource Member of group can run the Exploration Model function<br />
|-<br />
| Meta Data grant || Resource Member of group can manage the Metadata function<br />
|}<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
The Workflow management has been enriched with the possibility to profile ''Group'' as [[Glossary |Role]] in a Workflow.<br />
With this feature Resource present on a Group can be granted to:<br />
* Access a ticket<br />
* Manage a ticket<br />
For further detail see [[Workflow Engine Configuration |Workflow Management]] in a Workflow.<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3945Resources and Groups2018-06-13T15:52:49Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary | Resource]]'' is linked to a ''[[Glossary | User]]'' and can belongs to a different Groups.<br />
''[[Glossary | Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enables the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identify the area of the document. The Topic follow the document taxonomy<br />
|-<br />
| "Type" || Identify the type of document. The Type follow the document taxonomy.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database, default option, or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || Only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a group means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Tab General view || Resource can view General Tab of Resource session<br />
|-<br />
| Tab General update || Resource can update General Tab of Resource session<br />
|-<br />
| Tab Address view || Resource can view Address Tab of Resource session<br />
|-<br />
| Tab Address update|| Resource can update Address Tab of Resource session<br />
|-<br />
| Tab Document view|| Resource can view Document Tab of Resource session<br />
|-<br />
| Tab Document update|| Resource can update Document Tab of Resource session<br />
|-<br />
| Tab Configuration Item view|| Resource can view Configuration item Tab of Resource session<br />
|-<br />
| Tab Configuration Item update|| Resource can update Configuration item Tab of Resource session<br />
|-<br />
| Tab Project/Service view|| Resource can view Project/Service Tab of Resource session<br />
|-<br />
| Tab Project/Service update|| Resource can update Project/Service Tab of Resource session<br />
|-<br />
| Tab Service Request view|| Resource can view Service Request Tab of Resource session<br />
|-<br />
| Tab Service Request update|| Resource can update Service Request Tab of Resource session<br />
|-<br />
| Tab Group view|| Resource can view Group Tab of Resource session<br />
|-<br />
| Tab Group update|| Resource can update Group Tab of Resource session<br />
|-<br />
| Tab Privileges view|| Resource can view Privileges Tab of Resource session<br />
|-<br />
| Tab Privileges update|| Resource can update Privileges Tab of Resource session<br />
|-<br />
| Tab Cost Items view|| Resource can view Cost Items Tab of Resource session<br />
|-<br />
| Tab Cost Items update|| Resource can update Cost Items Tab of Resource session<br />
|}<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges are managed for entity. The list of available entity is:<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Price lists view || Resource can view Price List definition<br />
|-<br />
| Price lists update ||Resource can update Price List definition<br />
|-<br />
| View Price items for projects/services ||Resource can view Price Items Project / Service definition<br />
|-<br />
| Update Price items for projects/services||Resource can update Price Items Project / Service definition<br />
|-<br />
| View Cost items for resources||Resource can view Cost Items definition<br />
|-<br />
| Update Cost items for resources||Resource can update Cost Items definition<br />
|}<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recorded the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distribute it to a ''resource'' , groups as well to all the resources that belongs to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resources for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaration.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enables the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configures the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Cancelled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enabled to define a group of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between ''resource'' and ''group''.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two categories of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges can be set for the following entity:<br />
# Resources, with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists, with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refer to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refer to itself<br />
|}<br />
<br />
[[Glossary| ASM]] Privileges, show the [[Glossary | Configuration Item]] Structure present into the itmSUITE® CMS Module. For each folder/sub folder the ''Administrator'' can assign the following privileges:<br />
<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Read || Resource Member of group can view the ''configuration item'' present into the folder and read the information.<br />
|-<br />
| Update || Resource Member of group can view the ''configuration item'' present into the folder and update the information.<br />
|-<br />
| Read Own || Resource Member of group can view the ''configuration item'' present into the folder and read the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
|-<br />
| Update Own || Resource Member of group can view the ''configuration item'' present into the folder and update the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
<br />
|}<br />
It is possible also grant the group to:<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Exploration model grant || Resource Member of group can run the Exploration Model function<br />
|-<br />
| Meta Data grant || Resource Member of group can manage the Metadata function<br />
|}<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
The Workflow management has been enriched with the possibility to profile ''Group'' as [[Glossary |Role]] in a Workflow.<br />
With this feature Resource present on a Group can be granted to:<br />
* Access a ticket<br />
* Manage a ticket<br />
For further detail see [[Workflow Management |Workflow Management]] in a Workflow.<br />
<br />
<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3926Resources and Groups2018-06-13T15:29:49Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Tab General view || Resource can view General Tab of Resource session<br />
|-<br />
| Tab General update || Resource can update General Tab of Resource session<br />
|-<br />
| Tab Address view || Resource can view Address Tab of Resource session<br />
|-<br />
| Tab Address update|| Resource can update Address Tab of Resource session<br />
|-<br />
| Tab Document view|| Resource can view Document Tab of Resource session<br />
|-<br />
| Tab Document update|| Resource can update Document Tab of Resource session<br />
|-<br />
| Tab Configuration Item view|| Resource can view Configuartion item Tab of Resource session<br />
|-<br />
| Tab Configuration Item update|| Resource can update Configuartion item Tab of Resource session<br />
|-<br />
| Tab Project/Service view|| Resource can View Projet/Service Tab of Resource session<br />
|-<br />
| Tab Project/Service update|| Resource can update Project/Service Tab of Resource session<br />
|-<br />
| Tab Service Request view|| Resource can view Service Request Tab of Resource session<br />
|-<br />
| Tab Service Request update|| Resource can update Service Request Tab of Resource session<br />
|-<br />
| Tab Group view|| Resource can view Group Tab of Resource session<br />
|-<br />
| Tab Group update|| Resource can update Group Tab of Resource session<br />
|-<br />
| Tab Privileges view|| Resource can view Privileges Tab of Resource session<br />
|-<br />
| Tab Privileges update|| Resource can update Privileges Tab of Resource session<br />
|-<br />
| Tab Cost Items view|| Resource can view Cost Items Tab of Resource session<br />
|-<br />
| Tab Cost Items update|| Resource can update Cost Items Tab of Resource session<br />
|}<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Price lists view || Resource can view Price List definition<br />
|-<br />
| Price lists update ||Resource can update Price List definition<br />
|-<br />
| View Price items for projects/services ||Resource can view Price Items Project / Service definition<br />
|-<br />
| Update Price items for projects/services||Resource can update Price Items Project / Service definition<br />
|-<br />
| View Cost items for resources||Resource can view Cost Items definition<br />
|-<br />
| Update Cost items for resources||Resource can update Cost Items definition<br />
|}<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distrute it to a ''resource'' , groups as well to all the resources that belogons to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resourse for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaretion.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enable the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configure the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Canceled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enable to define a groups of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between resource and group.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two category of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges, can be set for the following entity:<br />
# Resources , with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists , with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refere to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refere to itself<br />
|}<br />
<br />
[[Glossary| ASM]] Privileges, show the [[Glossary|Configuuration Item]] Structure present into the itmSUITE® CMS Module. For each folder/sub folder the ''Admininstrator'' can assign the following provileges:<br />
<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Read || Resource Member of group can view the ''configuration item'' present into the folder and read the information.<br />
|-<br />
| Update || Resource Member of group can view the ''configuration item'' present into the folder and update the information.<br />
|-<br />
| Read Own || Resource Member of group can view the ''configuration item'' present into the folder and read the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
|-<br />
| Update Own || Resource Member of group can view the ''configuration item'' present into the folder and update the information only of he/she is the ''Creator'' of the ''configuration item''.<br />
<br />
|}<br />
It is possible also grant the group to:<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Exploration model grant || Resource Member of group can run the Exploration Model function<br />
|-<br />
| Meta Data grant || Resource Member of group can manage the Metadata function<br />
|}<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management in above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3925Resources and Groups2018-06-13T15:19:40Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Tab General view || Resource can view General Tab of Resource session<br />
|-<br />
| Tab General update || Resource can update General Tab of Resource session<br />
|-<br />
| Tab Address view || Resource can view Address Tab of Resource session<br />
|-<br />
| Tab Address update|| Resource can update Address Tab of Resource session<br />
|-<br />
| Tab Document view|| Resource can view Document Tab of Resource session<br />
|-<br />
| Tab Document update|| Resource can update Document Tab of Resource session<br />
|-<br />
| Tab Configuration Item view|| Resource can view Configuartion item Tab of Resource session<br />
|-<br />
| Tab Configuration Item update|| Resource can update Configuartion item Tab of Resource session<br />
|-<br />
| Tab Project/Service view|| Resource can View Projet/Service Tab of Resource session<br />
|-<br />
| Tab Project/Service update|| Resource can update Project/Service Tab of Resource session<br />
|-<br />
| Tab Service Request view|| Resource can view Service Request Tab of Resource session<br />
|-<br />
| Tab Service Request update|| Resource can update Service Request Tab of Resource session<br />
|-<br />
| Tab Group view|| Resource can view Group Tab of Resource session<br />
|-<br />
| Tab Group update|| Resource can update Group Tab of Resource session<br />
|-<br />
| Tab Privileges view|| Resource can view Privileges Tab of Resource session<br />
|-<br />
| Tab Privileges update|| Resource can update Privileges Tab of Resource session<br />
|-<br />
| Tab Cost Items view|| Resource can view Cost Items Tab of Resource session<br />
|-<br />
| Tab Cost Items update|| Resource can update Cost Items Tab of Resource session<br />
|}<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Price lists view || Resource can view Price List definition<br />
|-<br />
| Price lists update ||Resource can update Price List definition<br />
|-<br />
| View Price items for projects/services ||Resource can view Price Items Project / Service definition<br />
|-<br />
| Update Price items for projects/services||Resource can update Price Items Project / Service definition<br />
|-<br />
| View Cost items for resources||Resource can view Cost Items definition<br />
|-<br />
| Update Cost items for resources||Resource can update Cost Items definition<br />
|}<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distrute it to a ''resource'' , groups as well to all the resources that belogons to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resourse for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaretion.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enable the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configure the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Canceled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enable to define a groups of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between resource and group.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two category of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges, can be set for the following entity:<br />
# Resources , with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists , with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refere to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refere to itself<br />
|}<br />
<br />
[[Glossary| ASM]] Privileges, show the [[Glossary|Configuuration Item]] Structure present into the itmSUITE® CMS Module. For each folder/sub folder the ''Admininstrator'' can assign the following provileges:<br />
<br />
{| class="wikitable"<br />
! Privilege !! Description<br />
|-<br />
| Read || Resource Member of group can view the ''configuration item'' present into the folder and read the information.<br />
|-<br />
| Update || Resource Member of group can view the ''configuration item'' present into the folder and update the information.<br />
|-<br />
| Read Own || Resource Member of group can view the ''configuration item'' present into the folder and read the information only of he/she is the Owner of the ''configuration item''.<br />
|-<br />
| Update Own || Resource Member of group can view the ''configuration item'' present into the folder and update the information only of he/she is the Owner of the ''configuration item''.<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management in above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3915Resources and Groups2018-06-13T09:03:41Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Tab General view || Resource can view General Tab of Resource session<br />
|-<br />
| Tab General update || Resource can update General Tab of Resource session<br />
|-<br />
| Tab Address view || Resource can view Address Tab of Resource session<br />
|-<br />
| Tab Address update|| Resource can update Address Tab of Resource session<br />
|-<br />
| Tab Document view|| Resource can view Document Tab of Resource session<br />
|-<br />
| Tab Document update|| Resource can update Document Tab of Resource session<br />
|-<br />
| Tab Configuration Item view|| Resource can view Configuartion item Tab of Resource session<br />
|-<br />
| Tab Configuration Item update|| Resource can update Configuartion item Tab of Resource session<br />
|-<br />
| Tab Project/Service view|| Resource can View Projet/Service Tab of Resource session<br />
|-<br />
| Tab Project/Service update|| Resource can update Project/Service Tab of Resource session<br />
|-<br />
| Tab Service Request view|| Resource can view Service Request Tab of Resource session<br />
|-<br />
| Tab Service Request update|| Resource can update Service Request Tab of Resource session<br />
|-<br />
| Tab Group view|| Resource can view Group Tab of Resource session<br />
|-<br />
| Tab Group update|| Resource can update Group Tab of Resource session<br />
|-<br />
| Tab Privileges view|| Resource can view Privileges Tab of Resource session<br />
|-<br />
| Tab Privileges update|| Resource can update Privileges Tab of Resource session<br />
|-<br />
| Tab Cost Items view|| Resource can view Cost Items Tab of Resource session<br />
|-<br />
| Tab Cost Items update|| Resource can update Cost Items Tab of Resource session<br />
|}<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Price lists view || Resource can view Price List definition<br />
|-<br />
| Price lists update ||Resource can update Price List definition<br />
|-<br />
| View Price items for projects/services ||Resource can view Price Items Project / Service definition<br />
|-<br />
| Update Price items for projects/services||Resource can update Price Items Project / Service definition<br />
|-<br />
| View Cost items for resources||Resource can view Cost Items definition<br />
|-<br />
| Update Cost items for resources||Resource can update Cost Items definition<br />
|}<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distrute it to a ''resource'' , groups as well to all the resources that belogons to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resourse for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaretion.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enable the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configure the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Canceled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enable to define a groups of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between resource and group.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two category of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges, can be set for the following entity:<br />
# Resources , with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists , with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refere to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refere to itself<br />
|}<br />
<br />
ASM Privileges, can be set for the following folder:<br />
# Folder <br />
<br />
<br />
<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management in above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3914Resources and Groups2018-06-13T08:59:15Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
<br />
Resource privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Tab General view || Resource can view General Tab of Resource session<br />
|-<br />
| Tab General update || Resource can update General Tab of Resource session<br />
|-<br />
| Tab Address view || Resource can view Address Tab of Resource session<br />
|-<br />
| Tab Address update|| Resource can update Address Tab of Resource session<br />
|-<br />
| Tab Document view|| Resource can view Document Tab of Resource session<br />
|-<br />
| Tab Document update|| Resource can update Document Tab of Resource session<br />
|-<br />
| Tab Configuration Item view|| Resource can view Configuartion item Tab of Resource session<br />
|-<br />
| Tab Configuration Item update|| Resource can update Configuartion item Tab of Resource session<br />
|-<br />
| Tab Project/Service view|| Resource can View Projet/Service Tab of Resource session<br />
|-<br />
| Tab Project/Service update|| Resource can update Project/Service Tab of Resource session<br />
|-<br />
| Tab Service Request view|| Resource can view Service Request Tab of Resource session<br />
|-<br />
| Tab Service Request update|| Resource can update Service Request Tab of Resource session<br />
|-<br />
| Tab Group view|| Resource can view Group Tab of Resource session<br />
|-<br />
| Tab Group update|| Resource can update Group Tab of Resource session<br />
|-<br />
| Tab Privileges view|| Resource can view Privileges Tab of Resource session<br />
|-<br />
| Tab Privileges update|| Resource can update Privileges Tab of Resource session<br />
|-<br />
| Tab Cost Items view|| Resource can view Cost Items Tab of Resource session<br />
|-<br />
| Tab Cost Items update|| Resource can update Cost Items Tab of Resource session<br />
|}<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distrute it to a ''resource'' , groups as well to all the resources that belogons to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resourse for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaretion.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enable the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configure the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Canceled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enable to define a groups of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between resource and group.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two category of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges, can be set for the following entity:<br />
# Resources , with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists , with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refere to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refere to itself<br />
|}<br />
<br />
ASM Privileges, can be set for the following folder:<br />
# Folder <br />
<br />
<br />
<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management in above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3913Resources and Groups2018-06-13T08:49:35Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distrute it to a ''resource'' , groups as well to all the resources that belogons to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resourse for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaretion.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enable the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configure the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Canceled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enable to define a groups of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between resource and group.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two category of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges, can be set for the following entity:<br />
# Resources , with the same detail present in <u>''Resource / Privileges''</u><br />
# Price lists , with the same detail present in <u>''Resource / Privileges''</u><br />
# Timesheet<br />
<br />
Timesheet privileges can be granted on the following entity<br />
{| class="wikitable"<br />
! Entity!! Description<br />
|-<br />
| Group View || Resource Member of group can view all the timesheet that refere to itself<br />
|-<br />
| Group Approval || Resource Member of group can Approved the timesheet that refere to itself<br />
|}<br />
<br />
ASM Privileges, can be set for the following folder:<br />
# Folder <br />
<br />
<br />
<br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management in above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3911Resources and Groups2018-06-12T15:30:25Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distrute it to a ''resource'' , groups as well to all the resources that belogons to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resourse for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaretion.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enable the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configure the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Canceled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
General tab enable to define a groups of groups. itmSUITE® enable this selecting the <b>Add Group</b> button.<br />
<br />
For each ''Group'' is possible to define the <u>''Members''</u>. Manager can specify directly the list of resource that will be part of it. itmSUITE® presents an EJS grid with the possibility to <b> Add </b>, <b> Filter </b> and <b> Delete </b> the member ''resource'' of a group. Deletion in this case perform a physical relationship cancellation between resource and group.<br />
<br />
For each ''group'' is possible to manage <u>Privileges</u>. There are two category of privileges:<br />
# General Privileges<br />
# ASM Privileges<br />
<br />
General Privileges, can be set for the following entity:<br />
# Resources <br />
# Timesheet<br />
# Price lists<br />
<br />
ASM Privileges, can be set for the following folder:<br />
# Folder <br />
<br />
=== Add Resource to Group ===<br />
Refer to <u>''Member''</u> Tab management in above.<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3910Resources and Groups2018-06-12T15:14:52Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distrute it to a ''resource'' , groups as well to all the resources that belogons to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management| Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
Manage the ''Group'' is the entry point to manage group of resourse for:<br />
# Manage profile role on workflow<br />
# Create a visibility or assigned ownership or activity in workflow<br />
# Profile the Timesheet declaretion.<br />
<br />
Group management is done by a Manager ''[[Glossary | Role]]'', using the <b>General/Ticket/Groups </b>. This session enable the Manager / Administrator to: <b> Add<b>, <b> Delete </b> and <b> Print </b> the list of Group. <br />
<br />
The Group form presents four tabs:<br />
# General<br />
# Member<br />
# Privileges<br />
# Domain Info<br />
<br />
Groups deletion is a logical cancellation.<br />
<br />
To define a Group is we can insert:<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| Name || Group Name<br />
|-<br />
| Description || Group description<br />
|-<br />
| Default || Attribute of group. Usually the manager configure the group using the ''[[Glossary | MDMM]]'' function.<br />
|-<br />
| Status || This field can be Active / Canceled. Only "Active" group are seen in Workflow Management. changeableness<br />
|-<br />
| Menu Access || If flagged this Group will be accessible as menu link<br />
|-<br />
| Group can't be deleted || If flagged this Group can't be accidentally cancelled<br />
|}<br />
<br />
=== Add Resource to Group ===<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3909Resources and Groups2018-06-12T14:17:42Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distrute it to a ''resource'' , groups as well to all the resources that belogons to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester". For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
=== Add Resource to Group ===<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3908Resources and Groups2018-06-12T14:16:33Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
itmSUITE® enable the ''Manager'' to create a catalogue of request and to distrute it to a ''resource'' , groups as well to all the resources that belogons to an Organization unit. For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Timesheet declaration ===<br />
Timesheet declare can be perform by all the resource except the user with Role "Requester"<br />
For further detail about this subject refer to ''[[Workflow Engine Configuration]]''<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
Resource can be created manually or imported from Active Directory. For further detail about this subject refer to ''[[Domain authentication and SSO]]''<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
=== Add Resource to Group ===<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3907Resources and Groups2018-06-12T14:06:53Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
Resource in a key point of Project and Service management. Without resource is not possible to develop the activities, records costs and benefit. For further detail about this subject refer to<br />
''[[Project configuration steps - Resources]]''<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
<br />
<br />
=== Timesheet declaration ===<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
=== Add Resource to Group ===<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3906Resources and Groups2018-06-12T14:03:14Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
=== Add Resource to Project / Service ===<br />
<br />
=== Enable a Resource on Service Catalogue Request (SRCS) ===<br />
<br />
=== Timesheet declaration ===<br />
<br />
=== Synchronization User & Resource with Active Directory ===<br />
<br />
<br />
== Group Management process == <br />
The following table report the process the Group is involved<br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group as Profile in a Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|}<br />
<br />
=== Group Definition ===<br />
<br />
=== Add Resource to Group ===<br />
<br />
=== Add Group as Profile in a Workflow ===<br />
<br />
=== Add Group to Workflow ===<br />
<br />
=== Enable a Group on Service Catalogue Request (SRCS) === <br />
<br />
=== Profile a Timesheet declaration ===<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3905Resources and Groups2018-06-12T13:47:12Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different <u>Address</u>. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different <u>Documents</u>. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage <u>Configuration Item</u>. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |Project ]]'' / ''[[Glossary | Service]]''</u> he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of <u>''[[Glossary |SRCS ]]''</u> he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific <u>''group''</u>.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage <u>Privileges</u>. There are two possible levels of granularity: visibility or editability and can be assigned at the following entity:<br />
# Resources <br />
# Price lists<br />
<br />
<u>Resource privileges</u> is managed by ''resource type'' and Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
<u>''[[Glossary |Price list]]''</u> privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage <u>Cost Items</u>. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
<br />
<br />
== Group Management process == <br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Group || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|}<br />
<br />
<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3904Resources and Groups2018-06-12T13:40:19Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different Address. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different Documents. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage Configuration Item. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of ''[[Glossary |Project ]]'' / ''[[GlossaryService]]'' he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of ''[[Glossary |SRCS ]]'' he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific ''group''.<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage visibility or editability of two types of Privileges:<br />
# Resources <br />
# Price lists<br />
<br />
Resource privileges is managed by ''resource type'' than Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
''[[Glossary |Price list]]'' privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
For each ''resource'' is possible to manage Cost Items. Resource can manage Cost Item only if enabled in tab <u>''Privileges''</u>. Cost Item is the instance of a Price Item actualized with the Start Date. E.g a Price Item can be the license of a product. The Cost track and expense the assignment of the license to a resource. The session enables the user to <b>Add</b>, <b>Delete</b> a Cost Item. When a Cost Item is assigned to a resource is important to recored the quantity and the "Start Date" (Assignment Start Date). To track all figure assigned to a resource is better to set the "End Date" (Assignment End Date) instead of deleting the relationship between ''Resource'' and ''Cost Item''.<br />
<br />
<br />
<br />
== Group Management process == <br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Group || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|}<br />
<br />
<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3901Resources and Groups2018-06-12T10:48:53Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different Address. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different Documents. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage Configuration Item. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of ''[[Glossary |Project ]]'' / ''[[GlossaryService]]'' he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of ''[[Glossary |SRCS ]]'' he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific ''group''.<br />
<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage visibility or editability of two types of Privileges:<br />
# on resources <br />
# on price lists<br />
<br />
Resource privileges is managed by ''resource type'' than Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
''[[Glossary |Price list]]’’ privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
<br />
<br />
<br />
== Group Management process == <br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Group || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|}<br />
<br />
<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3900Resources and Groups2018-06-12T10:47:51Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different Address. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different Documents. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage Configuration Item. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration item. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item]]’’ are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of ''[[Glossary |Project ]]'' / ''[[GlossaryService]]'' he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of ''[[Glossary |SRCS ]]'' he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific ''group''.<br />
<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
# Adding a resource to groups means add he/she as a Group Member<br />
# Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
For each ''resource'' is possible to manage visibility or editability of two types of Privileges:<br />
# on resources <br />
# on price lists<br />
<br />
Resource privileges is managed by ''resource'' ''[[type]]'' than Entity. The list of available entity is:<br />
<Resource Type><br />
* Tab General view<br />
* Tab General update<br />
* Tab Address view<br />
* Tab Address update<br />
* Tab Document view<br />
* Tab Document update<br />
* Tab Configuration Item view<br />
* Tab Configuration Item update<br />
* Tab Project/Service view<br />
* Tab Project/Service update<br />
* Tab Service Request view<br />
* Tab Service Request update<br />
* Tab Group view<br />
* Tab Group update<br />
* Tab Privileges view<br />
* Tab Privileges update<br />
* Tab Cost Items view<br />
* Tab Cost Items update<br />
<br />
''[[Glossary |Price list]]’’ privileges is managed only the entity. The list of available entity is:<br />
* Price lists view<br />
* Price lists update<br />
* View Price items for projects/services<br />
* Update Price items for projects/services<br />
* View Cost items for resources<br />
* Update Cost items for resources<br />
<br />
<br />
<br />
<br />
== Group Management process == <br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Group || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|}<br />
<br />
<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Glossary&diff=3899Glossary2018-06-12T10:36:32Z<p>Francesco.bertuletti: /* P */</p>
<hr />
<div>{{Index}}<br />
{{clear}}<br />
<br />
Below is a list of terms and definitions used in this documentation.<br />
<br />
== A ==<br />
* ''Access management:'' according to ''ITIL®, t''he process responsible for allowing users to make use of IT services, data or other assets. Access management helps to protect the confidentiality, integrity and availability of assets by ensuring that only authorized users are able to access or modify them. Access management implements the policies of information security management and is sometimes referred to as rights management or identity management. In itmSUITE®, the typical activities required by ''access management'' can be dealt through ''service requests'' or ''changes''.<br />
* ''Action'': TBD<br />
* ''Action engine'': TBD<br />
* ''Active channel'': TBD<br />
* ''Admin'': a special ''user type''. The ''admin'' may: perform basic configuration and create other ''users'' for the administered ''company.'' For more information, have a look to the ''[[admin]]'' page.<br />
* ''Administrator'': resource with ''Admin'' characteristics<br />
* ''Admin kit'': TBD<br />
* ''Application language'': one of the languages for which itmSUITE® makes available the user interface (forms to interact and messages). See also ''business languages'' and [[Multi language]] management.<br />
* ''Application level role'': see ''role''.<br />
* ''ASM'': abbreviation for ''asset management''.<br />
* ''ASM view'': a view, defined by a list of columns, which is used to list ''configuration items''.<br />
* ''Asset'': any element, physical or virtual, which can contribute to the successful management of the business area supported by itmSUITE®. An asset can be, for example, a PC, a printer, a software component, a table a machine, etc.<br />
* ''Asset management:'' one of the ''modules ''of itmSUITE®. The full name of it is [[ItmSUITE® - Complementary modules#ASM - Asset Management|ASM - Asset Management]]. It allows to manage ''assets'', It can also refer to the asset management process according to the context. TBC.....<br />
* ''Attribute'': a ''configuration item'' information (e.g. its name, location, date of purchase, etc.).<br />
<br />
== B ==<br />
* ''Balance'': TBD<br />
* ''BaseDN'': TBD<br />
* ''Baseline'': see ''configuration baseline''.<br />
* ''Billing'': a feature, part of the ''[[ItmSUITE® - Core modules#FM - Financial Management|FM - Financial Management]]'' ''module, ''enabling the possibility to create ''invoices'' based on ''timesheets'' or predefined amounts related, or not, to a ''delivery''.<br />
* ''Billing schedule'': a tranche of a ''sales contract'' to be invoiced. The billing schedule may be dependent or not on ''[[glossary|deliveries]]''.<br />
* ''Binding layer'': a graphical frame used in the [[ItmSUITE® - Core modules#CMS - Configuration Management System|CMS - Configuration Management System]] ''module. ''For any object placed in it the relationships between the objects placed and the objects represented by the frame are automatically created. So, for example, a ''binding layer'' may represent an IT service and may be configured to generate the 'is component' relationships with the objects placed in it (e.g. a server is component of the IT service). ''Binding layers'' simplify the management and building of a ''CMS''.<br />
* ''Budget'': TBD<br />
* ''Business language:'' a language used by the itmSUITE® users to communicate within the business processes. See also ''application languages'' and [[Multi language]] management.<br />
* ''BIRT'': an open source software project that provides the BIRT technology platform to create data visualizations and reports that can be embedded into rich client and web applications. The itmSUITE® [[ItmSUITE® - Complementary modules#REP - Reporting Management|REP - Reporting Engine]] allows exactly this embedding. For further information, visit the [http://eclipse.org/birt/about/ BIRT website].<br />
* ''BIRT designer'': one of the two key components of ''BIRT ''allowing to create new reports which can be embedded in itmSUITE®.<br />
* ''BIRT engine'': the component of ''BIRT'' which allows the execution and rendering of reports created through the ''BIRT designer ''and embedded in itmSUITE® as ''.rptdesign'' files.<br />
<br />
== C ==<br />
* ''CAB'': abbreviation for ''change advisory board''. <br />
* ''Change:'' according to ''ITIL®'', a ''change'' is the addition, modification or removal of anything that could have an effect on IT services. ''Changes'' are managed through the ''change management'' process and a ''workflow cartridge'' is available for the ''SM'' ''module'' which supports its execution according to the guidelines provided by ''ITIL®'' and ''ISO/IEC 20000''. <br />
* ''Change advisory board'': TBD <br />
* ''Change authority'': TBD<br />
* ''Change management'': according to ''ITIL®,'' the process responsible for controlling the life cycle of all ''changes'', enabling beneficial changes to be made with minimum disruption to IT services. A ''workflow cartridge''is is made available for the ''SM module ''which supports the execution of the ''change management'' process according to the guidelines provided by ''ITIL® ''and ''ISO/IEC 20000''.<br />
* ''CI'': abbreviation for ''configuration item''.<br />
* ''Client'': a generic term that means a customer, the business or a business customer. itmSUITE® allows to manage ''client'' master data and ''client'' as an entity in ''workflows'' and ''modules''.<br />
* ''CMS'': abbreviation for Configuration Management System.<br />
* ''CMS DB'': TBD<br />
* ''CMS fat client'': a desktop application which enables to access ''CMS'' administration and reporting functionalities. See [[CMS fat client]] page for more information.<br />
* ''CMS server'': TBD<br />
* ''CMS web client'': a browser accessible application which enables to access and update ''CMS'' contents.<br />
* ''Closure cause'': TBD.<br />
* ''Company'': a business organization (legal entity or simply a business unit or a department) which is defined and used for the aim of segregating data. itmSUITE® is natively multi tenancy, meaning it allows to manage different ''companies'' in the same application instance. Only ''users ''login information (including the associated ''roles'') and ''super admin ''may be cross ''companies ''while all the other information are managed at ''company ''level.<br />
* ''Company calendar'': see ''company working days calendar''.<br />
* ''Company working days calendar'': the calendar specifying the working days and time for a specific ''company''.<br />
* ''Component: ''abbreviation for ''dashboard component''.<br />
* ''Configuration baseline'': TBD.<br />
* ''Configuration exploration'': a specific itmSUITE® functionality making possible, starting from a ''configuration item'', to analyse and graphically represent the relationship of it with other ''configuration items''. The number of levels and the scope of the exploration are defined at launch time. ''Configuration exploration'' is available if ''CMS'' ''module'' is installed. See also [[Configuration exploration]] page for more information.<br />
* ''Configuration item'': a specific type of ''asset ''which contributes to the delivery of an IT service.<br />
* ''Configuration management'': see ''service asset and configuration management''.'' ''<br />
* ''Configuration management database'': (CMDB) organized repository of all elements of IT structure which undergo the configuration management process.<br />
* ''Configuration management system'': a set of tools, data and information that is used to support service asset and configuration management. A dedicated ''module'' of ItmSUITE®, [[ItmSUITE®_-_Core_modules#CMS - Configuration Management System|CMS - Configuration Management System]], is dedicated to this. <br />
<br />
* ''Contact'': a referent person related to a ''client ''or a ''supplier ''and his/her information.<br />
* ''Contract'': generally, a legally binding agreement between two or more parties. itmSUITE® allows to manage ''contracts ''master data and ''contracts ''as an entity in various ''modules ''and functionalities. Contracts may be of two types:''sales contracts ''(with ''clients'') and ''purchase contracts ''(with ''suppliers'').''Purchase contracts ''are also often used to manage standard internal cost for ''resources''. This is an example of their flexible use, often for agreements which are not legally binding. ''Contracts'' management is made available only if the [[FM - Financial Management]] ''module'' is active.<br />
* ''Cost occurrence'': an actual cost which is recorded for a ''service ''and, optionally, for a ''ticket'' (therefore a process instance, such as a specific ''change''). <br />
<br />
* ''Cost occurrence dimension'': the type of ''cost occurrence''. Two alternative are possible: "Balance" or "Confirmed". The exact meaning is a convention. "Balance" may refer to an order confirmation while "Confirmed" to the actual occurrence of the cost (e.g. goods delivery).<br />
* ''Creator'': the ''user'' who creates a ''ticket''.<br />
* ''Credit note'': a form or letter sent by a seller to a buyer, stating that a certain amount has been credited to the buyer's. A ''credit note'' is issued in various situations to correct a mistake, such as when an invoice amount is overstated, correct discount rate is not applied, etc. itmSUITE® allows to issue and manage ''credit notes'' within the [[FM - Financial Management]] ''module''.<br />
* ''Custom field'': see ''workflow custom field''.<br />
* ''Custom time ranges'': these are definitions of time frames. These can be used in several other functionalities, for example by the ''self service configuration system''.<br />
<br />
== D ==<br />
* ''DashBoard'': TBD the dashboard ''module''.<br />
* ''Dashboard'': TBD (the elements managed by the DB module).<br />
* ''Dashboard component'': an object, e.g. graphic, which can be included in a ''dashboard''.<br />
* ''Data source'': is a name given to the connection set up to a database. In the context of ''workflow'' management this refers to the a set of data which is used to populate a ''workflow custom field''. <br />
* ''Data view'': views of data at data base level which can be used to create reporting or read operations. ''Data views'' shall not be confused with ''views''.<br />
* ''DB'': abbreviation for ''DashBoard''.<br />
* ''DE'': abbreviation for ''discovery engine''.<br />
* ''Decision matrix'': a rule which makes it possible to calculate the value of a target ''ticket'' ''workflow field'' based on the value of two other influencing (driving) ''workflow fields''.<br />
* ''Delivery'': an expected output of a'' [[glossary|project]]'' or ''[[glossary|service]]'', whether tangible or intangible.<br />
* ''Delivery type'': TBD.<br />
* ''Demand management: ''the process enabling the clients (and their delegated users) of services (e.g. IT services) to ask for new services or changes to those existing. The process includes the analysis and authorization steps needed to authorize the request and activate the fulfilment process (generally managed by means of ''change management'' or ''request fulfilment'' processes). '''<u>NOTE</u>''': this given definition of ''demand management'' is typical of some contexts (IT management in some countries) and does not fully match the ''ITIL®'' one nor the one commonly accepted in some business contexts (a planning methodology used to manage and forecast the demand of products and services). A ''workflow cartridge ''is made available for the ''SM module ''which supports the execution of the ''demand management ''process. See [[Demand Management]] page for more information on this configuration.<br />
* ''Deployment change'': TBD<br />
* ''Deployment change management'': TBD<br />
* ''Discovery engine'': one of the ''modules'' of itmSUITE®. The full name of it is [[ItmSUITE® - Core modules#DE - Discovery Engine|DE - Discovery Engine]]. By installing its agents on IT components, it allows to gather information on hardware, software components and their relationships. The result of the discoveries may be imported in the ''CMS''.<br />
* ''Dynamic solution group'': it is a ''workflow field'' (therefore used in ''tickets'') which contains a list of ''groups''. ''Dynamic solution groups'' are currently 6: DSG1 (also named ''master solution group''), DSG2 (also named ''solution group''), DSG3 (also named "third solution group", DSG4, DSG5 and DSG6.<br />
* ''Document'': TBD<br />
* ''Document position'': a logical repository area where ''documents'' can be stored. The logical repository areas are: "Project", "Timesheet Record", "Milestone", "Purchase Contract", "Sale Contract", "Resource", "Cost Occurence", "Delivery", "Ticket", "Service" and "Invoice/Credit Note".<br />
* ''DSG'': abbreviation for ''dynamic solution group''.<br />
<br />
== E ==<br />
* ''EAC'': abbreviation for ''estimation at completion''.<br />
* ''Earn'': TBD<br />
* ''Earned value'': TBD<br />
* ''EEM:'' abbreviation for ''external event management''.<br />
* ''Estimation'': an overall economic evaluation of a ''service'' or ''project'' or a related to a specific ''ticket'' (process instance). The ''estimation'' may include the following types of costs: effort related (deriving from ''timesheets'' work declarations and associated ''purchase contracts''), expenses related (deriving from expenses declared in ''timesheets'' and the applicable ''purchase contracts'') and cost items related (deriving from specific cost elements such as investments or services). The evaluation may include three cost dimensions: budget, balance and forecast (budget + balance) at a specific ''estimation period''. <br />
* ''Estimation at completion'': TBD<br />
* ''Estimation competence period'': the ''estimation'' can be split in time frames (''estimation competence periods'') for which it is possible to view and update data. The ''estimation competence periods'' can be: the overall ''project'' or ''service'', years or months.<br />
* ''Estimation period'': the date at which all costs of an ''estimation'' are evaluated.<br />
* ''Estimation repository'': the logical repository where ''estimations'' related to ''projects'' or ''services'' (not those related to ''tickets'') can be saved and from where they can be later loaded.<br />
* ''Estimation to completion'': TBD<br />
* ''ETC'': abbreviation for ''estimation to completion''.<br />
* ''External event management: ''one of the ''modules ''of itmSUITE®. The full name of it is [[ItmSUITE® - Complementary modules#EEM - External Event Management|EEM - External Event Management]]. It facilitates the integration of events occurring in systems external to itmSUITE® with the functionalities of itmSUITE® itself or vice versa (e.g. the opening of an itmSUITE® ''ticket'' based on the content of an incoming email).<br />
* ''Event type'': predefined types of occurring activities or outcomes in the domain of itmSUITE®. Examples of ''event types'' are the following: change of the status of a ''ticket activity'', assignment of a ''project activity'' to a ''resource'', a change of status of a ''ticket'', etc. ''Event types'' are associated to an ''event type template'' and sent according to the specified schedule (''notification''). See also [[Notifications management]] page.<br />
<br />
* ''Event type template'': the message template (an html file) related to an ''event type'' which is used when a notification for the ''event type'' is triggered. For more information on how to edit this type of file, see also [[Notifications management]] page.<br />
* ''Exploration'': see ''configuration exploration''.<br />
<br />
== F ==<br />
* ''Filter'': it is a set of selection criteria to be applied to a ''view''. ''Filters'' can be created and distributed to ''users''. See [[Filters management|Filter management]] page for more details.<br />
* ''Field'': see ''workflow field''.<br />
* ''Financial management:'' one of the ''modules ''of itmSUITE®. The full name of it is [[ItmSUITE® - Complementary modules#FM - Financial Management|FM - Financial Management]]. It allows to manage financial aspects (budget, balance data and forecasting) of ''projects'', ''services'' and their related entities (''project activities'', ''tickets'', and ''ticket activities'').<br />
* ''FM:'' abbreviation for ''financial management''.<br />
* ''Form section'': see workflow form section.<br />
<br />
== G ==<br />
* ''Grant'': a permission given to a ''role'' to view a specific ''workflow field''. ''Grants'' are given for specific ''workflow statuses'' in the context of ''workflow'' configuration.<br />
* ''Grid mode'': a component which allows to manage records of data in a way similar to what happens in a spreadsheet. See [[grid mode]] for more information on the features and use of this component.<br />
* ''Grid search'': TBD<br />
* ''Group'': a team of people but also one of the ''workflow ''related ''roles.''For example,'' groups ''can be used to assign ''tickets ''and ''ticket activities''.<br />
* ''Group manager'': the resource coordinating or responsible for a'' group''.<br />
<br />
== H ==<br />
''Help editor'': TBD.<br />
<br />
== I ==<br />
* ''Impact analysis'': a functionality of ''CMS''. Starting from a ''configuration item'','' ''it allows to find the impact of its failure on other ''configuration items'' of type IT service.<br />
* ''Impact chain'': TBD.<br />
* ''Incident:'' according to ''ITIL®'', an ''incident'' is an unplanned interruption to an IT service or reduction in the quality of an IT service. Failure of a configuration item that has not yet affected service is also an incident – for example, failure of one disk from a mirror set. ''Incidents'' are managed through the ''incident management'' process and a ''workflow cartridge'' is available for the ''SM'' ''module'' which supports its execution according to the guidelines provided by ''ITIL®'' and ''ISO/IEC 20000''.<br />
* ''Incident management'': according to ''ITIL®, ''the process responsible for for managing the lifecycle of all ''incidents''. ''Incident management'' ensures that normal service operation is restored as quickly as possible and the business impact is minimized. A ''workflow cartridge ''is made available for the ''SM module ''which supports the execution of the ''incident management ''process according to the guidelines provided by ''ITIL® ''and''ISO/IEC 20000''. See [[Incident Management]] page for more information on this configuration.<br />
* ''Invoice'': a commercial document issued by a seller to a buyer. It identifies both the trading parties and lists, describes, and quantifies the items sold, prices, discounts (if any), etc. itmSUITE® allows to issue and manage ''invoices ''within the [[FM - Financial Management]] ''module''.<br />
* ''Invoice attachment'': an attachment related to a specific ''invoice'', specifying the activities and or expenses included to which the ''invoice'' refer. ''Invoice attachments'' may be automatically generated during the billing process. See also ''billing'' and ''invoice''.<br />
* ''ISO/IEC 20000'': an international standard for the quality of ''IT service management''. See also the [http://www.iso.org/ ISO website] for more information.<br />
* ''ITIL®'': a set of best-practice publications for ''IT service management''. Owned by Axelos limited, ''ITIL®'' gives guidance on the provision of quality IT services and the processes, functions and other capabilities needed to support them. The ''ITIL®'' framework is based on a service lifecycle and consists of five lifecycle stages (service strategy, service design, service transition, service operation and continual service improvement), each of which has its own supporting publication. See also the ''ITIL® ''[http://www.itil-officialsite.com official site] for more information. ''ITIL® ''is a registered trade mark of Axelos limited.<br />
* ''itmSUITE'': TBD<br />
* ''IT Service Management'': the implementation and management of quality IT services that meet the needs of the business. IT service management is performed by IT service providers through an appropriate mix of people, process and information technology.<br />
<br />
== K ==<br />
* ''Key business entity'': one of the key entities managed by itmSUITE® (''resources'', ''projects'', ''timesheets'', ''tickets'', etc.).<br />
* ''Knowledge'': is one of the ''entities related to ''workflow engine''. See the ''[[Workflow engine]]'' page for more information.<br />
* ''Knowledge Portal'': TBD. <br />
* ''Known error'': a ''problem'' that has a documented root cause and/or a ''workaround''. The ''known error management'' process is responsible to manage ''known errors'' lifecycle. ''Known errors'' are typically used to provide (by publishing) ''workarounds'' to ''service'' users until a final solution for the underlying ''problem'' is not found.<br />
* ''Known error management'': the process responsible of managing the life cycle of ''known errors''. A ''workflow cartridge ''is made available for the ''SM module ''which supports the execution of the ''incident management ''process according to the guidelines provided by ''ITIL® ''and ''ISO/IEC 20000''. See [[Known Error Management]] page for more information on this configuration.<br />
* ''KPI'': Key Performance Indicator, TBD<br />
<br />
== L ==<br />
* ''Language Management'': TDB<br />
* ''LDAP'': TBD<br />
* ''License'': the activation key enabling the use of itmSUITE® ''modules'' by ''users''. The ''license'' articulation is per ''module'' and per ''user type''. View the [[License]] details page for more information.<br />
* ''List mode'': TBD non EJS mode, see also ''grid mode''.<br />
* ''Log info'': the information about the access of ''users'' to itmSUITE® automatically recorded by the system. See [[Log management]] page for more info.<br />
<br />
== M ==<br />
* ''Manager'': a ''user'' with associated ''user type'' "Manager". A ''manager'' can configure ''company'' master data according to the privileges set in ''MURM''. Furthermore, he/she is automatically associated to the static ''role'' "Manager" which can be used in ''workflows'' and ''projects'' configurations. <br />
* ''Manager row'': data for a'' timesheet'' corresponding to what a ''manager'' approves (usually corresponding to'' company'' billable values). <br />
* ''Master data'': the set of data agreed and shared across itmSUITE® which supports the management of the ''key business entities''. For the list of ''master data'' tables refer to [[ItmSUITE® - Cross master data configuration|cross master data configuration]]. <br />
* ''Matrix timesheet'': TBD <br />
* ''MB'': abbreviation for ''message bus''. <br />
* ''MDMM (Master Data Management Matrix)'': the functionality which allows to manage grants for the records of some master data. See [[MDMM management]] page for more details. <br />
* ''Master solution group'': a dynamic ''workflow role'' (e.g. used to define rights for ''workflow transitions'' or ''workflow fields''). The ''workflow field'' <u>Master Solution Group</u> let define the ''master solution group'' among available ''solution groups'' and this assignment can be done for each ''ticket'' instance. ''Master solution group'' is also named DSG1 (see ''dynamic solution groups'').<br />
* ''Menu'': a link to a management functionality of itmSUITE®. These links are provided on the left of the itmSUITE® screen and changes according to the privileges and the configuration of their visibility. See the [[Menu management]] page for more information. <br />
* ''Message'': a communication, caracterized by a subject, content, recipient(s) and, optionally, attachment(s) which can be sent through itmSUITE® ''message system'' to ''users'' or external recipients (in such a case the communication is sent through an email service). The ''message'' can also be based on a'' ticket message template''. See the [[Message system]] page for more information. <br />
* ''Message bus'': TBD <br />
* ''Message system'': one of the technical component of itmSUITE®, the ''message system'' is the engine dispatching all the messages automatically or manually generated within the system. The ''message system'' has a user interface which allows to receive and send messages and it can be synchronized with external mailing systems. See the [[Message system]] page for more information. <br />
* ''Message template'': TBD.<br />
* ''Metric'': TBD.<br />
* ''Module'': one of the components of itmSUITE® which makes avaiable a specific sets of functionalities. ''Modules'' may be core or complementary. Core modules can be installed and activated autonomously. Complementary ''modules'' require the presence of at least one core ''module''. For a list of core modules and a description of their features refer to [[itmSUITE® - Core modules]]. For a list of complementary modules and a description of their features refer to [[itmSUITE® - Complementary modules]]. <br />
* ''Model'': a set of ''configuration items'' and their ''relationship'' represented according to specific modelling conventions which includes the definition of the entities, relationship types among them and graphical appearance. <br />
* ''Monitoring system configuration'': TBD <br />
* ''MSC'': abbreviation for ''monitoring system configuration''. <br />
* ''MSG'': abbreviation for ''master solution group''. <br />
* ''MURM'' (Managers User Rights Management); the functionality used to grant rights for ''managers''. This functionality can be accessed from '''''General/Company/MURM'''''.<br />
<br />
== N ==<br />
* ''NTLM'': TBD<br />
* ''News'': they are broadcast communications relevant for the ''users'' or part of the ''users'' of itmSUITE®. The system makes available a management system to broadcast ''news'' to the target audience and for specific time frames. See [[News management]] page for more information.<br />
* ''News management'': TBD<br />
<br />
* ''Notification'': the configured schedule to communicate the ''event type template'' message related to an ''event type''. ''Notifications'' are sent via the itmSUITE® ''message system''. See also [[Notifications management]] page.<br />
<br />
== O ==<br />
* ''Object'': in [[ItmSUITE® - Core modules#CMS - Configuration Management System|CMS - Configuration Management System]] context, an element which can be used to represent an ''asset'' or a ''configuration item''.<br />
* ''Objective'': objective characterized by a metric and targets which can be set and calculated by means of the ''OCE'' ''module''. They can be typically used in order to manage service levels.<br />
* ''Objectives calculation engine'': a complementary module of itmSUITE®. The full name of it is [[OCE - Service Level Management]]. This ''module'' enables to manage ''service levels'' for ''service'' and ''projects''.<br />
* ''OCE'': abbreviation for ''objectives calculation engine''.<br />
* ''Organizational unit'': the representation of the organizational structure of a ''client''. Levels of the organization can be defined by means of tree nodes and ''clients'<nowiki/>'' associated ''resources'' can be related to each. The ''service provider''' s organization can be mapped by using a fictitious ''client''.<br />
* ''OU'': abbreviation for''organizational unit''.<br />
<br />
== P ==<br />
* ''Passive channel'': TBD<br />
* ''PBS'': see ''product breakdown structure''.<br />
* ''Percentage complete'' (''% complete''): TBD<br />
* ''Personal preferences'': the set of ''user''<nowiki/>'s preferences concerning the use of itmSUITE® which can be managed by the ''user''. See the [[Personal options|Personal preferences]] page for more details.<br />
* ''PFD'': see product flow diagram.<br />
* ''Planned % complete'': TBD<br />
* ''Pm'': abbreviation for ''project manager''.<br />
* ''PM'': abbreviation for ''project and portfolio management''. <br />
* ''PM row'': data for a ''timesheet'' corresponding to what the ''project manager'' or ''service manager'' approves (the ''company'' cost). <br />
* ''Portfolio analysis'': TBD report <br />
* ''Portfolio gantt'': TBD <br />
* ''Price Items'': TBD<br />
* ''Problem: ''according to ''ITIL®'', a ''problem'' is a cause of one or more ''incidents''. The cause is not usually known at the time a ''problem'' record is created, and the ''problem management'' process is responsible for further investigation. ''Problems'' are managed via the ''problem management'' process and a ''workflow cartridge'' is available for the ''SM'' ''module'' which supports its execution according to the guidelines provided by ''ITIL®'' and ''ISO/IEC 20000''. <br />
* ''Problem management'': according to ''ITIL®, ''the process responsible for managing the lifecycle of all ''problems''. ''Problem management'' proactively prevents ''incidents'' from happening and minimizes the impact of ''incidents'' that cannot be prevented. A ''workflow cartridge ''is made available for the ''SM module ''which supports the execution of the ''problem management ''process according to the guidelines provided by ''ITIL® ''and ''ISO/IEC 20000''. <br />
* ''Process owner'': TBD <br />
* ''Product'': this is any product or service provided by the ''company'' internally or to its clients. itmSUITE® allows to manage ''product ''master data ''product'' as an entity in ''workflows ''and ''modules''.See also [[ItmSUITE® - Introduction to basic configuration|Introduction to basic configuration]] page for ''products'' configuration. <br />
<br />
* ''Product breakdown structure'': a hierarchy of all the ''deliveries'' to be produced during a ''project'' or ''service''. <br />
* ''Product flow diagram'': a diagram showing the sequence of production and interdependencies of the ''deliveries'' listed in a ''product breakdown structure''. <br />
* ''Project'': a temporary organization that is created for the purpose of delivering one or more business products according to an agreed Business Case. For this purpose, in itmSUITE® a set of entities, their attributes and related management functionalities are made available to the'' users'' which play a role in the ''project''. <br />
* ''Project activity'': an activity scheduled for a ''project''. This is one of the information managed by itmSUITE[[ItmSUITE® - Core modules|®]] for a ''project''. <br />
* ''Project activity type'': a categorization for ''project activities''. <br />
* ''Project and portfolio management'': one of the ''modules ''of itmSUITE®. The full name of it is [[ItmSUITE® - Core modules#PM - Project and Portfolio Management|PM - Project and Portfolio Management]]. This ''module'' enables to manage ''projects'' and portfolios of ''projects''. <br />
* ''Project currency'': TBD. <br />
* ''Project delivery'': see ''delivery''. <br />
* ''Project explorer'': TBD (CMS context) <br />
* ''Project issue'': TBD <br />
* ''Project manager'': this is a special role on a ''project'', automatically inheriting specific rights and visibility of data for it. <br />
* ''Project milestone'': a structured check of the status of a ''project'' where several information (''estimation'', progress, comments, etc.) are gathered and stored. These information may be used for ''project'' control (see [[semaphores]]). <br />
* ''Project off-specs'': TBD <br />
* ''Project portfolio'': TBD <br />
* ''Project RFC'': TBD <br />
* ''Project risk'': see ''risk''. <br />
* ''Project semaphore'': see ''semaphore''. <br />
* ''Purchase contract'': see ''contract''.<br />
* ''Purchase tariff'': Tariff used by the system to calculate [[Timesheet]] costs. Tariff is usually set as Daily value.<br />
<br />
== Q ==<br />
<br />
== R ==<br />
* ''RE'': abbreviation for ''reconciliation engine''. <br />
* ''REP: ''abbreviation for ''reporting management''.<br />
* ''Reconciliation'': a process performed by the ''reconciliation engine'' which allows to import information from a data source into the ''CMS'' in a controlled way (deciding which information for which ''configuration item'' to import).<br />
* ''Reconciliation engine: ''one of the ''modules ''of itmSUITE®. The full name of it is [[ItmSUITE® - Complementary modules#RE - Reconciliation Engine|RE - Reconciliation Engine]]. This ''module ''enables the ''reconciliation'' process.<br />
* ''RfC'': abbreviation for ''Request for Change''.<br />
* ''Relationship'': a relationship between two ''configuration items''.<br />
* ''Release'': according to ''ITIL®'', one or more ''changes'' to an IT service that are built, tested and deployed together. A single release may include ''changes'' to hardware, software, documentation, processes and other components. ''Releases'' are managed through the ''release and deployment management'' process and a ''workflow cartridge'' is made available for the ''SM'' ''module'' which supports its execution according to the guidelines provided by ''ITIL®'' and ''ISO/IEC 20000''.<br />
* ''Release and deployment management: ''according to ''ITIL®'', the process responsible for planning, scheduling and controlling the build, test and deployment of ''releases'', and for delivering new functionality required by the business while protecting the integrity of existing ''services''. A ''workflow cartridge'' is available for the ''SM'' ''module'' which supports its execution according to the guidelines provided by ''ITIL®'' and ''ISO/IEC 20000''. See [[Release Management]] page for more information on this configuration.<br />
* ''Release management'': see ''release and deployment management''.<br />
* ''Report'': a report generated with ''reporting management''.<br />
* ''Reporting management: ''one of the ''modules ''of itmSUITE®. The full name of it is [[ItmSUITE® - Complementary modules#REP - Reporting Management|REP - Reporting Engine]]. This modules enables to define and embed new reports in addition to those predefined in itmSUITE®.<br />
* ''Report template'': TBD<br />
* ''Request'': see ''self service request''.<br />
* ''Request for Change'': TBD.<br />
* ''Request fulfilment: ''according to ''ITIL®, t''he process responsible for managing the lifec ycle of all ''service requests''. A ''workflow cartridge'' is available for the ''SM'' ''module'' which supports its execution according to the guidelines provided by ''ITIL®'' and ''ISO/IEC 20000''. See [[Request Fulfilment]] page for more information on this configuration.<br />
* ''Resource'': term used to refer to a human resource and his/her associated information managed in itmSUITE®. A ''resource'' may or may not have an account and, therefore, be a ''user''.<br />
* ''Resource row'': data for a ''timesheet'' corresponding to what declared by the ''resource''.<br />
* ''Resolution cause'': TBD<br />
* ''Risk'': an uncertain event or set of events that, should it occur, will have an effect on the achievement of objectives. A risk is measured by a combination of the probability of a perceived threat or opportunity occurring, and the magnitude of its impact on objectives. Risks can be managed for ''[[glossary|projects]]'' and ''[[glossary|services]]'' in the ''<u>Issues/Risks</u>'' tab.<br />
* ''Role'': a usage profile determining ''user''<nowiki/>'s rights on data and functionalities. More than a ''role'' may be associated to a ''user''. ''Roles'' are distinguished in ''application level'' ''roles'', ''projects'' and ''services'' related ''roles'', ''workflows'' related'' roles. Application level'' ''roles'' are set at ''user''<nowiki/>'s level and related to the available ''licenses'' (they determine the number of users who may be activated). ''Project'' and ''service'' roles are dynamically assigned to ''users'' in the context of each ''project'' or ''service''. ''Workflows roles'' are dynamically assigned to ''users'' in the context of each ''workflow'' See also ''[[Roles]]'' page for more information.<br />
* ''.rptdesign'': extension for a file created by the ''BIRT designer'' component.<br />
<br />
== S ==<br />
* ''SACM'': abbreviation for ''service asset and Configuration management''.<br />
* ''Sales contract'': see ''contract''.<br />
* ''Sale role'': TBD.<br />
* ''Sales role tarif'': TBD''.''<br />
* ''Search context'': the definition of the scope where a search, with a '''Quick Search''' (available right on the top part of the itmSUITE® screen). ''Search contexts ''are of three types: preinstalled (and not modifiable), published by a ''manager'' or defined by a ''user''. ''Search contexts'' are listed next to the '''Quick Search''' command and their scope can be tailored on any part of itmSUITE®. See [[search context management]] page for more information.<br />
* ''Self service'': see ''self service portal''.<br />
* ''Self service category'': a part of the organization of the ''self service portal''. ''Self service categories'' may be defined for each ''self service topic'' and they appear as a tree on left side of the ''self service portal ''with a maximum two level of depth.<br />
* ''Self service portal'': a functionality of itmSUITE® enabling ''users'' to quickly open ''tickets ''by browsing a structured presentation of the available ones. The levels of presentation are ''self service topics'' (highest level), ''self service category'' (intermediate level) and ''self service requests'' (lowest level). itmSUITE® makes it possible to define the visibility of data according to needs. See the [[self service portal]] page for more information. <br />
* ''Self service request'': the lowest element for the structure of a ''self service portal''. For each ''self service category'' it is possible to define one or more ''self service requests''. ''Self service requests'' are configured to trigger the activation of a ''workflow'', also passing some initial settings to it.<br />
* ''Self service topic'': a part of the organization of the ''self service portal''. ''Self service topics ''may be customized with icons and they appear in the upper part of the ''self service portal''. Their selection influences the visibility of ''self service categories''.<br />
* ''Semaphore'': a metric which is used to monitor a particular aspect of the status of a'' project ''(''project semaphore'') or ''service'' (''service semaphore''). Threshold values shall be defined for each ''semaphore'' and are used in reports and messages where the status of a ''project'' is reported. Se the [[semaphores]] dedicated page for more information.<br />
* ''Service'': a mean to provide value to customers by facilitating outcomes customers wants to achieve using resources and capabilities. For this purpose, in itmSUITE®, a set of entities, their attributes and related management functionalities are made available to the ''users ''which play a role in the delivery of the ''service''.<br />
* ''Service activity'': an activity scheduled for a ''service''. This is one of the information managed by itmSUITE® <nowiki/>for a ''service''. <br />
* ''Service asset and configuration management'': according to ''ITIL®'', the process responsible for ensuring that the assets required to deliver services are properly controlled, and that accurate and reliable information about those assets is available when and where it is needed. This information includes details of how the assets have been configured and the relationships between assets. Service asset and configuration management purpose and objectives are fully supported by the ''CMS'' ''module'' of itmSUITE®.<br />
* ''Service catalogue'': TBD<br />
* ''Service delivery'': see ''delivery''. <br />
* ''Service desk:'' according to ''ITIL®, t''he single point of contact between the service provider and the users. A typical service desk manages incidents and service requests, and also handles communication with the users. itmSUITE® fully enables the implementation and management of a ''service desk''. <br />
* ''Service desk and service management: ''one of the ''modules ''of itmSUITE®. The full name of it is [[ItmSUITE® - Core modules#SM - Service Desk and Service Management|SM - Service Desk and Service Management]]. This ''module ''enables to manage ''services''. <br />
* ''Service level'': according to ''ITIL®, a ''measured and reported achievement against one or more service level targets. The term is sometimes used informally to mean service level target. In itmSUITE® ''service levels'' can be defined and measured by means of the [[OCE - Service Level Management]] ''module''.<br />
* ''Service level management'': according to ''ITIL®, t''he process responsible for negotiating achievable service level agreements and ensuring that these are met. It is responsible for ensuring that all ''IT service management processes'', operational level agreements and underpinning contracts are appropriate for the agreed ''service level'' targets. ''Service level management'' monitors and reports on service levels, holds regular service reviews with customers, and identifies required improvements. Several itmSUITE® ''modules'' support the implementation and management of the ''service level management'' process: [[OCE - Service Level Management]] supports the definition, calculation and use (e.g. in ''ticket'' lists or forms) of the ''service levels''; [[ItmSUITE® - Core modules#SM - Service Desk and Service Management|SM - Service Desk and Service Management]] supports the definition of processes to manage service reviews and service improvements; [[ItmSUITE® - Complementary modules#REP - Reporting Management|REP - Reporting Engine]] supports the monitoring and reporting of ''service levels''.<br />
* ''Service manager'': this is a special ''role'' on a ''service'', automatically inheriting specific rights and visibility of data for it. In ''ITIL®'', this is a generic term for any manager within the service provider. Most commonly used to refer to a business relationship manager, a process manager or a senior manager with responsibility for IT services overall. <br />
* ''Service provider'': TBD <br />
* ''Service request'': according to ''ITIL®, ''a formal request from a user for something to be provided – for example, a request for information or advice; to reset a password; or to install a workstation for a new user. ''Service requests'' are managed by the ''request fulfilment'' process, usually in conjunction with the ''service desk''. A ''workflow cartridge'' is available for the ''SM'' ''module'' which supports its execution according to the guidelines provided by ''ITIL®'' and ''ISO/IEC 20000''. See [[Request Fulfilment]] page for more information on this configuration. ''Service requests'' should not be confused ''self service request'' although ''self service requests'' may often be a configured to instantiate ''service requests''.<br />
* ''Service review'': a structured check of the status of a ''service ''where several information (''estimation'', progress, comments, etc.) are gathered and stored. These information may be used for ''service ''control (see [[semaphores]]). <br />
* ''Service risk'': see ''risk''. <br />
* ''Service semaphore'': see ''semaphore''. <br />
* ''SG'': abbreviation for ''solution group''. <br />
* ''Sm'': abbreviation for ''service manager''. <br />
* ''SM'': abbreviation for ''service desk and service management.''<br />
* ''Solution group'': see groups. A ''solution group'' is generally meant as a ''group'' dedicated to the resolution of ''incidents'' and/or ''problems''. ''Solution group'' is also named DSG2 (see also ''dynamic solution groups'').<br />
* ''Solution group manager'': see ''group manager''. <br />
* ''SRCS'': abbreviation for Self service Request Configuration System, see ''self service''.<br />
* ''Standard change'': TBD<br />
* ''Standard function'': a set of functions delivered for reporting purpose<br />
* ''Status'': TBD<br />
* ''Superadmin'': a special ''user type''. A ''superadmin'' ''user'' is created with predefined access credentials when itmSUITE® is initially installed. The ''superadmin'' may: create new ''companies'', create other ''users'' (either ''superadmins'' or ''users'' with ''user type'' "Admin" enabled to configure the ''companies'' to which they are associated) and perform some key essential settings in order to enable other ''users'' to complete ''company'' configurations. For more information, have a look to the ''[[superadmin]]'' page.<br />
* ''Suppliers'': a generic term that means a supplier providing services, resources and/or goods to a ''company''. itmSUITE® allows to manage ''supplier ''master data and ''supplier ''as an entity in ''workflows ''and ''modules''.<br />
* ''Symbol'': in CMS context - TBD<br />
<br />
== T ==<br />
* ''Third solution group'': an alternative name for DSG3 (see ''dynamic solution groups'').<br />
* ''Ticket'': term used to refer to an instance of a process managed through the ''workflow engine''.<br />
* ''Ticket activity'': an activity scheduled to manage a ''ticket''. <br />
* ''Ticket activities template'': a predefined and configured set of ''ticket activities'' in order to manage a ''ticket''. <br />
* ''Ticket estimation'': a ''ticket'' estimation (budget, balance and estimation to complete) made for a ''ticket'' in its ''<u>Estimation</u>'' section. <br />
* ''Ticket message template'': a predefined model which is used to create a ''message''. For example, this is used for the creation of ''messages'' from ''tickets''. <br />
* ''Ticket type'': TBD<br />
* ''Ticket worker'': a ''resource'' assigned to work on a specific ''ticket''. This is also a ''workflow'' related ''role''. <br />
* ''Time zone'': the time zone of reference used to read date/time data which can be chosen by a ''resource'' (see ''personal preferences''). A time zone is set for the system and date/time values are converted and shown to the ''user'' according to the chosen ''time zone'' for the ''resource''. For more information see [[time zone management]] page.<br />
<br />
* ''Timesheet'': a record corresponding to a declaration of work done. This work can be related to a ''project'' or a a ''service ''or to any detailed elements (such as ''project activities'', ''service activities'', or ''tickets'' or ''ticket activities'') of them.<br />
* ''Timesheet attachment'': an attachment (document) related to a ''timesheet''. A ''timesheet attachment'' is generally used to document expenses.<br />
* ''To do list'': TBD<br />
* ''Transition'': see ''workflow transition''.<br />
* ''Tuple'': TBD<br />
<br />
== U ==<br />
* ''User'': the login information which can be associated to one ''resource'' per ''company''. A ''resource'' with an active ''user'' can enter and use itmSUITE® according to the configured grants. Only a ''user'' can be associated with a ''resource'' per each ''company'' (''a'' user may be associated to different ''resources'' in different ''companies''). The association of a ''user'' to a ''resource'' is not mandatory. ''Users'' should have one or more ''user type''.<br />
* ''User type'': there are different types of ''users'' ("Requester", "Resource", "Project/Service Manager", "Manager", "Admin" and "Superadmin"). one or more ''user types'' may be associated to a ''user''. The association of a ''user type'' also enables some related functionalities: see [[Users and resources]] and [[Roles]] pages for additional information.<br />
<br />
== V ==<br />
* VAT: TBD<br />
* ''VCE'': abbreviation for ''Visual Condition Editor''.<br />
* ''VCE condition'': a boolean expression defined with the ''Visual Condition Editor''.<br />
* ''View'': is a preconfigured selectionof attributes and associated preferences (including a ''filter'') to list records for an itmSUITE® managed entity (e.g. ''projects'', ''services''). ''Views'' can be created and distributed to ''users''. See [[Views management]] page for more details.<br />
* ''Visual Condition Editor'': TBD. See also ''[[visual condition editor]]'' page.<br />
== W ==<br />
* ''Workaround'': according to ''ITIL®, r''educing or eliminating the impact of an ''incident'' or ''problem'' for which a full resolution is not yet available – for example, by restarting a failed configuration item. ''Workarounds'' are documented in ''known error'' records. The ''known error management'' process is responsible for the life cycle of ''knonw errors''.<br />
* ''Workflow'': a business process, made of a sequence of activities transforming inputs into outputs with the aim to achieve specific outcomes. With itmSUITE® it is possible to support the execution of ''workflows ''by means of the ''workflow engine''. See the ''[[Workflow engine]] ''page for more information.<br />
* ''Workflow administrative status'': a field among those manageable for a ''workflow''. The field represents the administrative status of the ''workflow'' instance which, in turn, plays a role in the billing processes managed by the ''financial management'' module. <br />
<br />
* ''Workflow cartridge'': the set of configuration settings which define the contents and execution of a ''workflow'' by means of the ''workflow engine''. See the ''[[Workflow engine]]'' page for more information. <br />
* ''Workflow causal'': when transitioning from a ''workflow status'' to another it is possible to configure the ''workflow engine'' so that it requires or simply enables to specify the reason for the transition itself. This reason is known as ''workflow causal'' and it can be categorized using ''workflow causal types'' (e.g. all the possible workflow reasons to move from a source status to a closed status). <br />
* ''Workflow causal type'': a categorization of ''workflow causal''. <br />
* ''Workflow conditions'': Boolean expressions used to influence the visibility or possibility to edit ''workflow fields'' by ''users''. The Boolean expressions may take into consideration attributes of system entities (e.g. ''projects'', ''services'', ''tickets'', etc.). <br />
* ''Workflow custom field'': see ''workflow fields''.<br />
* ''Workflow engine'': the component of itmSUITE®, part of the [[ItmSUITE® - Core modules|SM - Service Desk and Service Management]] ''module'', which allows to configure and execute ''workflows''.See the ''[[Workflow engine]] ''page for more information.<br />
* ''Workflow explorer'': TBD<br />
* ''Workflow field'': a component of a ''workflow ''corresponding to a managed entity attribute which can be used in a ''workflow form''. ''Workflow fields'' can be of two types: "predefined" and "custom". Predefined ''workflow fields'' are pre installed and available for any ''workflow'' while custom ones can be specifically defined and managed for a ''workflow''.<br />
* ''Workflow form'': TBD.<br />
* ''Workflow form section'': TBD.<br />
<br />
* ''Workflow operational status'': see ''workflow status''.<br />
* ''Workflow notifications'': TBD.<br />
* ''Workflow role'': see ''role''.<br />
* ''Workflow status'': a condition of a ''workflow ''instance. ''Workflow statuses'' may be defined by the ''process owners ''and are of two types: "normal" and "legacy". TBD<br />
* ''Workflow Activity Template Options'': Options at ''workflow'' level that enable different behaviour of ''Ticket activity'' in a ''Ticket''<br />
* ''Workflow transition'': the rule allowing ''users'' to pass from a ''workflow status'' to another. Rights to execute ''workflow transitions'' are part of the ''workflow'' configuration.<br />
* ''Workspace'': TBD<br />
<br />
== X ==<br />
<br />
== Y ==<br />
<br />
== Z ==<br />
<br />
[[category:Glossary]]</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3892Resources and Groups2018-06-12T10:29:30Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different Address. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different Documents. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
For each ''resource'' is possible to Manage Configuration Item. The session enables the user to <b>Add and Associate</b>, <b>Assign to Requester </b> a configuration items. The possibility to see or manage the configuration is granted via the <u>''Privileges''</u> tab, see below.<br />
Anyway if ''[[Glossary | Configuration Item ]]'' are associated to the ''resource'' some property is show to the user. For further detail refer to [[ASM - Asset and Service Management]]<br />
<br />
For each ''resource'' is possible to see the list of ''[[Glossary |Project ]]'' / ''[[GlossaryService]]'' he/she is involved. The <u>''Project/Service''</u> tab show also if the resource is "On Budget" on a specific project/service.<br />
<br />
For each ''resource'' is possible to see the list of ''[[Glossary |SRCS ]]'' he/she has been enabled. <br />
<br />
For each ''resource'' is possible to manage the assignment of resource to specific ''group''.<br />
<br />
The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of groups. Note:<br />
Adding a resource to groups means add he/she as a Group Member<br />
Deleting resource from a groups means delete he/she as a Group Member<br />
<br />
<br />
== Group Management process == <br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Group || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|}<br />
<br />
<br />
<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3891Resources and Groups2018-06-12T10:04:54Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different Address. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different Documents. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Private" || so only the people that can manage the ''resource'' can manage the document.<br />
|-<br />
| "Public" || in this case the system enable to select the "All Users" flag.<br />
|}<br />
|-<br />
| "Description" ||Additional document description<br />
|-<br />
| "Upload Document" ||document full path or link.<br />
|}<br />
<br />
<br />
== Group Management process == <br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Group || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
<br />
|}<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3890Resources and Groups2018-06-12T09:56:11Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different Address. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
For each ''resource'' is possible to add different Documents. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of documents.<br />
<br />
The list of fields is shown in the table below:<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Name" || Document name. Populated automatically with the file name, can be change by the user.<br />
|-<br />
| "Topic" || Identitfy the area of the document. The Topic follow the document taxomony<br />
|-<br />
| "Type" || Identitfy the type of document. The Type follow the document taxomony.<br />
|-<br />
| "Format" || Document can be store in the itmSUITE® Database,default optiion or linked to an external source. <br />
|-<br />
| "Visibility" || This Option enable the user to set the Document visibility. <br />
<br />
|}<br />
<br />
|}<br />
<br />
<br />
== Group Management process == <br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Group || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
<br />
|}<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertulettihttp://wiki.itmsuite.eu/index.php?title=Resources_and_Groups&diff=3887Resources and Groups2018-06-12T09:44:15Z<p>Francesco.bertuletti: </p>
<hr />
<div>itmSUITE® manage resources and Groups as way to profile the user to the System.<br />
<br />
''[[Glossary|Resource]]'' is linked to a ''[[Glossary|User]]'' and can belongs to a different Groups.<br />
''[[Glossary|Group]]'' is used to profile the resources and assign to them different roles in the system.<br />
<br />
The main point treated in the guide are:<br />
# Resource Management process<br />
# Group Management process<br />
<br />
== Resource Management process == <br />
<br />
The following table report the process the ''resource'' is involved<br />
<br />
<br />
{| class="wikitable"<br />
! Resource Management!! Description<br />
|-<br />
| Resource Definition || See below<br />
|-<br />
| Add Resource to Group || See below<br />
|-<br />
| Add Resource to Project / Service|| ''[[ vvv |Resource on Project]]''<br />
|-<br />
| Enable a Resource on Service Catalogue Request (SRCS)|| ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
|-<br />
| Synchronization User & Resource with Active Directory || ''[[ vvv | User and Resource Synchronization]]''<br />
<br />
|}<br />
<br />
=== Resource Definition ===<br />
<br />
Manage the ''Resource'' is the entry point of Human management at the system.<br />
''Resource'' can be associate to a ''User’, so he/she has a login or can be a standalone resource.<br />
<br />
Resource management is done by a Manager ''[[Glossary | Role]]'', using the <b>Resources/ Resources </b><br />
This session enable the Manager / Administrator to: <b> Add<b>, <b> Copy </b> and <b> filter</b> <br />
<br />
To perform the copy of the ''Resource'' is necessary to select an existing ''Resource''.<br />
<br />
The Resource form presents nine tabs:<br />
<br />
# General<br />
# Address<br />
# Document<br />
# Configuration Items<br />
# Project / Service <br />
# Service Request<br />
# Groups<br />
# Privileges<br />
# Cost Items<br />
<br />
here below the list of fields present into the General tab:<br />
<br />
{| class="wikitable"<br />
! Field !! Description<br />
|-<br />
| "Creation User" || Contains the ''full name'' of resource that has created the record. Non editable.<br />
|-<br />
| "Creation Date" || Contains the ''Date time'' of record registration. Non editable.<br />
|-<br />
| "Edit User" || Contains the ''full name'' of the last resource that has saved the record. Non editable.<br />
|-<br />
| "Edit Date" || Contains the ''last Date time'' of record modification. Non editable.<br />
|-<br />
| "Status" || This field identify the ''supplier' status, available values are:<br />
{| class="wikitable"<br />
! Status!! Description<br />
|-<br />
| Inactive || Initial status of Resource enable the ''Manager'' to set all the properties<br />
|-<br />
| Active || Status to set if the Resource to get it operational<br />
|-<br />
| Cancelled || Status to set if the Resource is no more operational<br />
|}<br />
|-<br />
| "Code" || Company internal number of the resource. Non editable.<br />
|-<br />
| "Name" || Name of the Resource.<br />
|-<br />
| "Surname" || Surname of the Resource.<br />
|-<br />
| "Birthday" || Date of Birth of the Resource.<br />
|-<br />
| "Birth Place" || Place of Birth of the Resource.<br />
|-<br />
| "Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/Resource Type''</b>.<br />
|-<br />
| "External code" || This is an attribute of the ''Resource''. Usually is used as external key toward other Company software. E.g.: SAP Employee Number.<br />
|-<br />
| "Country" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Supplier" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Supplier Management/Suppliers''</b>.<br />
|-<br />
| "Sale Role" || This information determines the define the Default profile that will be used by the billing process. The master data for this field are present in <b>''/General/Resources/Sale Roles''</b>.<br />
|-<br />
| "Purchase Role" || This information determines the define the Default profile that will be used to charge costs. The master data for this field are present in <b>General/ Resources/Purchase Roles</b><br />
|-<br />
| "Is customer Resource" || This is an attribute of the ''Resource''. This flag declare that a resource is linked to a ''Client''<br />
|-<br />
| "Customer" || This is an attribute link the ''Resource'' to the client he/she belongs to.<br />
|-<br />
| "Organization Unit" || This is an attribute link the ''Resource'' to the Organization Unit (OU) of Client he/she belongs too.<br />
|-<br />
| "Login" || This is an attribute link the ''Resource''. Login is a link towards the User Management information.<br />
|-<br />
| "Can declare holiday" || If flagged enable the resource to manage his Holiday. Holiday is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Pers.View Right" || If flagged enable the resource to manage ''[[Views_management#Personal_Data_views|Personal views]]''<br />
|-<br />
| "Client Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Company/Client Types''</b>.<br />
|-<br />
| "VIP Type" || This is an attribute of the ''Resource''. The master data for this field are present in <b>''/General/Resources/VIP Types''</b>.<br />
|-<br />
| "Can declare illness" || If flagged enable the resource to manage his Illness. Illness is managed directly in <b>''/Personal/Resource calendar''</b>.<br />
|-<br />
| "Can switch Accessible Mode" || This is an attribute of the ''Resource''. If flagged enable the resource to access the system in Accessible Mode.<br />
|-<br />
| "Can open ticket by resource selection" || This is an attribute of the ''Resource''. If flagged enable the ''resource'' to call "Add Request by Resource". This is a special way to call ''[[ Glossary | SRCS]]'' session. The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| No (Default) || ''[[ Glossary | SRCS]]'' special form is not active for this ''Resource''<br />
|-<br />
| Simple || ''Resource'' can open "Add Request by Resource” but the edit resource information option isn't available<br />
|-<br />
| Full Options || ''Resource'' can open "Add Request by Resource" and the edit resource information option is available<br />
|}<br />
|-<br />
| "Resource search Capability" || This is an attribute depends of "Can open ticket by resource selection". The value available are:<br />
{| class="wikitable"<br />
! Field!! Description<br />
|-<br />
| "All Resources" || Default value, the "Add Request by Resource" function shown all the active Resources <br />
|-<br />
| "Only Resources of OU he/she belongs to" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present in the same Resource OU.<br />
|-<br />
| "Only Resources of OUs where Resource is OU Manager" || If flagged enable the ''resource'' to select in the "Add Request by Resource" function only the resources present all the OUs where he/she is the OU Manager.<br />
|}<br />
|-<br />
| "Can Edit Own Resource Data" || If flagged enable the ''resource'' to update the <b>''/Personal/Profile''</b> information.<br />
|-<br />
| "CMS Access" || If flagged enable the ''resource'' login to itmSUITE® CMS Module <br />
|-<br />
| "User Mapping mode" || itmSUITE® CMS is core module that can be called from itmSUITE® PM or itmSUITE® SM or via specific portal. When called from PM/SM we should specify how the connect resource can be seen in CMS.<br />
The available options are:<br />
{| class="wikitable"<br />
! Access Option!! Description<br />
|-<br />
| System || The current resource will be granted with system right on itmSUITE® CMS, so he/she will have the Administrator privileges. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| CMS local || The current resource should have a login on itmSUITE® CMS. PM /SM login should match with the CMS login. (see [[ASM - Asset and Service Management]]) <br />
|-<br />
| Suite || The current resource login will be used on CMS. The right on CMS will be inherit via Groups Privileges. (see [[ASM - Asset and Service Management]]) <br />
|}<br />
<br />
|}<br />
<br />
For each ''resource'' is possible to set different Address. For example, "Headquarters", "Order" addresses. The session enables the user to <b>Add</b>, <b>Delete</b> or <b>Print</b> the list of address.<br />
<br />
The list of fields is shown in the table below:<br />
<br />
{| class="wikitable"<br />
! Address tab fields!! Description<br />
|-<br />
| "Address" || Used to set Street information<br />
|-<br />
| "City" || Used to indicate the supplier's city<br />
|-<br />
| "Postal code" || Used to indicate the supplier's postal code<br />
|-<br />
| "District" || Used to indicate the supplier's province<br />
|-<br />
| "Region" || Used to indicate the supplier's region<br />
|-<br />
| "Phone" || Used to indicate the supplier's phone number. This should be specific by supplier address type, "Headquarters", "Order"<br />
|-<br />
| "Mobile" || Used to indicate the supplier's Mobile phone number. <br />
|-<br />
| "Fax" || Used to indicate the supplier's fax number. <br />
|-<br />
| "Email" || Used to indicate the supplier's Email information. <br />
|-<br />
| "Type" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Address Types''</b>.<br />
|-<br />
| "Notes" || Used to indicate general notes. <br />
|-<br />
| "Country" || This is an attribute of the ''supplier''. The master data for this field are present in <b>''/General/Company/Countries''</b>.<br />
|-<br />
| "Use for Ticket Info" || if flagged this address will be used to populate the <u>''Ticket User Info Tab''</u>. information<br />
|-<br />
| "Default" || if flagged this address will be proposed as default address.<br />
|}<br />
<br />
<br />
<br />
<br />
== Group Management process == <br />
<br />
{| class="wikitable"<br />
! Group Management !! Description<br />
|-<br />
| Group Definition || See Above<br />
|-<br />
| Add Group || See Above<br />
|-<br />
| Add Resource to Group || See above on Resource Chapter<br />
|-<br />
| Add Group to Workflow || ''[[ vvv |Workfow mangement]]''<br />
|-<br />
| Enable a Group on Service Catalogue Request (SRCS) || ''[[ vvv |SRCS Management]]''<br />
|-<br />
| Profile a Timesheet declaration || ''[[ Timesheet Management |Timesheet Management]]''<br />
<br />
|}<br />
<br />
== How to ==<br />
Set on Resource:<br />
<br />
{| class="wikitable"<br />
! Resource Configuration!! Link!! Description<br />
|-<br />
| VIP Type || <b>General/ Resources/VIP Type</b> || This function defines the data source to set the VIP type in Resource master data <br />
|-<br />
| Purchase Roles || <b>General/ Resources/Purchase Roles</b> || This function defines the data source used to set the default value for purchase role in the Resource master data.<br />
|-<br />
| Sale Roles || <b>General/ Resources/Sale Roles</b> || This function defines the data source used to set the default value for sale role in the Resource master data.<br />
<br />
|}</div>Francesco.bertuletti