Pro 3.4 & Portal 2.10 Release Notes


We’re excited to announce our latest software update is available now! Pro 3.4 and Portal 2.10 updates include Revit Sheet Support, UI improvements, TLS 1.2 security update, several bug fixes, plus a special announcement of a game changing feature we have in the works! Keep reading for the low down and don’t forget to update your platform to access these features now.


•Revit Sheet Support: 

You will now be able to batch export and store Revit sheets as individual assets in UNIFI.  

Any families, linework, drafting views, and/or schedules placed on the sheets will also be stored and inserted with the sheet.  Revit sheets uploaded to UNIFI will be automatically upgraded to newer versions of Revit and their parameters will be searchable as well. For more information on Revit sheets and how you can put it to good use, check out our blog here.

•UI Improvements – Search Results and Family Types

We’ve made various improvements to the UI for search results.  First, we added the category to all display modes which is the top requested feature on our ideas portal.  We also updated the grid display mode so it’s easier to navigate and made sure the same file information is displayed across all display modes.  On file details, we improved the UI for viewing family types and associated parameters.  Types are now displayed as a filterable list, making it easier to find the type you’re looking for.  You can also view parameters by Revit year, which is especially helpful for files that have been uploaded from multiple Revit years.

•Transition to TLS 1.2 

In order to ensure the continued protection of our your data stored within UNIFI, we are transitioning all communications between our clients and our backend services to utilize TLS 1.2.  TLS 1.2 ensures that the data transmitted to and from our backend is protected from anyone trying to eavesdrop on the transmission by encrypting the contents of those transmissions from our customers to our backend system.  Want to check and  see if your computer supports TLS 1.2 ? Please visit this page.  If the TLS 1.2 section says “Yes” then their system supports TLS 1.2.  If the TLS 1.2 section says “No” then you will need to upgrade their operating system so that it supports TLS 1.2. Please reach out to UNIFI Support if you need assistance.

Coming soon

•Shared Parameter Management

Shared parameters are notoriously difficult to manage.  With this upcoming feature, you will be able to upload all of your company’s shared parameters to UNIFI and manage them in a single location.  All changes will be saved as a new version with the ability to compare historical versions.  You will also see a new button in the UNIFI Revit add-in that notifies you when changes have been made so you can sync the latest shared parameter file to your local machine. 

This upcoming feature was requested by our customers and is an unsolved pain point in the industry!  There is no current solution for companies looking to store and access their shared parameters in a single, managed location.  By managing your shared parameters in UNIFI, you will always know the shared parameters you’re using are the latest and greatest, ensuring consistency across your content library and minimizing re-work.

ADditional Updates

•Added the ability to view parameters by Revit Version.  There is now a dropdown on the file details page for Revit Version, which will display the parameters for the selected type that are associated with the selected Revit version.

•Revit template files (.rte) will now initiate a new model (.rvt) by default when opened from UNIFI.  To edit the template file itself, right-click on the file in UNIFI and select “Open in Revit”.  

•The default due date for content requests has been changed from 1 day to 7 days out.

In Project Analytics, data on the model dashboard Content tab can now be exported to Excel.

•Made enhancements to the process of collecting Project Analytics data.

•Project Analytics data collection now includes Revit session properties and family parameter data.

•Resolved issues where search terms were not yielding accurate search results.

•Uploading multiple copies of the same Revit file that were saved in different Revit version years will now all upload as revisions of the file rather than only uploading the lowest Revit version.

•Deleting a base file of a Revit file will no longer clear the category for that file.

•Navigating back to browse after having a filter applied and viewing file details will now display properly.

•After rejecting a content upload request that had previously been approved, the applicable content will now be removed from search results.

•UNIFI will now launch when using 4K resolution monitors with screen zooming enabled.

•The UNIFI installer will now update on machines that don’t have Revit installed as well as UNIFI installations that include the MicroStation Add-In.

•Resolved an issue where Library Admin uploads were not approved automatically.

•Browsing channel content categories that do not exist in the company library now only displays content in the selected category.

•Revit files created in version 2009 or older will now upload to UNIFI.

•Resolved an issue where preview images were not captured when uploading MicroStation .dgn files.

•The category search filter now only lists categories that contain actively searchable content.

•Resolved an issue where all content requests were displaying for all users.  Regular users will only see content requests that they have submitted.

