[Isaac Harned]

So in looking for the answers to one question, I stumbled on a possible solution for this. setAction on a button can be modified by code to “openDoc” instead of “launchURL”. Is this something that would help?

[Isaac Harned]

LOL “Kind Of?”

[Isaac Harned]

Welcome to the party, looking forward to learning some of your workflow!

[Isaac Harned]

We use layers, but in a couple of outlying workflows from the rest of the industry. Much of what we do is marking up an already crowded print, so having the ability to shut some of those off can be very useful.

We also have forms where we activate / deactivate certain charts on the page (using scripted dropdowns) depending on testing requirements, giving the field some flexibility for the annual verifications we go through.

I do wish more mechanical pdfs were distributed with the layers still active. Most of that metadata is usually gone when we get it.

[Isaac Harned]

Good to have you Bruce, looking forward to your insights!

[Isaac Harned]

My work around for now is to print using the Image engine. This keeps my line weights visible, but is a pain to run on each individual. Bluebeam support has forwarded, but that’s the best it gets right now I think.

[Isaac Harned]

Hmmm this one is interesting. Do you know if he is using the print driver, the create PDF, or the stapler way of printing? Which method do you use?

[Isaac Harned]

We use the iPad app in the field now, but only for specific projects involving those new forms we went through. This is only for the use of javascript and layer controls, as well as the PDF check in check out system through projects. Field employees have enjoyed it so far, but only because they are using minimal markups, not storing DRL issues, and more of just entering data into form fields. Cloud for us is nowhere close to where we need it, and most of our field work is done through PlanGrid.

[Isaac Harned]

I think technically you could accomplish it through the A-word, but would be annoying to have to use that every time to update links. Hopefully that API expansion is coming soon and is not a let-down.

[Isaac Harned]

Ok getting more into the weeds of what Liz was referring to with security:

I tried to add a “File//” at the beginning in order to call file explorer if trying to go to a directory. it seems to concat just fine, but gave me a security error when I tried to execute.

It WILL however concatenate to open a specific file, i.e.:

var dataLink = this.getField(“Text1”).value + “M0-22CD Schedules Area CD.pdf”;

app.openDoc(dataLink);

This works and open up right in Revu, BUT it freezes the program for some random reason

Here is the File explorer code if anyone wants to play:

function launcher() {

var dataLink = “file://” + this.getField(“Text1”).value + “/DATA”;

app.launchURL(dataLink);

}

[Isaac Harned]

ok got the base of this working, let me know if I’m on the right track or if you need to do this a different way before I take it any further:

Global code:

function launcher() {

var link = this.getField(“Text1”).value

app.launchURL(link);

}

Button code (mouse up, javascript)

launcher()

If this is the right idea, we can take an input and concat with a set of standard relative locations.

Alternatively, we can use the openDoc method instead of launchURL if we want to open in Revu.

[Isaac Harned]

This is pretty frustrating, it looks like one way to do this would be to place a field on the page to collect the base of the address, then concatenate with a set of standard relative links. Couple of problems I am running into playing with this, and maybe you can expand Liz:

So there is no way that I can see to manipulate active hyperlinks as they are not named form fields, and as noted earlier, Revu has not made a method available to create link.

The work around that I see would be to set the action of buttons or other dashboard items. Unfortunately I am having issues getting the second half of my “setAction” command to work. I am pretty unfamiliar with the usable function calls here, but I have tried a couple, icluding this one, which seemed the most obvious:

(simplified without concatenating for now, just trying to get the base to work)

// Get the value of the form field

var fieldValue = this.getField(“Text1”).value;

// Set the action of the button to follow the hyperlink on MouseUp

this.getField(“Button1”).setAction(“MouseUp”, “this.getDoc().launchURL(\”” + fieldValue + “\”);”);

[Isaac Harned]

I have not, as we would also have to get every revision that way and at this moment, it’s not worth the constant struggle with various document departments.

Hopefully one day it’s just a standard

[Isaac Harned]

Wanted to follow up here on a part of your OP. When you say that editing a .bax is beyond your skill set, have you tried just exporting markups (not a summary), and then just opening the markup file like a PDF? you should be able to edit the markups on basically a blank space before re-importing to your file.

[Isaac Harned]

#4 here is key, you have to develop your power users to the max, get your tech minded people excited about the possibilities. Look at your most repetitive and annoying workflows and get those as automated as your workflow allows. Once the tech minded see the time savings and consistency advantage, they will do most of the work spreading knowledge.

The hardest part will be the veteran adobe users, be patient with them as they try to completely shift the way they work in the program. Things like the markup bar for comments will be hard for them to find. Set up a standard User Profile right away with simple interface only showing the tools they need and distribute.