[Liz Larsen]

Honestly, both questions sound like they warrant an email to Bluebeam tech support.

[Liz Larsen]

@Vince

Are the forms identical?

How many pages long is each form?

(I might be able to do it with JavaScript… No promises, though)

[Liz Larsen]

I have literally never used the typewriter. I guess I don’t have an issue with doing two clicks? Maybe I should give it a try and discover the wonder that is the typewriter tool?

[Liz Larsen]

@David Cutler, I was also thinking that the PDFs would have to be merged before doing any sort of data processing on them.

[Liz Larsen]

I don’t know that this would provide the type of solution he’s looking for. Is there a way to export that markup info without individually opening every single PDF?

[Liz Larsen]

Nice! I did not know this option existed. I don’t work with forms a lot, so I’d love to hear the results once @Vince tests this.

[Liz Larsen]

JavaScript can insert pages from another file. Would you like to do something like that?

[Liz Larsen]

Outside of Sessions, I would agree that it’d be nice to be able to clear a status. But, if you’re not in a session, you could just delete and recreate the markup to effectively clear the status.

[Liz Larsen]

Nope! You can only change the status to some other status.

[Liz Larsen]

A huge limitation to JavaScript within Bluebeam is that it can’t manipulate markups.

It can manipulate form fields, along with other document properties (insert/delete pages, page labels, bookmarks, etc…)

With that limitation in mind, I’m not sure how I would solve this using JavaScript. Sorry 😕

[Liz Larsen]

I had debated on how I wanted to do this particular video.

Did I want to figure it out off camera, then do a much more scripted video on how I fixed it? Or did I want to do it in real-time to show how I troubleshoot and problem-solve?

Obviously I went went with the latter. I figured “show, don’t tell” might work better. And it’ll make people feel better about their own silly mistakes. We all make them. Especially, I think, when writing code.

[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.

[Liz Larsen]

[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)

[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.