Ability to use script tags

[Director-Fusion]

Without being able to run JS via script tags the chartjs feature is severely limited in functionality. Being able to have the ability to allow the use of script tags (optional on/off) OR if worried about security with the product allow the import of server-side scripting to import a more robust chart that can iterate through the arrays. I'd rather be limited by imagination and skill set than by the tool.

[aronmolnar]

Hi,
Can you explain your exact use case?

Can you prepare variables in JS and use them in your charts?

[Director-Fusion]

I am building a scatter chart. I am just wanting to iterate through the cvss scores to place in a chart to generate a visual for clients. The chart is done, aside from the iteration issue. I can iterate with the v-for. But that creates a chart for each finding cvss score. I want the cvss scores all on one scatter chart. I guess how would I go about using the datalabels to get finding.title as the label and x,y finding.cvss.score with this lodash feature you mentioned? I gave it a go and it gives and error when doing the function JS placeholder like lodash.forEach(findings, function(finding).

The current chart is using the v-for iterator in the div tag. How can i get all the cvss scores in one chart instead of one per finding with the lodash utilities mentioned earlier? Thanks for your help with it. This is a very cool tool and just trying to make my reports stand out.

[aronmolnar]

What are your axes?
CVSS and what else?

[Director-Fusion]

Apologies, CVSS was just an arbitrary bit to explain how i need to iterate through the findings portion of the JSON data. We are using custom fields added to the report. X- Damage, Y - Exploitability(how difficult to exploit). When iterated it will be "finding.damage" or "finding.exploitability" respectively. Just a integer. Exactly as you see in the graph. Apologies for the screenshot, I didn't realize that the axes were cut off from the screenshot of the graph. We are using a gradient via CSS to act as a sort of heat map for the findings. To give the client the idea of what may be more pressing not just so much this could be bad.

[Director-Fusion]

SOOOOO. I figured it out using the JS map func.

data: findings.map((finding) => ({ label: finding.title, x: finding.damage, y: finding.exploitability })),

My issue was stemming from the data field having square brackets in there. Once I got the syntax for lodash and now just the JS map down, i played around with it and removed the square brackets. This populated the data on one chart as desired. Apologies for my lack of understanding of the product before raising the question. Thanks for being helpful none the less. Greatly appreciated.

Data is not from a client just arbitrary ints put in for report designing. Don't take the values to heart.

[aronmolnar]

Great - very good to hear. Congratulations.
No problem.

[aronmolnar]

This feature is now implemented.