Documentation

User Tools

Site Tools

Trace:
extensions:teemip-request-mgmt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
extensions:teemip-request-mgmt [2025/07/02 16:28] – [IP Portal] cnaudextensions:teemip-request-mgmt [2025/07/16 09:21] (current) – [Revision History] cnaud
Line 23: Line 23:
 php-max             : 8.3 php-max             : 8.3
 ---- ----
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
  
 TeemIp's IP Request Management extension allows you to manage user requests that are specific to IP management: IP and subnet creations, modifications or deletions. It includes a user portal where standard users can create and manage their IP requests. TeemIp's IP Request Management extension allows you to manage user requests that are specific to IP management: IP and subnet creations, modifications or deletions. It includes a user portal where standard users can create and manage their IP requests.
Line 41: Line 31:
 ===== Revision History ===== ===== Revision History =====
 ^  Version  ^  Release Date  ^  Status  ^  iTop \\ Min  ^  IPAM for iTop \\ Min  ^  Comments  ^ ^  Version  ^  Release Date  ^  Status  ^  iTop \\ Min  ^  IPAM for iTop \\ Min  ^  Comments  ^
-|  **3.2.0**  |  2025-07-02  |  Supported  |  3.2.0  |  3.2.0  | - Implement iTop Portal new look \\ - Replace legacy CRUD methods by new CRUD events  |+|  **3.2.0**  |  2025-07-02  |  Supported  |  3.2.0  |  3.2.0  | - Add Brazilian translation \\ - Implement iTop Portal new look \\ - Replace legacy CRUD methods by new CRUD events  |
 |  3.1.2  |  2024-08-14  |  Supported  |  3.0.0  |  3.1.0  | - TeemIp / iTop 3.2 and PHP 8.3 compatible version | |  3.1.2  |  2024-08-14  |  Supported  |  3.0.0  |  3.1.0  | - TeemIp / iTop 3.2 and PHP 8.3 compatible version |
 |  3.1.1  |  2023-12-11  |  Obsolete  |  3.0.0  |  3.1.0  | - Add Chinese (simplified) translation | |  3.1.1  |  2023-12-11  |  Obsolete  |  3.0.0  |  3.1.0  | - Add Chinese (simplified) translation |
Line 66: Line 56:
 At any time of the life of the ticket, the support agent can communicate with the customer via a “Public log.” He can also communicate with teams internal to his company through a “Private log”. At any time of the life of the ticket, the support agent can communicate with the customer via a “Public log.” He can also communicate with teams internal to his company through a “Private log”.
  
-TeemIp IP Request Management includes a dedicated portal that is described [[2_x:portal:start|here]].+TeemIp IP Request Management includes a dedicated portal that is described [[2_x:portal|here]].
  
 ===== Licensing ===== ===== Licensing =====
Line 101: Line 91:
 Once installed, the module will add a menu group called IP Helpdesk where IP requests will be managed from. Once installed, the module will add a menu group called IP Helpdesk where IP requests will be managed from.
  
-{{ details_menu_iphelpdesk3x.png }}+{{ details_menu_iphelpdesk3x.png?nolink }}
  
 The overview dashboard allows agents and managers to monitor the helpdesk activity. It displays a set of 6 dashlets: The overview dashboard allows agents and managers to monitor the helpdesk activity. It displays a set of 6 dashlets:
Line 111: Line 101:
   * The number of Open IP requests, grouped by organization.   * The number of Open IP requests, grouped by organization.
  
-{{ dashboard_iprequests.PNG }}+{{ dashboard_iprequests.PNG?nolink }}
  
 ===== IP Request ===== ===== IP Request =====
  
-{{iprequest.png  }}+{{iprequest.png?nolink  }}
  
 IP requests in TeemIp are focusing on IP management. A catalogue of 6 types of IP requests have been defined, each of them focusing on a specific request: IP requests in TeemIp are focusing on IP management. A catalogue of 6 types of IP requests have been defined, each of them focusing on a specific request:
Line 152: Line 142:
 == Specific information for IP address V4 creation == == Specific information for IP address V4 creation ==
  
