Getting the palette structure from the post-build action variant input (or in any other way)

[SlippinJimmy]

Hello,

The input variant passed to the post-build action VI contains several data, such as Output Package File Path, Package Member Source Files, Product Name, Package Version, etc.
As far as I know, there is no data related to the palette structure. With palette structure I mean the list of palette names and the list of contained VIs and sub-palettes. A kind of hierarchical structure. 
Is there any way to get this kind of data?

To better understand my question, I share what I would like to obtain. In our company, we have an internal VI package that is shared with all the LabVIEW developers in the company. We have moved the VI documentation to Confluence and we've been doing this in an automatic way (using Confluence HTTP API). This operation is done in the post-build action set for the VI package. This way, the Confluence documentation is updated every time we build a new version of the package.
What we are missing is to (automatically) replicate the palette structure on Confluence in order to have a well-organized documentation and to have a match with the palette structure. In other words, if the package is composed as follow:

• Main palette:
  • String palette
    • VI 1
    • VI 2
  • File palette
    • VI 3
    • VI 4
    • VI 5

 

...we would like to build Confluence pages in this way:

• Documentation home page
  • Page of String palette
    • Page with documentation of VI 1
    • Page with documentation of VI 2
  • Page of File palette
    • Page with documentation of VI 3
    • Page with documentation of VI 4
    • Page with documentation of VI 5

 

So, getting back to  my question, is there any way to get the palette structure in the post-build action variant input (or with any other way)? If no, here's a suggestion for a new feature 😎

Edited September 13 by SlippinJimmy
Added tags