Soft triggers from plugin

Answered

Comments

8 comments

  • Avatar
    Andrey Terentyev

    Hello David,

    We would like to add a button on the display that allows performing a plugin action, to open a web page.

    Could you give more detail on this, please? What web-page is to be opened?

    What is your pipeline?

    "Soft trigger" rule created -> Button pressed -> "Soft trigger" event -> "Do HTTP request" action

    Is that correct? What is the URL for the "Do HTTP request" action? Where executeAnalyticsAction should be invoked?

    0
    Comment actions Permalink
  • Avatar
    Tagir Gadelshin

    David Brown

    maybe a little context on what Andrey asked.

    We have context actions, that can open a webpage to enroll a face, for example. Those ones can be called by the user. When the tile with the object is right-clicked and the option is selected, Desktop Client calls executeAnalyticsAction call and opens what the call returns.

    It looks like this:

    We also have a webpage, that can be located on the layout, near the cameras. BTW, it has its own JS API to perform actions within the client (open cameras, set time to archive, etc)

    But as I understand, you need a soft trigger to open the webpage the way the context action does, right? In pop-up window?

    Or do you need a webpage to be opened on the layout?

     

     

    In general, full user story will help us better understand how it can be done within our platform (what the webpage shows, what user should do on this webpage and so on)

    0
    Comment actions Permalink
  • Avatar
    David Brown

    Hi Andrey, Tagir,

    Thanks for the replies.

    "Soft trigger" rule created -> Button pressed -> "Soft trigger" event -> "Do HTTP request" action

    Is that correct? What is the URL for the "Do HTTP request" action? Where executeAnalyticsAction should be invoked?

    Unless there is a better way, the "Do HTTP request" action URL is localhost:7001/api/executeAnalyticsAction, with enough dummy parameters to allow the action to occur. The action then returns a URI of our web page to do the enrolment.

    But as I understand, you need a soft trigger to open the webpage the way the context action does, right?

    Exactly.

    We have enrolment via the context menu currently, for the person being right-clicked on. We can, as you suggested, do the same to enrol a person absent from the object list. We would prefer to use some form of button for when the context menu doesn't make sense (e.g. enrolling person B by clicking on the face of person A). Using the HTTP API from the plugin is not super-desirable though.

    0
    Comment actions Permalink
  • Avatar
    Tagir Gadelshin

    David Brown

    We have smth that can be done to perform this scenario. But creating an Event Rule, Shared Layout, and Web Page item will be required. It should be done either via HTTP API or by the system administrator. 4.2 & 5.0 SDK does not have those interfaces available at the moment, unfortunately. We are working on some improvements that will allow this in the next major version.

    The idea is in opening a new layout (tab on the top) with a webpage on it. 

    Steps are:
    1. add a webpage of the Face Recognition system.

    2. Add this webpage on layout and share this layout with all users.

    3. Create Event Rule (Soft Trigger -> Open new layout)

    I'm attaching GIF that represents the idea.
    BTW, this webpage can control the client via JS API (open/close cameras on layout and so on). Let me know if you are interested in this.

    0
    Comment actions Permalink
  • Avatar
    Tagir Gadelshin

    0
    Comment actions Permalink
  • Avatar
    Tagir Gadelshin

    Maybe a soft trigger is not even needed. As the webpage appears in the resource tree on the left and can be opened on the layout. Webpage name can me like "Add person to Face Recognition". 

    Cause from a UX standpoint it feels like opening an integration from the resource tree is more convenient.

    Anyway, both options can be configured. The only drawback is additional steps during integration configuration (but they can be automated or implemented in the plugin via HTTP requests)

    0
    Comment actions Permalink
  • Avatar
    David Brown

    Hi Tagir,

    Thanks for the detailed response. We will use the context menu for the moment. The HTTP API would be the next option.

    It would be nice if the HTTP API could be accessed directly through the plugin SDK, without requiring authentication.

    Regards,

    Doug

    0
    Comment actions Permalink
  • Avatar
    Tagir Gadelshin

    David Brown

    thanks!that's smth we have on our roadmap

    0
    Comment actions Permalink

Please sign in to leave a comment.