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:46] – [Managing Public & Private Log] cnaudextensions:teemip-request-mgmt [2025/07/16 09:21] (current) – [Revision History] cnaud
Line 31: 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 286: 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 ?nolink}}+{{ classassign_iprequest3x.png?nolink }}
  
 <note> <note>
Line 306: Line 306:
 </note> </note>
  
-{{ classprocess_iprequestipcreation13x.png ?nolink}} +{{ classprocess_iprequestipcreation13x.png?nolink }} 
-{{ classprocess_iprequestipcreation23x.png ?nolink}}+{{ classprocess_iprequestipcreation23x.png?nolink }}
  
 <note> <note>
Line 333: Line 333:
 </note> </note>
  
-{{ classprocess_iprequestsubnetcreation.png ?nolink}}+{{ 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 361: 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 ?nolink}}+{{ classdetails_ipv4subnet3x.png?nolink }}
  
-{{ classdetails_ipv6block3x.png ?nolink}}+{{ 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 ?nolink}}+{{ lifecycle_iprequest3x.png?nolink }}
  
  
extensions/teemip-request-mgmt.1751467572.txt.gz · Last modified: by cnaud

Page Tools