•Inserting Revit 2019 materials with 2018 rendered assets can now be inserted from UNIFI.

•Uploading a revision for Revit family template files (.rft) to UNIFI will now display the proper Revit base file year.

•Batch exporting Schedules and Drafting Views will no longer fail when UNIFI is maximized.

•Resolved an issue where using Harvest Project to search for a Revit project stored in UNIFI would not generate results.

•Resolved an issue with setting pinned libraries via the API.

•Resolved an issue with users unable to login using an SSO provider.

•Identified a known issue: When updating UNIFI without Revit installed on the machine, the update process may get interrupted or end prematurely.  If this occurs, simply uninstall reinstall UNIFI using the latest installer.

Wrap up:

Thanks for being a valued UNIFI customer and taking the time to get the scoop on our latest update. We hope you find the updates and fixes in this release useful!

We wanted to quickly mention one last platform change to come; the Event Stream feature will no longer be supported and removed from the UNIFI Portal at the end of this year. It has been replaced by Project Analytics.  Information about content inserted from UNIFI and what revision of the content was inserted compared to the current revision in UNIFI can be found on the Content tab of the model dashboard in Project Analytics. 

Please stay tuned for updates on our Shared Parameter Management feature coming next month.Until then, please remember that your feedback is very important to us and we’re always looking for ways to improve our platform. If you have suggestions for future updates or changes, please click here to learn how to submit your recommendations directly in the UNIFI platform.

Open Sourced: A Sample App to Generate a Changelog of Revit Elements

Earlier this year, we launched our very first open source project which serves as an example of how to leverage our Content Management API to validate Revit family parameters for Revit elements in your UNIFI Pro libraries. This week, we’re excited to announce that we’ve released our second open source sample application which demonstrates how to implement the Project Analytics API. Please click here for the full UNIFI API documentation.

What does the new application  do?

Project Analytics collects Revit data every time a user syncs with the central model, making it one of the few ways to review the “live” Revit model data without opening the Revit application itself. This tool is able to capture the data for each placed Revit element, including its parameter values, as of any given sync. Said differently, Project Analytics essentially creates a snapshot of the Revit model every time a user syncs.

What most users don’t realize is that these snapshots of the Revit model are stored in our database and available via the Project Analytics API. This sample application demonstrates how users have the ability to surface this valuable data using the API.

Please note that all users must have access to the Project Analytics API to use this application. If you have trouble logging in, talk to your company administrator or contact us.

Here’s a few of the many things you can do with the open source sample application:

#1: Review Historical BIM Data

The main feature of this sample application is to surface the Revit element parameter data as of each sync to central. End-users are given an intuitive interface to step through the data and browse model snapshots, placed Revit elements, and parameter data.

Revit Elements

1. Select a project from the Projects dropdown menu. If the selected project has models assigned, the Models dropdown menu appears and is populated with the models that are assigned to the selected project.

This action makes an API call to the /models endpoint to retrieve all models from the selected project.

2. Select a model from the Models dropdown menu to populate the Model Snapshots column with the snapshots (i.e., syncs to central) of the selected model.

This action makes an API call to the /models/{id}/commits endpoint to retrieve all commits for the selected model.

3. Select a snapshot (i.e., commit) to populate the Assets column with all of the assets (i.e., family instances) that were placed in the model at the time of the selected sync.

This action makes an API call to the /models/{id}/commmits/{eventId} endpoint to retrieve the data for that specific commit.

4. Select an asset from the Assets column to populate the Data grid to review the parameter values of that particular family instance.

This action does not make an API call because the data was previously collected from the /models/{id}/commits/{eventId} endpoint.

#2: Generate a Changelog for Revit Elements

In my previous life as a BIM manager, we had bounced around several ideas on how to track who was doing what in our models across our internal team or 3rd party consultants. We came up with more than a few time-consuming ideas such as having our staff add a narrative to a text file every day (i.e., a changelog). Of course, nobody had the time or energy to manually type up everything they were doing in their models, so that immediately compromised the accuracy of the changelog.

This sample application has the ability to automatically generate a changelog which compares any historical snapshot of the model to the current snapshot. In the current version, the application identifies Revit elements that were added or deleted from a Revit model. The Revit element ID is also included in the report (in square brackets) allowing users to track down the family instance within the Revit environment as well.