-{{icons8-rj45-48.png  }}+{{icons8-rj45-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 171: Line 161:
 == Specific information for IP address V6 creation == == Specific information for IP address V6 creation ==
  
-{{icons8-rj45v6-48.png  }}+{{icons8-rj45v6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 190: Line 180:
 == Specific information for IP update == == Specific information for IP update ==
  
-{{icons8-rj45-48.png  }} +{{icons8-rj45-48.png?nolink }} 
-{{icons8-rj45v6-48.png  }}+{{icons8-rj45v6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 203: Line 193:
 == Specific information for IP release == == Specific information for IP release ==
  
-{{icons8-rj45-48.png  }} +{{icons8-rj45-48.png?nolink }} 
-{{icons8-rj45v6-48.png  }}+{{icons8-rj45v6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 212: Line 202:
 == Specific information for Subnet V4 creation == == Specific information for Subnet V4 creation ==
  
-{{icons8-subnet-48.png  }}+{{icons8-subnet-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 225: Line 215:
 == Specific information for Subnet V6 creation == == Specific information for Subnet V6 creation ==
  
-{{icons8-subnetv6-48.png  }}+{{icons8-subnetv6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 238: Line 228:
 == Specific information for Subnet update == == Specific information for Subnet update ==
  
-{{icons8-subnet-48.png  }} +{{icons8-subnet-48.png?nolink }} 
-{{icons8-subnetv6-48.png  }}+{{icons8-subnetv6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 252: Line 242:
 == Specific information for Subnet release == == Specific information for Subnet release ==
  
-{{icons8-subnet-48.png  }} +{{icons8-subnet-48.png?nolink }} 
-{{icons8-subnetv6-48.png  }}+{{icons8-subnetv6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 272: Line 262:
 From the Helpdesk menu, click on the “New IP Request” link. User is then asked to select amongst the 6 types of requests: From the Helpdesk menu, click on the “New IP Request” link. User is then asked to select amongst the 6 types of requests:
  
-{{ classcreate_iprequest13x.png }}+{{ classcreate_iprequest13x.png?nolink }}
  
 Once selection is done, the creation form is displayed (IPv4 subnet creation, in the example below). Once selection is done, the creation form is displayed (IPv4 subnet creation, in the example below).
  
-{{ classcreate_iprequest23x.png }}+{{ classcreate_iprequest23x.png?nolink }}
  
  
Line 285: Line 275:
  
 The **private log** is the preferred way for keeping track of the investigations or operations: copy/paste of command line results, summary of communications with a provider, etc. The **private log** is the preferred way for keeping track of the investigations or operations: copy/paste of command line results, summary of communications with a provider, etc.
- +  
-{{public-privatelog_iprequest3x.png}}+{{ public-privatelog_iprequest3x.png?nolink }}
  
 Each entry in the public or private log is tracked with the name of the user who updated it and when it was done. It cannot be modified nor deleted. Each entry in the public or private log is tracked with the name of the user who updated it and when it was done. It cannot be modified nor deleted.
Line 296: Line 286:
 Once an IP request is created, it needs to be assigned to a team and agent before being further processed. For that to happen, select the Assign action in the list of menus available from the details page. Once an IP request is created, it needs to be assigned to a team and agent before being further processed. For that to happen, select the Assign action in the list of menus available from the details page.
  
-{{ details-popup-menu-iprequestotheractions3x.png }}+{{ details-popup-menu-iprequestotheractions3x.png?nolink }}
  
 Then select the Support team you want to assign the ticket to, as well as the agent from this team. Then select the Support team you want to assign the ticket to, as well as the agent from this team.
  
-{{ classassign_iprequest3x.png }}+{{ classassign_iprequest3x.png?nolink }}
  
 <note> <note>
Line 316: Line 306:
 </note> </note>
  
-{{ classprocess_iprequestipcreation13x.png }} +{{ classprocess_iprequestipcreation13x.png?nolink }} 
-{{ classprocess_iprequestipcreation23x.png }}+{{ classprocess_iprequestipcreation23x.png?nolink }}
  
 <note> <note>
Line 343: Line 333:
 </note> </note>
  
-{{ classprocess_iprequestsubnetcreation.png }}+{{ classprocess_iprequestsubnetcreation.png?nolink }}
  
 Once the subnet is selected, pressing the "Process" button will create the subnet in the data base with the attributes set in the request. At the same time, the ticket is put in the Resolved state. Once the subnet is selected, pressing the "Process" button will create the subnet in the data base with the attributes set in the request. At the same time, the ticket is put in the Resolved state.
Line 371: Line 361:
 For creation requests, the subnet or the subnet block, where the IP or subnet are supposed to be picked from, need to be eligible for automatic creation. This behaviour is driven buy a parameter named "**Allow automatic subnet creation**" / "**Allow automatic IP creation**" added to the subnet blocks and subnets. Default is "yes". For creation requests, the subnet or the subnet block, where the IP or subnet are supposed to be picked from, need to be eligible for automatic creation. This behaviour is driven buy a parameter named "**Allow automatic subnet creation**" / "**Allow automatic IP creation**" added to the subnet blocks and subnets. Default is "yes".
  
-{{ classdetails_ipv4subnet3x.png }}+{{ classdetails_ipv4subnet3x.png?nolink }}
  
-{{ classdetails_ipv6block3x.png }}+{{ classdetails_ipv6block3x.png?nolink }}
 ===== IP Request Life Cycle ===== ===== IP Request Life Cycle =====
 All IP requests share the same life cycle. This one is pretty simple and can be summarized as follows: All IP requests share the same life cycle. This one is pretty simple and can be summarized as follows:
  
-{{ lifecycle_iprequest3x.png }}+{{ lifecycle_iprequest3x.png?nolink }}
  
  
extensions/teemip-request-mgmt.1751466511.txt.gz · Last modified: by cnaud

Page Tools