Menu
▾
▴
#2066 [iTOP 3.0.1 - Send updates by email] Broken public log update notification
more-info-needed
None
Extension
Medium
3.0.1
defect
2022-09-14
2022-05-10
No
Hello!
I have just updated the iTOP version to 3.0.1 but suddenly all the notification configured to use the public_log parameter stopped working.
I have configured a mail notification when the public_log is updated but both from the administration interface and the customer portal, whenever I update the public log, the notification is not triggered; actually if I try to send an update via the administration interface the "notify" trigger is completly gone.
I have reverted the installation to version 3.0.0 and everything is working again.
However if I update the private log, everything works propertly.
Unfortunally I don't have any log to share because there arent' any.
BR,
Giorgio
@pgoiffon @glajarige
Anyone? :)
Hello,
Can you share trigger and action configuration ?
Do you reproduce this on our online demo ?
Also next time please use the forums first. We prefer to use tickets for qualified bugs only.
Hello Pierre,
sorry for the misunderstood use of the ticket, but this seems to be (on my infrastructure) a confirmed bug.
So, on the online demo seems to be working because the trigger references to the User Request class; in my installation I reference the Ticket class and (for the moment) everything still works (at this point I'm not sure why, since the public logs are specific of the User Request class)....
Giorgio
Ok
We need to reproduce to understand the bug, can you send your configuration, actually every information to reproduce the behavior ?
Hello Pierre,
attached the screenshots of the configuration that in 3.0.0 is working and with 3.0.1 is not.
BR,
Giorgio
As far as I am able to see you are using a Trigger with the target class "Ticket" and the log attribut "public_log". Using the default datamodel the attribut "public_log" does not exist for the class Ticket. It is only defiened within the sub classes "Incident" and "UserRequest"..
I am wondering that your solution seems to work with previous iTop versions..
Looking in the release notes of the 3.0.1 does not seems to be a fix for this "error", so I'm not sure why.
I'll try to change the triggers in my test environment in the next days and I'll get back to you for the upgrade.
BR,
Giorgio
EDIT: the configuration I posted is working in production right now ;)
Last edit: Giorgio Maggiolo 2022-05-19