Vincent @ Combodo

$this->url()$ The url to access the current object in iTop console

Hi Raphaël, The widget used to search for an external Key, only searches through the friendlyname of the object. That one can be configured to include the organization code, in which case if the user enters an organization code the corresponding organization would be retrieved. That widget can also display other information, such as the code and the country of an organization, but those additional fields aren't used to search for organizations matching what the user has typed in the widget. Maybe...

Hi, This is a well known datamodel issue, the ServiceSubcategory class do not have any field named "org_id", as a result, no limitation on what is visible to users. With an iTop extension, you can rename the "service_org_id" field into "org_id" which is an iTop reserved name for access rights restriction based on the User's "Allowed Organizations" <class id="ServiceSubcategory" _delta="must_exist"> <fields> <field id="org_id" xsi:type="AttributeExternalField" _rename_from="service_org_id"/> </fields>...

User Interface Sub-Categories of Service, too many displayed

Hi, This is a well known datamodel issue, the ServiceSubcategory class do not have any field named "org_id", as a result, no limitation on what is visible to users. With an iTop extension, you can rename the "service_org_id" field into "org_id" which is a iTop reserved name for access rights restriction based on the User's "Allowed Organizations" <class id="ServiceSubcategory" _delta="must_exist"> <fields> <field id="org_id" xsi:type="AttributeExternalField" _rename_from="service_org_id"/> </fields>...

No it is not possible, but you can configure the "From (label)" and the "Reply to (email)" email address on the various Email Notifications, so it looks like coming from 2 different sources and for sure the replies will go to 2 different addresses

This might be achieved with this Combodo customer restricted extension Also it only allow read access, it won't let your A2 guys modify Google assets. Another strategy is to use the field "org_id" to modelize the Silo (because this is the way iTop is designed) and create another field "owner_org_id" on Functional CI to represent a different organization notion, which would not be used to control access rights.

Hi Arnaud, You might get more replies, if you were using english in this forum. Your filter is totally wrong because as soon as the Ticket has moved one day to the priority three, the filter will always matches. The filter to apply on a TriggerOnUpdate ( Déclencheur sur la modification d'un objet ) is much simpler, just do: SELECT Incident WHERE priority='3' The filter is applied in database after the object has been modified. And choose "priority" in the fields ( Attributs cibles ) so you are sure...