[Andrew Veggian]

I have used JavaScript for making dashboards more dynamic, but I don’t know of a way to automate the creation of hyperlinks. I do have an idea that might work, but it depends on how your files are named. Are the files always named the same thing (Drawings.pdf, Specifications.pdf, etc.) or are they project-specific (ProjectName_Drawings.pdf, ProjectName_Specifications.pdf, etc.) or do they have random names every time?

[Doug McLean]

Yes, most of them are the same.

They will go to a specific sub folder within our Estimate folder.

Everything is consistent. Everything is all contained within the same parent folder.

[David Cutler]

Looking back through some older threads and saw this one @Doug McLean (have to study history so I know where to get my hyperlinks from for @Vince ). Did you find a way to simplify this process? If not, perhaps some of those who have joined the Brainery since your original post might have some ideas.😎

[Vince French]

😅

[Doug McLean]

@lizlarsen is mulling this over as I understand it

[Liz Larsen]

I’m still working on it. My optimism fades, though.

Any method I think of, there are security reasons for disabling JavaScripts ability to do it. Such as JavaScript being able to open folder leads to the possibility of inserting malicious code onto your computer.

Like, I get it. But at the same time I’m frustrated because I have it planned out in my head and it would be possible if not for security reasons. Ugh.

[Troy DeGroot]

@Doug McLean What are you trying to automate? I’ve seen lots of digital dashboard strategies, here is what I’ve always done:

1. Create a template project folder structure, Saved on your network.
2. Save the Template Dashboard in the root directory of that project.
3. Create all the links, and make sure all your links are set to Relative.
4. When a new project comes in, make a duplicate where you save your project data, whether that’s a network location or Studio Project. All the paths should remain if you move the entire thing together.

I saw a video a year ago using javascript to turn layers on/off on a dashboard. I didn’t really understand why they took that approach. It’s a lot easier to create several pages that look different, than to script hiding things on one page.

I’d love to hear what ideas you guys picked up from @mechave presentation. Digital Dashboards are one of my favorite things to do in Bluebeam.

[Liz Larsen]

Coincidentally, my newest video (debuting tomorrow!) goes over a dashboard that uses JavaScript to hide and show layers.

And you’ll see exactly why JavaScript was used here, rather than creating a bunch of similar pages.

(P.S. if anyone needs help adding JavaScript to their dashboards, come see me)

[Troy DeGroot]

You might convince me @lizlarsen we’ll see. 🤣

[Liz Larsen]

[Doug McLean]

the folder structure is set, that’s not the issue, its the location of that folder structure within our Jobs/ Estimating Drive.
Every project has a different starting location, which is the main problem really, even being on SharePoint.
It would just be nice to not have to set up those initial links.

[Troy DeGroot]

I’m really pulling at straws here, but if you go to the Hyperlink Panel you could Edit Action and paste the Root folder into the front of the path…. For each one… I know….

Maybe there could be a script for that @lizlarsen

[Liz Larsen]

This is exactly one of the things I’m looking at.

With writing JavaScript in Bluebeam, there’s the eternal questions of:

• Does my code not work because I wrote it wrong?
• or
• Does my code not work because it’s not possible?

With such limited documentation available for what I’m doing, I have no idea if I should continue down some pathways in an attempt to fix my code, or if that will be a fruitless endevour.

[David Cutler]

Perhaps the question needs to be “what do I need to break to make this work?” @lizlarsen 😎