Note that this is just a small subset of the data that is collected at each sync. In addition to placed Revit elements, Project Analytics stores data such as project basepoints, sheets, drafting views, and more.

Revit Elements

Open Source on GitHub

These open source projects are available for the community’s contributions in any way. A few ideas that we had around additional features include finding changes to parameter values, checking for moved project base points, validating sheet naming conventions, and more. 

We’d love to hear your ideas as well. Please check out the repo on GitHub and let’s build something together!

Implementing a Sandbox Library in UNIFI

Sandbox library

Many of our users are in a constant state of quality control of the content within their libraries regardless of their BIM maturity level. This is because there will always be a need for new content and most large firms need some sort of a vetting process to approve any new content before it is rolled out to their libraries. This quality control process is a critical component of maintaining solid BIM standards.

In this post, I’ll guide you through one option for implementing a workflow for vetting content using UNIFI Pro. This method involves implementing what I like to call “a sandbox library”.

What is a sandbox library?

This may be a new term for the AECO industry, but I borrowed the concept of a sandbox library from software developers.

“A sandbox is a type of software testing environment that enables the isolated execution of software or programs for independent evaluation, monitoring or testing.” – techopedia

You may be more accustomed to terms like “work in progress” or “do not use,” but I like using the phrase “sandbox” because it has a literal meaning of a place that you play which is also contained.

In the context of BIM objects, a sandbox library would be very similar to the above definition, but rather than a testing environment for software, it is a testing environment for Revit families (or really any other type of content you’re storing in UNIFI).

For this concept to work, you’ll need to setup a library specifically for this workflow, which is illustrated in the simple flowchart below. As you can see, it is a relatively simple process and can be implemented in just a few minutes.

Sandbox library

Permissions Configurations

You’ll want a specific library created dedicated to this workflow because libraries in UNIFI Pro are driven by permissions. Each library has options to grant access to specific users or groups of users as well as administrator rights for approving and rejecting content.

I typically suggest that your sandbox library has limited access to your entire team because it helps you control what content is released out in the wild. When thinking about this in terms of Revit families, it can be a major issue when unapproved Revit families get into live Revit projects because it is conventionally very difficult know which models have the most up-to-date version of the family (check out Project Analytics which helps keep track the current revision of the families loaded into projects).

In addition to controlling access to the content within the sandbox library, you’ll also want to identify a group of individuals who will oversee approving and rejecting the content. Remember, content is not visible to non-admin users of libraries until it’s approved by an admin.

The UNIFI Pro Interface for Configuring Library Permissions

Sandbox Library1. Toolbar – Manage Libraries2. Tab – Assign library administrators

2. Tab – Grant individual users access to the library

3. Tab – Grant user groups access to the library

4. Button – Select a user to be added as a library administrator

5. Button – Remove an existing library administator from the library

Permissions for Testing Content

As you’re planning out the permissions for access and administrators, you’ll need to put some thought into whether or not you want non-admins to test the content. With that being said, you have two main scenarios for the testing content within a sandbox library:

1.Users with access can upload content and test the content – Going this route means the sandbox library admins will need to approve content before testing because it will not be visible to standard users.

2.Only library admins can test content – This means there is no approval process necessary because library admins can use content that is in a pending status.

Both are viable options for sandbox libraries in UNIFI Pro, you’ll need to identify which works best for your organization and assign permissions accordingly.

Revisions in UNIFI

One of the highly acclaimed features of UNIFI Pro is the revisioning system. When content is revised and re-uploaded to the library, a new  revision is automatically created. These revisions automatically keep track of who changed the content and when, but most importantly, it has the capability to add notes for each revision.

This is the main reason that I recommend UNIFI as a platform for testing and approving content. The ability to store multiple revisions and roll back to a previous revision is key when working on a team. You can consider this a change log and backup system all in one.

Sandbox Library

Rolling Out Approved Content

Once you’re ready to roll out your tested, revised, and approved content to the rest of the team, it’s as easy as flipping a few switches. You’ll simply need to navigate to the Library Management tab of the content and uncheck the Sandbox library and check the box next to the libraries you’ll want to move the content to.

This single step removes the content from the testing ground and essentially publishes it because it will now be accessible to anyone who has access to the newly assigned libraries.

Sandbox Library

UNIFI Pro as Quality Control Platform

