[Isaac Harned]

I am curious Doug, on PDF usage on sharepoint in relation to storage. You have some massive PDF’s, does your storage balloon with the versioning?

[Isaac Harned]

Played with this a little more, sorry, haven’t messed with stamps before, it should use an event callout that way it knows which file it’s looking at. Here is an example of the basic submittal approval stamp that’s built in to Revu, but modified to pull that File name. Check out the “getProjectNoFromDocName();” callout and function at the end. Let me know if this works, and if more issues, we may have to see the specific stamp file to help.

var builder =

{

// These map to Text Fields in the Stamp

textBoxes :

[

{ field: “Other – Description”, description: “Other – Description:”, default: function() { return “”; } },

{ field: “CheckedBy”, description: “Checked by:”, default: function() { return Collab.user; } },

{ field: “Date”, description: “Date:”, default: function()

{

var curDate = new Date();

return (curDate.getMonth() + 1) + “/” + curDate.getDate() + “/” + curDate.getFullYear();

}

},

{ field: “Submittal”, description: “Submittal #:”, default: function() { return event.source.source.documentFileName; } },

{ field: “Project”, description: “Project:”, default: function() { return getProjectNoFromDocName(); } }

],

// This maps to a Radio Group in the PDF named ‘Type of Submittal’

radioGroup : “Document Type”,

radioButtons :

[

// value maps to the ‘Choice’ of each radio button in the group, description will show on the dialog

{ value: “SubmittalForApproval”, description: “Submittal For Approval” },

{ value: “Resubmittal”, description: “Re-Submittal For Approval” }

],

checkBoxes :

[

{ field: “Approved” },

{ field: “Rejected” },

{ field: “Revise” },

{ field: “Not Reviewed” },

{ field: “Other” }

]

};

function getProjectNoFromDocName() {

var docName = event.source.source.documentFileName; // Access the document name correctly

return docName.slice(0, 4); // Grab the first four characters

}

[Isaac Harned]

var name = this.documentFileName;

this.getField(“fieldname“).value = name;

Alternatively if it needs to be split into multiple outputs it might look something like:

var name = this.documentFileName;

var parts = name.replace(“.pdf”, “”).split(“_”);

var projectNum = parts[0];

var projectName = parts[1];

this.getField(“ProjectNo”).value = projectNum;

this.getField(“ProjName”).value = projectName;

This of course is if you are using the same identifier to split the Number and name in the doc title, i.e. “_” in this case

Hopefully this helps, let me know if you have anything else!

[Isaac Harned]

Why not File Name?

I know this takes setting up bookmarks ahead of time, which are hardly ever correct downstream, but you could simplify the bookmarks and have Bluebeam Split the Doc by Top level, with naming dependent on the Bookmark. Obviously this would probably take more individual files, but using callouts for this kind of info (Noticed it with RFI’s too) is definitely becoming a thing.

[Isaac Harned]

I would maybe start with the original profile as a base and import the other items you need, export as the new. Depending on how many toolbars you have it could save you a bit.

[Isaac Harned]

What kind of header and footer, something with just standard text, or graphics?

I am trying to think of a way the normal automation scripts can handle this, but unfortunately the page referencing for the script arguments only allows a specific range (and if you don’t have that many sheets it will throw an error) or all pages. It also doesn’t have a “Clear Previous” Argument in the Script. The best solution maybe to have preset headers and footers, can save them now in the dialogue.

[Isaac Harned]

Is there a reason you can’t flatten them and run Batch hyperlink? It should not flatten permanently, so you should be able to unflatten afterwards.

[Isaac Harned]

I don’t have to make any consistent adjustments to get it working, but I don’t use it a whole bunch.

[Isaac Harned]

Possible that running though the stapler and printing as a Revu PDF would fix this. This will permanently flatten markups though so just a quick export before trying.

Stapler-Setttings.png 50 KB Image File - Click to view

Options

• Copy Download Link

[Isaac Harned]

Man I thought of this one today and it is the bane of my existence when processing print revisions. STOP MOVING YOUR NOTES lol

[Isaac Harned]

No worries, I’m glad it worked out! Not to make myself look like a loser but a lot of my answers come from GPT 🤣 If you guys ever struggle with this, just ask it questions based on “Adobe PDF JavaScript”. There are a few methods that don’t work in Revu, but with a little troubleshooting and back and forth with the bot, but that usually gets me pretty close to what I need.

[Isaac Harned]

I would agree here, plenty you can do with a CSV file, but without the getAnnots method, your scripts will never even see the markups.

[Isaac Harned]

The script route would only work if they fixed the arguments for it so that it can reference specific pages. I think the defaults might be your only option, and it would be a two step manual process.

[Isaac Harned]

I don’t know if it’s exactly what you need, but you can save defaults in the Header and Footer preferences. If I was making the workflow for myself, I might make one that I apply to Page 1, and another that I would apply to the rest of the pages. Again though, if it has graphics, template might be the only way.

Header-Footer-Defaults.png 18 KB Image File - Click to view

Options

• Copy Download Link

[Isaac Harned]

I think these are toolchests instead of toolbars