In Bluebeam Revu, the Status column in the Markups List can be used to apply statuses to individual markups. Although Revu features several default statuses that can be applied, you can also create custom statuses as well.
With a custom status created, it can then be used on the currently active PDF. However, when you open a new PDF document, by default the custom statuses will be cleared from the status list. This can be frustrating, as many users create statuses that they will be reusing on many different PDFs.
Custom statuses, like most customizations within Revu, can be saved the current profile for reuse. After saving a custom status to a profile, the status can be used over and over again on different PDF documents.
This article will outline how to save a custom status to the profile for reuse. For instructions on how to create and use custom statuses, please refer to this article first.
The following examples are taken from the 64x Bluebeam Revu 20 eXtreme edition, but the functionality can be performed in all versions of Revu.
To save a custom status to your current profile, first create the custom status. With your custom status created, select the Status Column Settings button and select Manage Status.
Select the desired State Model, and select the Save to Profile button.
With the custom status saved to the profile, it will now be available to use on every PDF – as long as you continue using the profile the status was saved to.
If you have any comments, questions or suggestions, please use the comment section on the bottom of this page, and don’t forget to subscribe to our blog to get more Bluebeam tips & tricks directly in your inbox!
Lauren Hecker is a Bluebeam Certified Instructor and teaches Onsite Bluebeam Certified Courses, virtual Bluebeam Basics and Advanced courses, and custom onsite or virtual courses. To see her next open enrollment course, please visit our calendar. To schedule an onsite or custom course, please contact us!
Hello,
I saved a custom model to my profile to use across multiple PDFs. However, I am only able to access the custom model in the instance of Bluebeam that I created it in. If I open another Bluebeam window, it does not show up as a status option. Do you have any thoughts on why I wouldn’t be able to use the model in other PDFs if I saved it to my profile?
Hi Kristyn,
Once you create your custom status model, select the Save to Profile button in the Manage Status window. You will then need to save and export your profile to the other instance of Bluebeam that you need to use. To be clear, if you export/import a profile before making a change, such as saving statuses, those changes won’t be made on the exported version on the profile, so make sure you make the changes you need before exporting the profile.
Let me know if this solves your issue!
Lauren,
I have the same problem and even if I save my profile after, the list of custom status I created and save to profile are not available for othe documents
Hi Avril,
This issue has to do with the fact that the markup list arrangement is saved both to the profile and to the document. So even if you save the custom status to the profile, if the document has another arrangement already saved to it, the document column arrangement will replace the profile arrangement. Unfortunately, for documents where this issue occurs, you may need to recreate the custom status for the document to replace the document’s saved arrangement.
So I seem to be having the same issue as Avril. Even though I’ve saved it to my profile, it isn’t available when I open another pdf or create a new one.
My workaround is to insert the new pdf into the existing one, delete the original sheets, and save it as a new file. Moving forward, I’ll just have a “template” file set up and do this whenever I need to use the specific status.
Hi Luke,
Thank you, that is a good solution. The error here is that unfortunatley markup list settings will save to both the profile and the document – and if settings are saved to the PDF, they may override the profile settings. Hopefully this is something that will be fixed in future iterations of Revu.