Sunilkumar

Hello everyone, We are currently working on creating a custom extension for iTop using a low-code tool. Due to organisational policies, we are not able to use the extension that is already available. I have encountered two key tables during this process public_log and public_log_index. I would like to better understand the relationship between these two tables, especially when it comes to their intended purpose and how they interact during logging and indexing. Could anyone clarify on below points....

Hello Team, I am experiencing an issue where only 5 out of 10 systems are successfully reporting to iTop from OCS NG. Below are the details of my setup and the problem I am encountering: Setup Details: OCS NG Server Version: 2.11.1 OCS NG Agent Version: 2.10.0 iTop Version: 3.1.1 iTop Extensions in Use: Data Collector for OCS Inventory NG (Version: 2.0.0) Data model for OCS Inventory (Version: 2.0.0) Scenario: I have installed OCS NG agents on 10 systems. All 10 systems are successfully sending data...

Hello team, I have developed new ticket states and transitions for UserRequest via an extension, It is working as expected except for SLA (TTO & TTR). Since my custom statuses are inherited from Assigned and Pending statuses, I expected that it will inherit the stopwatches also based on that which didnt happen. I'm also using "SLA considering business hours" extension by Combodo. Could you please advise how I can incorporate my new statuses to the considered in include/exclude as appropriate keeping...

Hello team, I have developed new ticket states and transitions for UserRequest via an extension, It is working as expected except for SLA (TTO & TTR). Since my custom statuses are inherited from Assigned and Pending statuses, I expected that it will inherit the stopwatches also based on that which didnt happen. I'm also using "SLA considering business hours" extension by Combodo. Could you please advise how I can incorporate my new statuses to the considered in include/exclude as appropriate keeping...

Hello team, I have developed new ticket states and transitions for UserRequest via an extension, It is working as expected except for SLA (TTO & TTR). Since my custom statuses are inherited from Assigned and Pending statuses, I expected that it will inherit the stopwatches also based on that which didnt happen. I'm also using "SLA considering business hours" extension by Combodo. Could you please advise how I can incorporate my new statuses to the considered in include/exclude as appropriate keeping...

Hello team, I have developed new ticket states and transitions for UserRequest via an extension, It is working as expected except for SLA (TTO & TTR). Since my custom statuses are inherited from Assigned and Pending statuses, I expected that it will inherit the stopwatches also based on that which didnt happen. I'm also using "SLA considering business hours" extension by Combodo. Could you please advise how I can incorporate my new statuses to the considered in include/exclude as appropriate keeping...

Hello team, I have developed new ticket states and transitions for UserRequest via an extension, It is working as expected except for SLA (TTO & TTR). Since my custom statuses are inherited from Assigned and Pending statuses, I expected that it will inherit the stopwatches also based on that which didnt happen. I'm also using "SLA considering business hours" extension by Combodo. Could you please advise how I can incorporate my new statuses to the considered in include/exclude as appropriate keeping...

Hello team, I have developed new ticket states and transitions for UserRequest via an extension, It is working as expected except for SLA (TTO & TTR). Since my custom statuses are inherited from Assigned and Pending statuses, I expected that it will inherit the stopwatches also based on that which didnt happen. I'm also using "SLA considering business hours" extension by Combodo. Could you please advise how I can incorporate my new statuses to the considered in include/exclude as appropriate keeping...