Many BIM managers tend to have the mindset that they only want “good content” to be added to their UNIFI libraries, but I hope this has presented some of the benefits of using UNIFI Pro throughout the quality control process for your content. I feel that throughout the vetting process, you’ll want a changelog and backups for your content, so why not use UNIFI to keep track of this data?

Questions or comments?

What are your thoughts on using a sandbox library to help with the vetting of your Revit families? Do you have any questions on implementing a sandbox library at your firm? Leave us a comment and let’s discuss!

Managing Your Revit Add-ins: A Must Have Application

These days, there are typically several Revit add-ins in any power user’s toolbox. Whether you use Revit add-ins to help you manage data, batch process tasks, or automatically model elements, there is no doubt that Revit has an ecosystem of productivity tools built around it.

If you tend to rely on several Revit add-ins, there may come a time where you need an easy way to temporarily disable them without uninstalling. The ability to disable Revit add-ins in this fashion can help speed up the time it takes to launch Revit as well as help identify which add-ins are problematic.

The good news is that one of our favorite clients, Stantec, has open-sourced their Revit add-in manager which grants users the power of enabling and disabling Revit add-ins on the fly. I prefer this Revit Add-in Manager over the one provided by Autodesk in their SDK because it is a standalone application, meaning you don’t need to run Revit to manage your add-ins.

Download the Revit Add-in Manager

Before we continue, it is worth noting that although you will be downloading a Visual Studio solution, you won’t need to understand C# or how to use Visual Studio to run the Revit Add-in Manager application.

Perhaps someday I’ll propose that Stantec hosts the Revit Add-in Manager code on GitHub in true open source fashion, but as of now Boost Your BIM has shared the Visual Studio solution as a zip file on Bit Bucket. Simply download the zip file and unzip it to any location on your machine.

No Installation Needed

Being as this is a lightweight application, you won’t need to run an installer. You can simply double-click the exe file to run the Revit Add-in Manager.

Navigate to \AddInManager\bin\Debug. For reference, the full path on my machine after extraction is:  C:\Users\Jay Merlan\Downloads\BoostYourBIM-stantecaddinmanager-03365f381880\BoostYourBIM-stantecaddinmanager-03365f381880\AddInManager\bin\Debug.

In this folder, you’ll find a lonely file called AddInManager.exe. Double-click that file to run the Revit Add-in Manager.

How to Use the Stantec Revit Add-in Manager

Revit add-ins

I love the simplicity of this tool.

Immediately upon launching, you’ll see a list of every single Revit add-in that is installed on your machine. The interface is really straightforward and easy to understand, but let’s cover the two most important features.

1) Filter Revit Add-ins by Revit Version

Revit add-ins

At the very top of the Revit Add-in Manager application window, a dropdown menu allows you to filter the list of Revit add-ins by the version of Revit. This proves extremely helpful for navigating through the Revit add-ins for the several Revit versions that you most likely have installed.

2) Enable or Disable Revit Addins

Revit add-ins

Select any Revit add-ins that you don’t have a use for. Note that you can select multiple Revit add-ins by holding down the control key or shift key on your keyboard while clicking. Once you’ve selected the Revit Add-ins that you would like to disable, click the “Enable / Disable” button in the lower right corner of the window. You’ll notice that the “Enabled” column now read “no” for the Revit add-ins that you’ve disabled.

Launch Revit and you’ll discover that the Revit add-ins that you’ve chosen to disable no longer load.

Revit add-ins

How The Stantec Revit Add-in Manager Works

Even under the hood, this application is actually rather simple. If you navigate to your add-ins folder (C:\ProgramData\Autodesk\Revit\Addins\2019), you’ll notice that the Revit add-ins that you’ve disabled now have a new file extension, *.disabled. The Revit Add-in Manager has simply changed the file extension from the default *.addin, so Revit no longer sees the file as an add-in and does not load it. Simple!

Revit add-ins

This means that you can easily re-enable the Revit add-ins, with or without the Revit Add-in Manager application itself. If you no longer have the Stantec Revit Add-in Manager, simply rename the file and revert the “*.disabled” file extension back to “*.addin”.

Thank you, Stantec.

A special thank you goes out to Stantec for sharing this simple, yet useful, application with our industry. I hope that it will help you maintain control over the many Revit add-ins that you currently have installed, especially if you only need to temporarily enable or disable them.