Vasek

Thank you @jeffrey_bostoen! iTOP upgraded to 3.2.2 :)) GDPR attribute solved.

Hello, I am using iTop version 2.7.12 and I have a trigger on the Incident class for the gdpr attribute (values: yes, no, not_evaluated). The problem is: In 2.7.12, triggers only evaluate objects based on the current state after save, not on the attribute change itself. This means I cannot reliably send an email only when gdpr changes to yes. I would like to know: Does iTop version 3.0+ allow triggers to detect changes in attribute values directly, so that the trigger can fire only when gdpr changes...

Hey, I would like to ask you, if is some option to change attachment storage location. All attachments are saved to the database (table attachment). I would need to change storage location (other server, disc etc.) Thank you for an advice. Old topic: https://sourceforge.net/p/itop/discussion/922361/thread/aa9813b6/ Vasek.

Thank you Vincent. I will think about the new version of itop.

Hey. Hey. I have the same problem as was in the thread here: https://sourceforge.net/p/itop/discussion/customizing-itop/thread/cf6026f8/?limit=25#b0de I have a new class lnkPersonToSoftware where I have an array: <field id="software_id" xsi:type="AttributeExternalKey"> <sql>software_id</sql> <target_class>Software</target_class> <filter><![CDATA[SELECT Software WHERE type = 'othersoftware' AND status = 'production']]></filter> <dependencies> <attribute id="org_id"/> </dependencies> <is_null_allowed>false</is_null_allowed>...

SOLVED: I changed my.cnf. I added: max_allowed_packet=512M.

UPDATE 2: I wanted to do the following: CREATE TABLE priv_event_email_new LIKE priv_event_email; INSERT INTO priv_event_email_new SELECT * FROM priv_event_email; But problem is: mysql_innodb_table_stats: Query opened in 0,010s [0,004s exec, 0,006s fetch] itop_prod_priv_action_notification: Query opened in 0,009s [0,002s exec, 0,007s fetch] SQL9.sql: Error (3,15): Table 'itop.priv_action_email' doesn't exist SQL9.sql: Query opened in 0,012s [0,003s exec, 0,009s fetch] SQL9.sql: Query opened in 0,049s...

UPDATE: I found a ticket that has REF R-xxxxx, but the URL is not UserRequest, but UserRequestApplication. How could this have happened? When I change it to UserRequest, the ticket still works. I deleted this ticket from the database in the ticket_requestapplication table and it remained normally in the ticket_request table. ITOP seems to be working properly now. It's just that the backup is still not working and it's reporting an error about the priv_event_email table. :(