The fix did the trick.
Thank you very much!

Hi Reinhard,

that's not possible at the moment. You can create your own custom categories at "Administration / CMDB Settings / Custom categories"

Hi Reinhard,

Can you please explain your problem with more details? What exactly is not working?

Kind Regards,
Christian Reiß

Sorry for late answer.
Your query helped a lot. Thanks.
Jan

This issue is going to be resolved in the next i-doit pro version 1.8.1. It will be released within the next weeks.

Hi JP,

Thanks for your request. There is an easy way to connect one input with two or more outputs: Just create one input (with no connected output) and then two outputs connected to the input. You will get a similar result as in the online demo for i-doit pro.

The other way (two inputs connected to one output) is currently not possible with i-doit pro. Can you give us a simple drawing which scenario in real life you would like to document? Maybe there is a workaround.

Greetings
Ben

Hi,

I know this topic is old, but maybe it helps someone in the future.

You have to open the logbook entry itself by clicking on it and then there is a button "Show details". I added some screenshots.

Kind Regards,

new_lb_entry.png
show_new_entry.png
details_in_entry.png

Hi,

This is in fact a known issue and was already reported to our developers.

Kind Regards,

Hi,

Please try upgrading i-doit to the newest version. Maybe there was a bug in i-doit 1.6.X.

Kind Regards,

I figured it out.  Our i-doit instance is set to require authentication from JSON-RPC calls, which are not included in the JS files in the module.  I unchecked this option and it works.  As this is a test environment this is fine for now, but I may need to hard-code authentication at a later date when we move into production.

Hi,

What I wanted you to see there, is the installation process. There is a different one for SUSE (11 and 12): https://i-doit.atlassian.net/wiki/pages/viewpage.action?pageId=10223840

As you can see, SLES 11 is described in the bottom of the article but it is not supported anymore.

I remember SELinux to prevent a local connection between the webserver and the database. Perhaps you have to disable that.

Kind Regards,
Christian

For all those, who have this problem, I found out the solution for the V4.1.15-8-default:

1st: keep cool (it took me several coffees to calm down on this silly thing. If the value for timeout is 0, so the setting is off or the value is wrong. Why the heck, wasn't this catched by the program??)

2nd: Login on your webserver, go into the i-doit-folder in the apache-webfiles (f.e. SuSE: /srv/www/htdocs/i-doit/…)
3rd: find the globals.inc.php
4th: open it with your favourite text-editor
5th: find and copy the following line:

$g_config["sess_time"]  = isys_settings::get('session.time', 300);

6th: uncomment one of the original one with two slashes

// $g_config["sess_time"]  = isys_settings::get('session.time', 300);

7th: change the copied line:

FROM

$g_config["sess_time"]  = isys_settings::get('session.time', 300);

TO

$g_config["sess_time"]  = 900;

8th: SAVE the file, but leave it open in your text-editor

9th: Login to i-doit and change the value for Session Timeout in the Settings. 3600 (1 hour) might be a good value. Save the sessings

10th: uncomment in the globals.inc.php

// $g_config["sess_time"]  = isys_settings::get('session.time', 300);

and comment the line

$g_config["sess_time"]  = 900;

That's it.

Hallo jkondek

Das sieht super aus, vielen Dank!

Gruss
Nadine

Unfortunately when I copy the Database from the OCS Server to the local Database on the i-doit installation it works like a charm. But thats not a practicable solution.

Furthermore I can't figure out how to specify the connection OCS-Object<-> i-doit Object in the GUI. Some Information isn't passed at all like the User in OCS.

Hello Thomas,

that's easy, here is a query for all objects with a primary contact:

SELECT
j1.isys_obj__title AS 'object',
j2.isys_obj__title AS 'primary contact'

FROM isys_obj AS j1

LEFT JOIN isys_catg_contact_list
ON isys_catg_contact_list__isys_obj__id = j1.isys_obj__id

LEFT JOIN isys_connection
ON isys_connection__id = isys_catg_contact_list__isys_connection__id

LEFT JOIN isys_obj AS j2
ON j2.isys_obj__id = isys_connection__isys_obj__id

WHERE TRUE
AND isys_catg_contact_list__primary_contact = 1

Maybe you want to add something like this (only all server):
AND j1.isys_obj__isys_obj_type__id = 5

Regards,
jkondek