Hi, in a "DashletGroupByTable" we are using the "average" aggregation function. We can see values with 4 decimal places, after a refresh we only see the value without decimal places, even not correct rounded. Attached are Screenshots before and after refresh. Maybe a function to define the number of decimals and round options would be great for a future release? Thank, best regards, Nico
Hi, I have the problem that 2 different Expiration rules are fireing the same notification. 1st Expiration-rule (NM_AgentAppointment is a DateTime field): SELECT UserRequest AS ur WHERE NM_AgentAppointment <= DATE_FORMAT(NOW(),'%Y-%m-%d 23:59:59') AND NM_AgentAppointment >= DATE_FORMAT(NOW(),'%Y-%m-%d 00:00:00') AND status NOT IN ('closed','resolved') 2nd Expiration-rule (should notify about long running tickets): SELECT Ticket WHERE finalclass IN ('UserRequest','Incident') AND operational_status...
Hi Guillaume, thanks for the hint. I changed it to <itop_design xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.0"> And now it works. Thanks again, Greetings, Nico
Hi, in my iTop 3.1.1 develeopment environment I am testing setting colours based on custom enum values. I added a new state (status) to class UserRequest and defined a color: <class id="UserRequest" _delta="must_exist"> <fields> <field id="status"> <values> <value id="pending_supplier" _delta="define"> <code>pending_supplier</code> <style> <main_color>#d8e096</main_color> <complementary_color>#d8e096</complementary_color> <decoration_classes>fas fa-hourglass-half</decoration_classes> </style> </value>...
Hi, is there any explanation how to set attribute flags using the new events? I already successfully used "EVENT_DB_AFTER_DELETE" and "EVENT_DB_AFTER_WRITE" but I have no idea how to access attributes and set them for example readonly using this events. Thanks for any hint, regards, Nico
Hi, thanks for that hint. I can understand the purpose of that change. It seems I can use that interfaces for my customizations. Great Tool :-) Cheers, Nico
Hi, in iTop 2.7 I used the interface "OnDisplayProperties" to inject HTML/JS code to the form on a stimulus action. E.g. when a UserRequest is to be resolved I added some comments to that form via Javascript. In iTop 3.1 this interface not called anymore on stimulus actions. Only when an object is displayed I can still use this to inject code using $oPage->add_ready_script(). With the new events API I can only manipulate object on database level as I understand, not how objects are displayed on the...
Like this: public function OnDisplayProperties($oObject, $oPage, $bEditMode = false) { $oFailAlertBlock = AlertUIBlockFactory::MakeForDanger('Test-Title', "Test-content", 1313); $oPage->AddUiBlock($oFailAlertBlock); $oPage->add_ready_script( <<<JS $('#1313').appendTo($('#ibo-page-header')); JS); ...