Hoppa till huvudinnehållet

Close workflow results in data region

Permanently deleted user
I want to be able to close the workflow results (shown in the data region) once I rerun the same workflow (on initialize of this workflow).  I don't know the ID of my workflow results panel, and assume that I use something like the  "DeactiveView" external command to not show this view anymore.  Am I on the right track?  If so, how do I determine the ID of the workflow results?

 

Thanks!
0

Kommentarer

4 kommentarer

Datum Röster
  • John Nerge
    Here are the two commands to run to close the results list and clear the pushpins from your map. You would just need to put this at the beginning of your workflow. So that it would close past results any time it was rerun.

     

    User-added image
    0
  • Permanently deleted user
    Thanks John!

     

    That did it.  New BIG question: How was I supposed to know that the correct "ID" for the Results View is "ResultsListView."  This seems like too deep a mystery.  Is there any documentation on what the various views are called?
    0
  • John Nerge
    There's documentation on the views in the GVH admin guide, but unless you know what you're looking for it's not always easy to find.

     

    When I'm looking for something to change in the viewer, I usually open the viewer config (e.g. desktop.json.js) and search for a term. In this case, I would search for "results", and one of the things that came up was ResultsListView.

     

    No magic trick, just trial and error, experience working with the viewer config files, and always remembering to make sure I can hit Undo to any changes I make.
    0
  • Permanently deleted user
    It can also be helpful to open the browser's developer tools (F12) and switch to the Elements tab (also called DOM Explorer or Inspector tab, depending on your browser). In the top left corner is a element-selection tool that will allow you to identify what various regions of the viewer are called and where they live in the document. It's especially helpful for playing around with CSS, but it's also handy for determining things like the names of specific components. As with the admin guide, it sometimes helps to know what you're looking for, but the dev tools are the easiest way to see what's going on behind the curtain.

     

    I'll ask the team to review the documentation.
    0

Du måste logga in om du vill lämna en kommentar.

Hittade du inte vad du sökte?

Nytt inlägg