Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Parent template name filter for Object Tools

Parent template name filter for Object Tools

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 26.4k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P
    P
    pvo
    wrote on last edited by
    #1

    I am not sure if it is a bug or a featureĀ  ;).

    I use "Parent template name should match the following template (comma separated regular expression list)" filter for some Object Tools. This works correctly if the user has at least Read access right to Templates. If the user does not have this right, the tool will not appear in the Command section of the Node.

    I think think that is not the expected behavior because a normal user does not need to see Templates for his daily work, but he needs to use Object tools.

    Would it be possible to solve this problem and allow using this filter without having the Read access right to Templates?

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      this is a bug that cannot be solved easily. Object tool filtering for displaying in context menu is done on client side. If client application does not have access to templates it cannot check if node is in that template or not. This can be solved by sending filtering request to the server, but that will require round trip to server on each right click on object (possibly combined with some sort of caching and push notifications from server when template membership changes) - this can significantly slow down UI.
      Alternative approach for such filtering could be by using custom attributes - you can use configuration poll hook to set custom attribute for each parent template and then in object tool check for those custom attributes.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • P
        P
        pvo
        wrote on last edited by
        #3

        Hi Victor,

        thank you for the confirmation that it is an error and for the workaround.

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better šŸ’—

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups